Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 67
Question 660
A data science team sees DiskPressure on a node that stopped starting new containers. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a data science team sees DiskPressure on a node that stopped starting new containers. Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Acceptance evidence: Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible. This pairing is justified because a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.
Incorrect Answers
This action and check address the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” instead of the stated acceptance requirement. The matching action is to inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Its confirming test is to simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.
This action and check address the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors” instead of the stated acceptance requirement. The matching action is to inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Its confirming test is to simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.
This action and check address the distinct objective “Enforce workload service account token boundaries and avoid needless mounts” instead of the stated acceptance requirement. The matching action is to inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Its confirming test is to simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.
Question 661
A public health app needs claim-backed state that survives ordinary Pod replacement. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. This resolves the issue because a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory. To verify, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
Incorrect Answers
This option addresses the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”, not the immediate requirement. A NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid. For the stated case, a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
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, a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
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, a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
Question 662
A public health app needs claim-backed state that survives ordinary Pod replacement. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
A PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory. It supports this action: Request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. To confirm, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
Incorrect Answers
That statement explains the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments” rather than the cause in this case. The deciding mechanism here is that a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
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 a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
That statement explains the distinct objective “Enforce workload service account token boundaries and avoid needless mounts” rather than the cause in this case. The deciding mechanism here is that a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
Question 663
A public health app needs claim-backed state that survives ordinary Pod replacement. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence. This is the relevant test because a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
Incorrect Answers
This check would help evaluate the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules”, but not the required result. For this case, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
This check would help evaluate the distinct objective “Use an immutable image digest for exact deployment provenance”, but not the required result. For this case, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
This check would help evaluate the distinct objective “Understand CSI drivers and volume attachment responsibilities”, but not the required result. For this case, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
Question 664
A public health app needs claim-backed state that survives ordinary Pod replacement. An engineer proposes: “Write critical records to a container filesystem and assume a PVC will be created automatically without any claim.” What adverse outcome would be most direct?
Explanation
Correct Answer
Replacing a Pod can destroy state because no independent persistent volume was requested. The shortcut creates this risk because a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
Incorrect Answers
That outcome concerns the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacing a Pod can destroy state because no independent persistent volume was requested.
That outcome concerns the distinct objective “Understand CSI drivers and volume attachment responsibilities”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacing a Pod can destroy state because no independent persistent volume was requested.
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 replacing a Pod can destroy state because no independent persistent volume was requested.
Question 665
A public health app needs claim-backed state that survives ordinary Pod replacement. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
Request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. Acceptance evidence: Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence. This pairing is justified because a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
Incorrect Answers
This action and check address the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it” instead of the stated acceptance requirement. The matching action is to request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. Its confirming test is to create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
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 request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. Its confirming test is to create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
This action and check address the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk” instead of the stated acceptance requirement. The matching action is to request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. Its confirming test is to create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
Question 666
A college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. What technical action should the platform team take in this situation?
Explanation
Correct Answer
The situation is that a college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. Request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. This resolves the issue because a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory. To verify, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
Incorrect Answers
This option addresses the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk”, not the immediate requirement. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known. For the stated case, a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
This option addresses the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims”, not the immediate requirement. StatefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy. For the stated case, a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
This option addresses the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects”, not the immediate requirement. Open-source community processes provide transparent review and shared maintenance, but do not imply unreviewed external code should be merged into production. For the stated case, a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
Question 667
A college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. A PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory. It supports this action: Request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. To confirm, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
Incorrect Answers
That statement explains the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” rather than the cause in this case. The deciding mechanism here is that a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
That statement explains the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability” rather than the cause in this case. The deciding mechanism here is that a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
That statement explains the distinct objective “Distinguish the CNI Pod network from Service discovery and routing” rather than the cause in this case. The deciding mechanism here is that a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
Question 668
A college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence. This is the relevant test because a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
Incorrect Answers
This check would help evaluate the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk”, but not the required result. For this case, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
This check would help evaluate the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion”, but not the required result. For this case, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
This check would help evaluate the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”, but not the required result. For this case, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
Question 669
A college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. The team suggests: “Write critical records to a container filesystem and assume a PVC will be created automatically without any claim.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. Replacing a Pod can destroy state because no independent persistent volume was requested. The shortcut creates this risk because a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
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 replacing a Pod can destroy state because no independent persistent volume was requested.
The situation is that a college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. That outcome concerns the distinct objective “Understand CSI drivers and volume attachment responsibilities”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacing a Pod can destroy state because no independent persistent volume was requested.
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 replacing a Pod can destroy state because no independent persistent volume was requested.
Question 670
A college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. Request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. Acceptance evidence: Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence. This pairing is justified because a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
Incorrect Answers
This action and check address the distinct objective “Distinguish the CNI Pod network from Service discovery and routing” instead of the stated acceptance requirement. The matching action is to request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. Its confirming test is to create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
This action and check address the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability” instead of the stated acceptance requirement. The matching action is to request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. Its confirming test is to create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
This action and check address the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment” instead of the stated acceptance requirement. The matching action is to request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. Its confirming test is to create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 68 - 10 Questions (Last Reviewed 10-Nov-2026)
- Linux Foundation KCNA Practice Test 69 - 10 Questions (Last Reviewed 09-Nov-2026)