Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 64
Question 630
A hospital reports restart loops after making a liveness probe more aggressive than application initialization. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a hospital reports restart loops after making a liveness probe more aggressive than application initialization. Inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. Acceptance evidence: Induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure. This pairing is justified because a failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.
Incorrect Answers
The situation is that a hospital reports restart loops after making a liveness probe more aggressive than application initialization. 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 inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. Its confirming test is to induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.
This action and check address the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point” instead of the stated acceptance requirement. The matching action is to inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. Its confirming test is to induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.
This action and check address the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability” instead of the stated acceptance requirement. The matching action is to inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. Its confirming test is to induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.
Question 631
A library's records service stays in ContainerCreating with a FailedMount warning. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. This resolves the issue because kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure. To verify, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
Incorrect Answers
This option addresses the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”, not the immediate requirement. A namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces. For the stated case, kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
This option addresses the distinct objective “Diagnose cluster DNS separately from Pod network reachability”, not the immediate requirement. 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. For the stated case, kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
This option addresses the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”, not the immediate requirement. Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. For the stated case, kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
Question 632
A library's records service stays in ContainerCreating with a FailedMount warning. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure. It supports this action: Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. To confirm, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
Incorrect Answers
That statement explains the distinct objective “Diagnose cluster DNS separately from Pod network reachability” rather than the cause in this case. The deciding mechanism here is that kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
That statement explains the distinct objective “Understand ports, targetPort and protocol mapping in a Service” rather than the cause in this case. The deciding mechanism here is that kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
That statement explains the distinct objective “Distinguish service mesh traffic management from external ingress routing” rather than the cause in this case. The deciding mechanism here is that kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
Question 633
A library's records service stays in ContainerCreating with a FailedMount warning. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim. This is the relevant test because kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
Incorrect Answers
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, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
This check would help evaluate the distinct objective “Investigate readiness failures separately from liveness-related restarts”, but not the required result. For this case, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
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, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
Question 634
A library's records service stays in ContainerCreating with a FailedMount warning. An engineer proposes: “Modify container application code to skip its database initialization when the real problem is an unbound PVC.” What adverse outcome would be most direct?
Explanation
Correct Answer
A workload remains nonfunctional and the persistent data dependency is never satisfied. The shortcut creates this risk because kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
Incorrect Answers
That outcome concerns the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload remains nonfunctional and the persistent data dependency is never satisfied.
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 a workload remains nonfunctional and the persistent data dependency is never satisfied.
That outcome concerns the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload remains nonfunctional and the persistent data dependency is never satisfied.
Question 635
A library's records service stays in ContainerCreating with a FailedMount warning. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
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
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 “Read the API resource model using namespaces and names rather than guessing ownership” 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 “Diagnose cluster DNS separately from Pod network reachability” 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 636
A research group creates a Pod that references a PersistentVolumeClaim in another namespace. Which engineering approach is the most appropriate for this cloud-native 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. This resolves the issue because kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure. To verify, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
Incorrect Answers
This option addresses the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”, not the immediate requirement. CrashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe. For the stated case, kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
This option addresses the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion”, not the immediate requirement. A PV reclaim policy controls how underlying storage is treated after claim release; deleting the Pod and deleting the PVC are distinct events with different effects. For the stated case, kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
This option addresses the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”, not the immediate requirement. A kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment. For the stated case, kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
Question 637
A research group creates a Pod that references a PersistentVolumeClaim in another namespace. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure. It supports this action: Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. To confirm, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
Incorrect Answers
That statement explains the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it” rather than the cause in this case. The deciding mechanism here is that kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. That statement explains the distinct objective “Distinguish service mesh traffic management from external ingress routing” rather than the cause in this case. The deciding mechanism here is that kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
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 kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
Question 638
A research group creates a Pod that references a PersistentVolumeClaim in another namespace. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. Reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim. This is the relevant test 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 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, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. This check would help evaluate the distinct objective “Investigate readiness failures separately from liveness-related restarts”, but not the required result. For this case, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
This check would help evaluate the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”, but not the required result. For this case, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
Question 639
A research group creates a Pod that references a PersistentVolumeClaim in another namespace. The change review contains this proposal: “Modify container application code to skip its database initialization when the real problem is an unbound PVC.” What risk matters most?
Explanation
Correct Answer
The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. A workload remains nonfunctional and the persistent data dependency is never satisfied. The shortcut creates this risk 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. That outcome concerns the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload remains nonfunctional and the persistent data dependency is never satisfied.
That outcome concerns the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload remains nonfunctional and the persistent data dependency is never satisfied.
That outcome concerns the distinct objective “Use nodeSelector to place a workload on nodes with required labels”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload remains nonfunctional and the persistent data dependency is never satisfied.
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.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 62 - 10 Questions (Last Reviewed 16-Nov-2026)
- 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)