Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 13
Question 120
A small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Acceptance evidence: Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge. This pairing is justified because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
Incorrect Answers
This action and check address the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities” instead of the stated acceptance requirement. The matching action is to change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Its confirming test is to set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
This action and check address the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” instead of the stated acceptance requirement. The matching action is to change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Its confirming test is to set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
This action and check address the distinct objective “Use image provenance and policy controls without trusting mutable tags” instead of the stated acceptance requirement. The matching action is to change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Its confirming test is to set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
Question 121
A hospital schedules application Pods with a team label and wants a Service to expose only the approved backend. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. This resolves the issue because Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships. To verify, compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
Incorrect Answers
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, Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
This option addresses the distinct objective “Explain metrics, logs and traces as complementary observability signals”, not the immediate requirement. Each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop. For the stated case, Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
This option addresses the distinct objective “Explain the container runtime interface without conflating it with the control plane”, not the immediate requirement. A supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface. For the stated case, Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
Question 122
A hospital schedules application Pods with a team label and wants a Service to expose only the approved backend. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships. It supports this action: Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. To confirm, compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
Incorrect Answers
That statement explains the distinct objective “Understand taints and tolerations as repulsion controls” rather than the cause in this case. The deciding mechanism here is that Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
That statement explains the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities” rather than the cause in this case. The deciding mechanism here is that Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
That statement explains the distinct objective “Use kubectl logs and previous container logs to isolate application crashes” rather than the cause in this case. The deciding mechanism here is that Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
Question 123
A hospital schedules application Pods with a team label and wants a Service to expose only the approved backend. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload. This is the relevant test because Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
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, compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
This check would help evaluate the distinct objective “Identify reconciliation work performed by kube-controller-manager”, but not the required result. For this case, compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
This check would help evaluate the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”, but not the required result. For this case, compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
Question 124
A hospital schedules application Pods with a team label and wants a Service to expose only the approved backend. An engineer proposes: “Name every Pod inventory but omit or mistype the Service's app selector, expecting name similarity to route traffic.” What adverse outcome would be most direct?
Explanation
Correct Answer
The Service receives no intended ready endpoints even when healthy Pods exist. The shortcut creates this risk because Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
Incorrect Answers
That outcome concerns the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Service receives no intended ready endpoints even when healthy Pods exist.
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 the Service receives no intended ready endpoints even when healthy Pods exist.
That outcome concerns the distinct objective “Use rollout status and undo to validate and recover a Deployment release”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Service receives no intended ready endpoints even when healthy Pods exist.
Question 125
A hospital schedules application Pods with a team label and wants a Service to expose only the approved backend. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Acceptance evidence: Compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload. This pairing is justified because Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
Incorrect Answers
This action and check address the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments” instead of the stated acceptance requirement. The matching action is to apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Its confirming test is to compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
This action and check address the distinct objective “Use Pods as the shared network and storage execution unit” instead of the stated acceptance requirement. The matching action is to apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Its confirming test is to compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
This action and check address the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities” instead of the stated acceptance requirement. The matching action is to apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Its confirming test is to compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
Question 126
A campus project renames Pods but does not update labels referenced by its existing Service. What technical action should the platform team take in this situation?
Explanation
Correct Answer
The situation is that a campus project renames Pods but does not update labels referenced by its existing Service. Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. This resolves the issue because Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships. To verify, compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
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, Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
This option addresses the distinct objective “Distinguish etcd persistence from running workload data”, not the immediate requirement. Etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd. For the stated case, Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
This option addresses the distinct objective “Instrument services with OpenTelemetry context propagation”, not the immediate requirement. Trace context allows spans from different services to join one transaction view, while collectors receive and forward telemetry without automatically storing all data. For the stated case, Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
Question 127
A campus project renames Pods but does not update labels referenced by its existing Service. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a campus project renames Pods but does not update labels referenced by its existing Service. Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships. It supports this action: Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. To confirm, compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
Incorrect Answers
The situation is that a campus project renames Pods but does not update labels referenced by its existing Service. That statement explains the distinct objective “Use kubectl logs and previous container logs to isolate application crashes” rather than the cause in this case. The deciding mechanism here is that Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
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 Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
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 Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
Question 128
A campus project renames Pods but does not update labels referenced by its existing Service. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a campus project renames Pods but does not update labels referenced by its existing Service. Compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload. This is the relevant test because Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
Incorrect Answers
This check would help evaluate the distinct objective “Explain desired state versus observed status in Kubernetes objects”, but not the required result. For this case, compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
This check would help evaluate the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”, but not the required result. For this case, compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
This check would help evaluate the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability”, but not the required result. For this case, compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
Question 129
A campus project renames Pods but does not update labels referenced by its existing Service. The team suggests: “Name every Pod inventory but omit or mistype the Service's app selector, expecting name similarity to route traffic.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a campus project renames Pods but does not update labels referenced by its existing Service. The Service receives no intended ready endpoints even when healthy Pods exist. The shortcut creates this risk because Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
Incorrect Answers
That outcome concerns the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Service receives no intended ready endpoints even when healthy Pods exist.
That outcome concerns the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Service receives no intended ready endpoints even when healthy Pods exist.
That outcome concerns the distinct objective “Understand ports, targetPort and protocol mapping in a Service”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Service receives no intended ready endpoints even when healthy Pods exist.
Question 130
A campus project renames Pods but does not update labels referenced by its existing Service. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a campus project renames Pods but does not update labels referenced by its existing Service. Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Acceptance evidence: Compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload. This pairing is justified because Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
Incorrect Answers
This action and check address the distinct objective “Separate kube-scheduler decisions from kubelet execution” instead of the stated acceptance requirement. The matching action is to apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Its confirming test is to compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
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 apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Its confirming test is to compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
This action and check address the distinct objective “Distinguish Deployment desired state from a manually created Pod” instead of the stated acceptance requirement. The matching action is to apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Its confirming test is to compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 11 - 10 Questions (Last Reviewed 10-Nov-2026)
- Linux Foundation KCNA Practice Test 12 - 10 Questions (Last Reviewed 09-Nov-2026)
- Linux Foundation KCNA Practice Test 13 - 10 Questions (Last Reviewed 08-Nov-2026)
- Linux Foundation KCNA Practice Test 14 - 10 Questions (Last Reviewed 07-Nov-2026)
- Linux Foundation KCNA Practice Test 15 - 10 Questions (Last Reviewed 06-Nov-2026)