Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 87
Question 860
A retailer sees new checkout failures but the Kubernetes Deployment condition remains Available. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a retailer sees new checkout failures but the Kubernetes Deployment condition remains Available. Compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression. Acceptance evidence: Deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior. This pairing is justified because Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.
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 compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression. Its confirming test is to deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.
The situation is that a retailer sees new checkout failures but the Kubernetes Deployment condition remains Available. This action and check address the distinct objective “Use metrics, logs and traces together when investigating cross-service latency” instead of the stated acceptance requirement. The matching action is to compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression. Its confirming test is to deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.
This action and check address the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors” instead of the stated acceptance requirement. The matching action is to compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression. Its confirming test is to deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.
Question 861
A public library web app resolves api.library.svc but receives no successful responses. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. This resolves the issue because a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port. To verify, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
Incorrect Answers
This option addresses the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments”, not the immediate requirement. Kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files. For the stated case, a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
This option addresses the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards”, not the immediate requirement. An ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration. For the stated case, a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
This option addresses the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”, not the immediate requirement. The scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests. For the stated case, a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
Question 862
A public library web app resolves api.library.svc but receives no successful responses. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
A Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port. It supports this action: Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. To confirm, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
Incorrect Answers
That statement explains the distinct objective “Configure Deployment rolling updates with availability safeguards” rather than the cause in this case. The deciding mechanism here is that a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
That statement explains the distinct objective “Explain metrics, logs and traces as complementary observability signals” rather than the cause in this case. The deciding mechanism here is that a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
That statement explains the distinct objective “Use metrics, logs and traces together when investigating cross-service latency” rather than the cause in this case. The deciding mechanism here is that a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
Question 863
A public library web app resolves api.library.svc but receives no successful responses. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms. This is the relevant test because a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
Incorrect Answers
This check would help evaluate the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors”, but not the required result. For this case, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
This check would help evaluate the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, but not the required result. For this case, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
This check would help evaluate the distinct objective “Identify reconciliation work performed by kube-controller-manager”, but not the required result. For this case, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
Question 864
A public library web app resolves api.library.svc but receives no successful responses. The change review contains this proposal: “Recreate the CoreDNS deployment every time a Service resolves but still returns connection refused.” What risk matters most?
Explanation
Correct Answer
DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged. The shortcut creates this risk because a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
Incorrect Answers
That outcome concerns the distinct objective “Use metrics, logs and traces together when investigating cross-service latency”; it is not the most direct consequence of this shortcut. The relevant consequence is that DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.
That outcome concerns the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults”; it is not the most direct consequence of this shortcut. The relevant consequence is that DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.
That outcome concerns the distinct objective “Use SLI and SLO measures to focus reliability objectives”; it is not the most direct consequence of this shortcut. The relevant consequence is that DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.
Question 865
A public library web app resolves api.library.svc but receives no successful responses. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Acceptance evidence: Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms. This pairing is justified because a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
Incorrect Answers
This action and check address the distinct objective “Use kubectl logs and previous container logs to isolate application crashes” instead of the stated acceptance requirement. The matching action is to check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Its confirming test is to test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
This action and check address the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors” instead of the stated acceptance requirement. The matching action is to check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Its confirming test is to test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
This action and check address the distinct objective “Understand readiness, liveness and startup probes as different signals” instead of the stated acceptance requirement. The matching action is to check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Its confirming test is to test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
Question 866
A regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. What technical action should the platform team take in this situation?
Explanation
Correct Answer
The situation is that a regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. This resolves the issue because a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port. To verify, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
Incorrect Answers
This option addresses the distinct objective “Distinguish Deployment desired state from a manually created Pod”, not the immediate requirement. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object. For the stated case, a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
This option addresses the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, not the immediate requirement. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller. For the stated case, a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
This option addresses the distinct objective “Use kubectl logs and previous container logs to isolate application crashes”, not the immediate requirement. Kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events. For the stated case, a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
Question 867
A regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. A Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port. It supports this action: Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. To confirm, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
Incorrect Answers
That statement explains the distinct objective “Correlate application rollout revisions with error spikes” rather than the cause in this case. The deciding mechanism here is that a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
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 a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
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 a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
Question 868
A regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms. This is the relevant test because a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
Incorrect Answers
This check would help evaluate the distinct objective “Externalize application configuration from an image while protecting secrets”, but not the required result. For this case, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
This check would help evaluate the distinct objective “Use metrics, logs and traces together when investigating cross-service latency”, but not the required result. For this case, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
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, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
Question 869
A regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. The team suggests: “Recreate the CoreDNS deployment every time a Service resolves but still returns connection refused.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged. The shortcut creates this risk because a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
Incorrect Answers
That outcome concerns the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors”; it is not the most direct consequence of this shortcut. The relevant consequence is that DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.
That outcome concerns the distinct objective “Diagnose cluster DNS separately from Pod network reachability”; it is not the most direct consequence of this shortcut. The relevant consequence is that DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.
That outcome concerns the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”; it is not the most direct consequence of this shortcut. The relevant consequence is that DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.
Question 870
A regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Acceptance evidence: Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms. This pairing is justified because a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
Incorrect Answers
This action and check address the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards” instead of the stated acceptance requirement. The matching action is to check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Its confirming test is to test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
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 check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Its confirming test is to test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
This action and check address the distinct objective “Distinguish ClusterRoles from Roles and binding scope” instead of the stated acceptance requirement. The matching action is to check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Its confirming test is to test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 85 - 10 Questions (Last Reviewed 24-Oct-2026)
- Linux Foundation KCNA Practice Test 86 - 10 Questions (Last Reviewed 23-Oct-2026)
- Linux Foundation KCNA Practice Test 87 - 10 Questions (Last Reviewed 22-Oct-2026)
- Linux Foundation KCNA Practice Test 88 - 10 Questions (Last Reviewed 21-Oct-2026)
- Linux Foundation KCNA Practice Test 89 - 10 Questions (Last Reviewed 20-Oct-2026)