Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 17
Question 160
A shipping developer reads Ready 0/1 from kubectl get and wants conditions and Events before changing the image. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a shipping developer reads Ready 0/1 from kubectl get and wants conditions and Events before changing the image. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Acceptance evidence: Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events. This pairing is justified because get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.
Incorrect Answers
This action and check address the distinct objective “Understand Prometheus pull-based metrics collection and exporters” instead of the stated acceptance requirement. The matching action is to use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Its confirming test is to compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.
This action and check address the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability” instead of the stated acceptance requirement. The matching action is to use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Its confirming test is to compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.
This action and check address the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” instead of the stated acceptance requirement. The matching action is to use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Its confirming test is to compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.
Question 161
A research portal updates a container image across two campus clusters with the same manifest. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. This resolves the issue because declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management. To verify, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
Incorrect Answers
This option addresses the distinct objective “Use annotations for tool metadata rather than workload selection”, not the immediate requirement. Labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control. For the stated case, declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
This option addresses the distinct objective “Run images with least-privilege runtime security contexts”, not the immediate requirement. SecurityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised. For the stated case, declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
This option addresses the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, not the immediate requirement. CNCF maturity describes aspects of adoption and governance, not a blanket guarantee that every deployment or version is free of defects. For the stated case, declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
Question 162
A research portal updates a container image across two campus clusters with the same manifest. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
Declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management. It supports this action: Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. To confirm, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
Incorrect Answers
That statement explains the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend” rather than the cause in this case. The deciding mechanism here is that declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
That statement explains the distinct objective “Explain the container runtime interface without conflating it with the control plane” rather than the cause in this case. The deciding mechanism here is that declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
That statement explains the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” rather than the cause in this case. The deciding mechanism here is that declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
Question 163
A research portal updates a container image across two campus clusters with the same manifest. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change. This is the relevant test 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 check would help evaluate the distinct objective “Use rollout status and undo to validate and recover a Deployment release”, but not the required result. For this case, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
This check would help evaluate the distinct objective “Diagnose cluster DNS separately from Pod network reachability”, but not the required result. For this case, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
This check would help evaluate the distinct objective “Understand readiness, liveness and startup probes as different signals”, but not the required result. For this case, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
Question 164
A research portal updates a container image across two campus clusters with the same manifest. A shortcut is proposed: “Install a package manually inside a running Pod and treat that mutable container filesystem as the durable release artifact.” Which technical consequence follows most closely?
Explanation
Correct Answer
The emergency fix disappears when the Pod is replaced and cannot be reproduced reliably. The shortcut creates this risk because declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
Incorrect Answers
That outcome concerns the distinct objective “Distinguish etcd persistence from running workload data”; it is not the most direct consequence of this shortcut. The relevant consequence is that the emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.
That outcome concerns the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”; it is not the most direct consequence of this shortcut. The relevant consequence is that the emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.
That outcome concerns the distinct objective “Use kubectl get and describe for distinct inspection needs”; it is not the most direct consequence of this shortcut. The relevant consequence is that the emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.
Question 165
A research portal updates a container image across two campus clusters with the same manifest. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
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 “Explain metrics, logs and traces as complementary observability signals” 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 “Interpret Kubernetes spec and status fields without confusing intent with condition” 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 “Recognize the kubelet role in local Pod lifecycle management” 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 166
A hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. What technical action should the platform team take in this situation?
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. This resolves the issue because declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management. To verify, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
Incorrect Answers
The situation is that a hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. This option addresses the distinct objective “Use annotations for tool metadata rather than workload selection”, not the immediate requirement. Labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control. For the stated case, declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
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, declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
This option addresses the distinct objective “Understand ports, targetPort and protocol mapping in a Service”, not the immediate requirement. A Service exposes port to clients and forwards to targetPort on selected endpoints; a mismatched targetPort can break delivery even with valid DNS and selectors. For the stated case, declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
Question 167
A hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. Declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management. It supports this action: Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. To confirm, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
Incorrect Answers
That statement explains the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration” rather than the cause in this case. The deciding mechanism here is that declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
That statement explains the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” rather than the cause in this case. The deciding mechanism here is that declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
That statement explains the distinct objective “Understand CSI drivers and volume attachment responsibilities” rather than the cause in this case. The deciding mechanism here is that declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
Question 168
A hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change. This is the relevant test 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 check would help evaluate the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition”, but not the required result. For this case, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
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, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
This check would help evaluate the distinct objective “Use Pods as the shared network and storage execution unit”, but not the required result. For this case, edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
Question 169
A hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. The team suggests: “Install a package manually inside a running Pod and treat that mutable container filesystem as the durable release artifact.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a hotel service team keeps modifying a live Pod shell instead of changing its Deployment definition. The emergency fix disappears when the Pod is replaced and cannot be reproduced reliably. The shortcut creates this risk because declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
Incorrect Answers
That outcome concerns the distinct objective “Correlate application rollout revisions with error spikes”; it is not the most direct consequence of this shortcut. The relevant consequence is that the emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.
That outcome concerns the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration”; it is not the most direct consequence of this shortcut. The relevant consequence is that the emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.
That outcome concerns the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”; it is not the most direct consequence of this shortcut. The relevant consequence is that the emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.
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.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 15 - 10 Questions (Last Reviewed 06-Nov-2026)
- 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)