Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 18
Question 170
A hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Acceptance evidence: Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change. This pairing is justified because declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
Incorrect Answers
This action and check address the distinct objective “Apply GitOps reconciliation with a version-controlled desired state” instead of the stated acceptance requirement. The matching action is to keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Its confirming test is to edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
This action and check address the distinct objective “Use nodeSelector to place a workload on nodes with required labels” instead of the stated acceptance requirement. The matching action is to keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Its confirming test is to edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
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 keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Its confirming test is to edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
Question 171
A municipal data team creates a Deployment whose Pods cannot find matching nodes. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. This resolves the issue because the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors. To verify, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
Incorrect Answers
This option addresses the distinct objective “Separate kube-scheduler decisions from kubelet execution”, not the immediate requirement. The scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers. For the stated case, the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
This option addresses the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”, not the immediate requirement. Authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it. For the stated case, the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
This option addresses the distinct objective “Define secure release governance with staged approvals and policy verification”, not the immediate requirement. A deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production. For the stated case, the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
Question 172
A municipal data team creates a Deployment whose Pods cannot find matching nodes. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors. It supports this action: Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. To confirm, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
Incorrect Answers
That statement explains the distinct objective “Use rollout status and undo to validate and recover a Deployment release” rather than the cause in this case. The deciding mechanism here is that the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
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 the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
That statement explains the distinct objective “Define secure release governance with staged approvals and policy verification” rather than the cause in this case. The deciding mechanism here is that the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
Question 173
A municipal data team creates a Deployment whose Pods cannot find matching nodes. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events. This is the relevant test because the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
Incorrect Answers
This check would help evaluate the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”, but not the required result. For this case, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
This check would help evaluate the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”, but not the required result. For this case, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
This check would help evaluate the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance”, but not the required result. For this case, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
Question 174
A municipal data team creates a Deployment whose Pods cannot find matching nodes. The change review contains this proposal: “Conclude that successful API object creation guarantees successful container execution on a worker.” What risk matters most?
Explanation
Correct Answer
A resource can remain Pending indefinitely even while its desired configuration is stored correctly. The shortcut creates this risk because the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
Incorrect Answers
That outcome concerns the distinct objective “Distinguish preferred node affinity from required scheduling rules”; it is not the most direct consequence of this shortcut. The relevant consequence is that a resource can remain Pending indefinitely even while its desired configuration is stored correctly.
That outcome concerns the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”; it is not the most direct consequence of this shortcut. The relevant consequence is that a resource can remain Pending indefinitely even while its desired configuration is stored correctly.
That outcome concerns the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources”; it is not the most direct consequence of this shortcut. The relevant consequence is that a resource can remain Pending indefinitely even while its desired configuration is stored correctly.
Question 175
A municipal data team creates a Deployment whose Pods cannot find matching nodes. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Acceptance evidence: Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events. This pairing is justified because the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
Incorrect Answers
This action and check address the distinct objective “Use Events and pod describe for failed volume mounting” instead of the stated acceptance requirement. The matching action is to read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Its confirming test is to apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
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 read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Its confirming test is to apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
This action and check address the distinct objective “Explain the container runtime interface without conflating it with the control plane” instead of the stated acceptance requirement. The matching action is to read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Its confirming test is to apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
Question 176
A medical lab sees an updated Deployment specification but its available replicas remain zero. What technical action should the platform team take in this situation?
Explanation
Correct Answer
The situation is that a medical lab sees an updated Deployment specification but its available replicas remain zero. Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. This resolves the issue because the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors. To verify, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
Incorrect Answers
This option addresses the distinct objective “Use kubectl get and describe for distinct inspection needs”, not the immediate requirement. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis. For the stated case, the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
This option addresses the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point”, not the immediate requirement. The kube-apiserver validates authorized API requests and exposes the declarative resource interface; kubelets and controllers subsequently reconcile the saved desired state. For the stated case, the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
This option addresses the distinct objective “Distinguish service mesh traffic management from external ingress routing”, not the immediate requirement. Service meshes commonly use proxies or ambient dataplanes to control east-west traffic; ingress/gateway handling addresses entry routes and can integrate with the mesh. For the stated case, the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
Question 177
A medical lab sees an updated Deployment specification but its available replicas remain zero. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a medical lab sees an updated Deployment specification but its available replicas remain zero. The spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors. It supports this action: Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. To confirm, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
Incorrect Answers
That statement explains the distinct objective “Distinguish Deployment desired state from a manually created Pod” rather than the cause in this case. The deciding mechanism here is that the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
That statement explains the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration” rather than the cause in this case. The deciding mechanism here is that the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
That statement explains the distinct objective “Investigate readiness failures separately from liveness-related restarts” rather than the cause in this case. The deciding mechanism here is that the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
Question 178
A medical lab sees an updated Deployment specification but its available replicas remain zero. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a medical lab sees an updated Deployment specification but its available replicas remain zero. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events. This is the relevant test because the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
Incorrect Answers
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, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
This check would help evaluate the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”, but not the required result. For this case, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
The situation is that a medical lab sees an updated Deployment specification but its available replicas remain zero. This check would help evaluate the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”, but not the required result. For this case, apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
Question 179
A medical lab sees an updated Deployment specification but its available replicas remain zero. The team suggests: “Conclude that successful API object creation guarantees successful container execution on a worker.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a medical lab sees an updated Deployment specification but its available replicas remain zero. A resource can remain Pending indefinitely even while its desired configuration is stored correctly. The shortcut creates this risk because the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
Incorrect Answers
That outcome concerns the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it”; it is not the most direct consequence of this shortcut. The relevant consequence is that a resource can remain Pending indefinitely even while its desired configuration is stored correctly.
That outcome concerns the distinct objective “Run images with least-privilege runtime security contexts”; it is not the most direct consequence of this shortcut. The relevant consequence is that a resource can remain Pending indefinitely even while its desired configuration is stored correctly.
That outcome concerns the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership”; it is not the most direct consequence of this shortcut. The relevant consequence is that a resource can remain Pending indefinitely even while its desired configuration is stored correctly.
Question 180
A medical lab sees an updated Deployment specification but its available replicas remain zero. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a medical lab sees an updated Deployment specification but its available replicas remain zero. Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Acceptance evidence: Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events. This pairing is justified because the spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
Incorrect Answers
This action and check address the distinct objective “Distinguish preferred node affinity from required scheduling rules” instead of the stated acceptance requirement. The matching action is to read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Its confirming test is to apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
This action and check address the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion” instead of the stated acceptance requirement. The matching action is to read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Its confirming test is to apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
This action and check address the distinct objective “Use annotations for tool metadata rather than workload selection” instead of the stated acceptance requirement. The matching action is to read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Its confirming test is to apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 16 - 10 Questions (Last Reviewed 05-Nov-2026)
- Linux Foundation KCNA Practice Test 17 - 10 Questions (Last Reviewed 04-Nov-2026)
- Linux Foundation KCNA Practice Test 18 - 10 Questions (Last Reviewed 03-Nov-2026)
- Linux Foundation KCNA Practice Test 19 - 10 Questions (Last Reviewed 02-Nov-2026)
- Linux Foundation KCNA Practice Test 20 - 10 Questions (Last Reviewed 01-Nov-2026)