Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 65
Question 640
A research group creates a Pod that references a PersistentVolumeClaim in another namespace. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. Acceptance evidence: Reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim. This pairing is justified because kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
Incorrect Answers
The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. This action and check address the distinct objective “Investigate readiness failures separately from liveness-related restarts” instead of the stated acceptance requirement. The matching action is to inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. Its confirming test is to reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
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 inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. Its confirming test is to reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
This action and check address the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules” instead of the stated acceptance requirement. The matching action is to inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. Its confirming test is to reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
Question 641
A school API can reach a backend by ClusterIP but cannot resolve its Service hostname. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
Run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. This resolves the issue because 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. To verify, test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
Incorrect Answers
This option addresses the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”, not the immediate requirement. Mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse. For the stated case, 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.
This option addresses the distinct objective “Use Events and pod describe for failed volume mounting”, not the immediate requirement. Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure. For the stated case, 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.
This option addresses the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”, not the immediate requirement. Pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes. For the stated case, 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.
Question 642
A school API can reach a backend by ClusterIP but cannot resolve its Service hostname. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
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. It supports this action: Run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. To confirm, test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
Incorrect Answers
That statement explains the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk” rather than the cause in this case. The deciding mechanism here is that 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.
That statement explains the distinct objective “Externalize application configuration from an image while protecting secrets” rather than the cause in this case. The deciding mechanism here is that 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.
That statement explains the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors” rather than the cause in this case. The deciding mechanism here is that 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.
Question 643
A school API can reach a backend by ClusterIP but cannot resolve its Service hostname. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
Test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails. This is the relevant test because 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.
Incorrect Answers
This check would help evaluate the distinct objective “Distinguish Deployment desired state from a manually created Pod”, but not the required result. For this case, test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
This check would help evaluate the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, but not the required result. For this case, test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
This check would help evaluate the distinct objective “Use image provenance and policy controls without trusting mutable tags”, but not the required result. For this case, test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
Question 644
A school API can reach a backend by ClusterIP but cannot resolve its Service hostname. A shortcut is proposed: “Reinstall the CNI plugin whenever one app misspells a Kubernetes Service name.” Which technical consequence follows most closely?
Explanation
Correct Answer
Unnecessary networking changes can disrupt unrelated services while the original name lookup error persists. The shortcut creates this risk because 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.
Incorrect Answers
That outcome concerns the distinct objective “Understand CNCF project maturity stages without equating them to security approval”; it is not the most direct consequence of this shortcut. The relevant consequence is that unnecessary networking changes can disrupt unrelated services while the original name lookup error persists.
That outcome concerns the distinct objective “Use Events and pod describe for failed volume mounting”; it is not the most direct consequence of this shortcut. The relevant consequence is that unnecessary networking changes can disrupt unrelated services while the original name lookup error persists.
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 unnecessary networking changes can disrupt unrelated services while the original name lookup error persists.
Question 645
A school API can reach a backend by ClusterIP but cannot resolve its Service hostname. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
Run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. Acceptance evidence: Test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails. This pairing is justified because 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.
Incorrect Answers
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 run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. Its confirming test is to test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
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 run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. Its confirming test is to test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
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 run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. Its confirming test is to test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
Question 646
A small bank has cross-node Pod IP failures as well as DNS failures after changing the network plugin. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
The situation is that a small bank has cross-node Pod IP failures as well as DNS failures after changing the network plugin. Run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. This resolves the issue because 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. To verify, test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
Incorrect Answers
The situation is that a small bank has cross-node Pod IP failures as well as DNS failures after changing the network plugin. This option addresses the distinct objective “Use Events and pod describe for failed volume mounting”, not the immediate requirement. Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure. For the stated case, 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.
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, 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.
This option addresses the distinct objective “Investigate readiness failures separately from liveness-related restarts”, not the immediate requirement. A failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ. For the stated case, 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.
Question 647
A small bank has cross-node Pod IP failures as well as DNS failures after changing the network plugin. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The situation is that a small bank has cross-node Pod IP failures as well as DNS failures after changing the network plugin. 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. It supports this action: Run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. To confirm, test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
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 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.
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 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.
That statement explains the distinct objective “Protect API server access using authenticated TLS clients and audited authorization” rather than the cause in this case. The deciding mechanism here is that 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.
Question 648
A small bank has cross-node Pod IP failures as well as DNS failures after changing the network plugin. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
The situation is that a small bank has cross-node Pod IP failures as well as DNS failures after changing the network plugin. Test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails. This is the relevant test because 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.
Incorrect Answers
This check would help evaluate the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions”, but not the required result. For this case, test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
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 the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
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, test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
Question 649
A small bank has cross-node Pod IP failures as well as DNS failures after changing the network plugin. The change review contains this proposal: “Reinstall the CNI plugin whenever one app misspells a Kubernetes Service name.” What risk matters most?
Explanation
Correct Answer
The situation is that a small bank has cross-node Pod IP failures as well as DNS failures after changing the network plugin. Unnecessary networking changes can disrupt unrelated services while the original name lookup error persists. The shortcut creates this risk because 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.
Incorrect Answers
That outcome concerns the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”; it is not the most direct consequence of this shortcut. The relevant consequence is that unnecessary networking changes can disrupt unrelated services while the original name lookup error persists.
The situation is that a small bank has cross-node Pod IP failures as well as DNS failures after changing the network plugin. That outcome concerns the distinct objective “Use Events and pod describe for failed volume mounting”; it is not the most direct consequence of this shortcut. The relevant consequence is that unnecessary networking changes can disrupt unrelated services while the original name lookup error persists.
That outcome concerns the distinct objective “Use an immutable image digest for exact deployment provenance”; it is not the most direct consequence of this shortcut. The relevant consequence is that unnecessary networking changes can disrupt unrelated services while the original name lookup error persists.
Question 650
A small bank has cross-node Pod IP failures as well as DNS failures after changing the network plugin. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a small bank has cross-node Pod IP failures as well as DNS failures after changing the network plugin. Run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. Acceptance evidence: Test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails. This pairing is justified because 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.
Incorrect Answers
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 run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. Its confirming test is to test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
This action and check address the distinct objective “Protect API server access using authenticated TLS clients and audited authorization” instead of the stated acceptance requirement. The matching action is to run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. Its confirming test is to test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
This action and check address the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads” instead of the stated acceptance requirement. The matching action is to run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. Its confirming test is to test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 63 - 10 Questions (Last Reviewed 15-Nov-2026)
- Linux Foundation KCNA Practice Test 64 - 10 Questions (Last Reviewed 14-Nov-2026)
- Linux Foundation KCNA Practice Test 65 - 10 Questions (Last Reviewed 13-Nov-2026)
- Linux Foundation KCNA Practice Test 66 - 10 Questions (Last Reviewed 12-Nov-2026)
- Linux Foundation KCNA Practice Test 67 - 10 Questions (Last Reviewed 11-Nov-2026)