Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 42
Question 410
A city records service keeps durable PDF attachments on an emptyDir and loses them during maintenance. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a city records service keeps durable PDF attachments on an emptyDir and loses them during maintenance. Use emptyDir for temporary sharing between containers within a Pod, and PVC-backed storage when data must survive Pod replacement. Acceptance evidence: Write a synthetic temporary file into emptyDir, restart a container and then recreate the Pod to compare lifetime semantics. This pairing is justified because emptyDir is initialized for a Pod and its contents can be shared among containers but do not survive the Pod's removal.
Incorrect Answers
This action and check address the distinct objective “Understand taints and tolerations as repulsion controls” instead of the stated acceptance requirement. The matching action is to use emptyDir for temporary sharing between containers within a Pod, and PVC-backed storage when data must survive Pod replacement. Its confirming test is to write a synthetic temporary file into emptyDir, restart a container and then recreate the Pod to compare lifetime semantics.
This action and check address the distinct objective “Design a release rollback trigger from measurable service signals” instead of the stated acceptance requirement. The matching action is to use emptyDir for temporary sharing between containers within a Pod, and PVC-backed storage when data must survive Pod replacement. Its confirming test is to write a synthetic temporary file into emptyDir, restart a container and then recreate the Pod to compare lifetime semantics.
This action and check address the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images” instead of the stated acceptance requirement. The matching action is to use emptyDir for temporary sharing between containers within a Pod, and PVC-backed storage when data must survive Pod replacement. Its confirming test is to write a synthetic temporary file into emptyDir, restart a container and then recreate the Pod to compare lifetime semantics.
Question 411
A hospital deploys an HTTP API that only needs to bind an unprivileged port. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
Set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root. This resolves the issue because securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised. To verify, deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
Incorrect Answers
This option addresses the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules”, not the immediate requirement. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior. For the stated case, securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
This option addresses the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling”, not the immediate requirement. Multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer. For the stated case, securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
This option addresses the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”, not the immediate requirement. Image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs. For the stated case, securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
Question 412
A hospital deploys an HTTP API that only needs to bind an unprivileged port. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
SecurityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised. It supports this action: Set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root. To confirm, deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
Incorrect Answers
That statement explains the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images” rather than the cause in this case. The deciding mechanism here is that securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
That statement explains the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads” rather than the cause in this case. The deciding mechanism here is that securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
That statement explains the distinct objective “Distinguish a container image from a running container and its writable layer” rather than the cause in this case. The deciding mechanism here is that securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
Question 413
A hospital deploys an HTTP API that only needs to bind an unprivileged port. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
Deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work. This is the relevant test because securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
Incorrect Answers
This check would help evaluate the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”, but not the required result. For this case, deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
This check would help evaluate the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”, but not the required result. For this case, deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
This check would help evaluate the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend”, but not the required result. For this case, deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
Question 414
A hospital deploys an HTTP API that only needs to bind an unprivileged port. A shortcut is proposed: “Set privileged=true on every Pod so normal application file-permission errors disappear.” Which technical consequence follows most closely?
Explanation
Correct Answer
Containers gain broad host exposure and compromise blast radius becomes larger than the application's needs. The shortcut creates this risk because securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
Incorrect Answers
That outcome concerns the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”; it is not the most direct consequence of this shortcut. The relevant consequence is that containers gain broad host exposure and compromise blast radius becomes larger than the application's needs.
That outcome concerns the distinct objective “Externalize application configuration from an image while protecting secrets”; it is not the most direct consequence of this shortcut. The relevant consequence is that containers gain broad host exposure and compromise blast radius becomes larger than the application's needs.
That outcome concerns the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition”; it is not the most direct consequence of this shortcut. The relevant consequence is that containers gain broad host exposure and compromise blast radius becomes larger than the application's needs.
Question 415
A hospital deploys an HTTP API that only needs to bind an unprivileged port. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
Set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root. Acceptance evidence: Deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work. This pairing is justified because securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
Incorrect Answers
This action and check address the distinct objective “Distinguish a container image from a running container and its writable layer” instead of the stated acceptance requirement. The matching action is to set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root. Its confirming test is to deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
This action and check address the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration” instead of the stated acceptance requirement. The matching action is to set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root. Its confirming test is to deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
This action and check address the distinct objective “Distinguish Pod IPs from stable Services during rescheduling” instead of the stated acceptance requirement. The matching action is to set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root. Its confirming test is to deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
Question 416
A nonprofit investigates a container requiring root solely because its image directory permissions were configured incorrectly. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
The situation is that a nonprofit investigates a container requiring root solely because its image directory permissions were configured incorrectly. Set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root. This resolves the issue because securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised. To verify, deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
Incorrect Answers
This option addresses the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”, not the immediate requirement. Kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function. For the stated case, securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
This option addresses the distinct objective “Diagnose cluster DNS separately from Pod network reachability”, not the immediate requirement. Healthy direct IP connectivity with failed name resolution suggests a DNS path issue; failed Pod-to-Pod IP traffic suggests a lower-level network problem. For the stated case, securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
This option addresses the distinct objective “Distinguish a container image from a running container and its writable layer”, not the immediate requirement. An image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage. For the stated case, securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
Question 417
A nonprofit investigates a container requiring root solely because its image directory permissions were configured incorrectly. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
The situation is that a nonprofit investigates a container requiring root solely because its image directory permissions were configured incorrectly. SecurityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised. It supports this action: Set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root. To confirm, deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
Incorrect Answers
That statement explains the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts” rather than the cause in this case. The deciding mechanism here is that securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
That statement explains the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms” rather than the cause in this case. The deciding mechanism here is that securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
That statement explains the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names” rather than the cause in this case. The deciding mechanism here is that securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
Question 418
A nonprofit investigates a container requiring root solely because its image directory permissions were configured incorrectly. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
The situation is that a nonprofit investigates a container requiring root solely because its image directory permissions were configured incorrectly. Deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work. This is the relevant test because securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
Incorrect Answers
This check would help evaluate the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability”, but not the required result. For this case, deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
This check would help evaluate the distinct objective “Use kubectl get and describe for distinct inspection needs”, but not the required result. For this case, deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
This check would help evaluate the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”, but not the required result. For this case, deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
Question 419
A nonprofit investigates a container requiring root solely because its image directory permissions were configured incorrectly. A shortcut is proposed: “Set privileged=true on every Pod so normal application file-permission errors disappear.” Which technical consequence follows most closely?
Explanation
Correct Answer
The situation is that a nonprofit investigates a container requiring root solely because its image directory permissions were configured incorrectly. Containers gain broad host exposure and compromise blast radius becomes larger than the application's needs. The shortcut creates this risk because securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
Incorrect Answers
That outcome concerns the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling”; it is not the most direct consequence of this shortcut. The relevant consequence is that containers gain broad host exposure and compromise blast radius becomes larger than the application's needs.
That outcome concerns the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”; it is not the most direct consequence of this shortcut. The relevant consequence is that containers gain broad host exposure and compromise blast radius becomes larger than the application's needs.
That outcome concerns the distinct objective “Understand Prometheus pull-based metrics collection and exporters”; it is not the most direct consequence of this shortcut. The relevant consequence is that containers gain broad host exposure and compromise blast radius becomes larger than the application's needs.
Question 420
A nonprofit investigates a container requiring root solely because its image directory permissions were configured incorrectly. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
The situation is that a nonprofit investigates a container requiring root solely because its image directory permissions were configured incorrectly. Set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root. Acceptance evidence: Deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work. This pairing is justified because securityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
Incorrect Answers
This action and check address the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling” instead of the stated acceptance requirement. The matching action is to set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root. Its confirming test is to deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
This action and check address the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure” instead of the stated acceptance requirement. The matching action is to set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root. Its confirming test is to deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
This action and check address the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance” instead of the stated acceptance requirement. The matching action is to set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root. Its confirming test is to deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 40 - 10 Questions (Last Reviewed 12-Oct-2026)
- Linux Foundation KCNA Practice Test 41 - 10 Questions (Last Reviewed 11-Oct-2026)
- Linux Foundation KCNA Practice Test 42 - 10 Questions (Last Reviewed 10-Oct-2026)
- Linux Foundation KCNA Practice Test 43 - 10 Questions (Last Reviewed 09-Oct-2026)
- Linux Foundation KCNA Practice Test 44 - 10 Questions (Last Reviewed 08-Oct-2026)