Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 72
Question 710
A school cluster has PVCs referencing a storage system whose CSI node plugin is not running. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a school cluster has PVCs referencing a storage system whose CSI node plugin is not running. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Acceptance evidence: Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload. This pairing is justified because CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.
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 verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Its confirming test is to inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.
The situation is that a school cluster has PVCs referencing a storage system whose CSI node plugin is not running. This action and check address the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims” instead of the stated acceptance requirement. The matching action is to verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Its confirming test is to inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.
The situation is that a school cluster has PVCs referencing a storage system whose CSI node plugin is not running. This action and check address the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods” instead of the stated acceptance requirement. The matching action is to verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Its confirming test is to inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.
Question 711
A regional bank needs a safe cleanup policy for retired report volumes containing sensitive data. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. This resolves the issue because 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. To verify, create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
Incorrect Answers
This option addresses the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources”, not the immediate requirement. A PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory. For the stated case, 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.
This option addresses the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”, not the immediate requirement. Ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding. For the stated case, 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.
This option addresses the distinct objective “Use an immutable image digest for exact deployment provenance”, not the immediate requirement. Tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label. For the stated case, 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.
Question 712
A regional bank needs a safe cleanup policy for retired report volumes containing sensitive data. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
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. It supports this action: Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. To confirm, create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
Incorrect Answers
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 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.
That statement explains the distinct objective “Separate kube-scheduler decisions from kubelet execution” rather than the cause in this case. The deciding mechanism here is that 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.
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 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.
Question 713
A regional bank needs a safe cleanup policy for retired report volumes containing sensitive data. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior. This is the relevant test because 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.
Incorrect Answers
This check would help evaluate the distinct objective “Understand readiness, liveness and startup probes as different signals”, but not the required result. For this case, create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
This check would help evaluate the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods”, but not the required result. For this case, create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
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 disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
Question 714
A regional bank needs a safe cleanup policy for retired report volumes containing sensitive data. The change review contains this proposal: “Assume deleting a Pod deletes every bound persistent disk or that deleting a PVC always preserves customer data indefinitely.” What risk matters most?
Explanation
Correct Answer
Unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies. The shortcut creates this risk because 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.
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 unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.
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 unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.
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 unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.
Question 715
A regional bank needs a safe cleanup policy for retired report volumes containing sensitive data. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Acceptance evidence: Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior. This pairing is justified because 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.
Incorrect Answers
This action and check address the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources” instead of the stated acceptance requirement. The matching action is to review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Its confirming test is to create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
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 review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Its confirming test is to create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
This action and check address the distinct objective “Use labels and selectors to connect resources predictably” instead of the stated acceptance requirement. The matching action is to review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Its confirming test is to create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
Question 716
A college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
The situation is that a college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. This resolves the issue because 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. To verify, create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
Incorrect Answers
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, 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.
This option addresses the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, not the immediate requirement. CNCF maturity describes aspects of adoption and governance, not a blanket guarantee that every deployment or version is free of defects. For the stated case, 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.
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 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.
Question 717
A college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The situation is that a college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. 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. It supports this action: Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. To confirm, create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
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 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.
That statement explains the distinct objective “Separate CI build verification from CD environment promotion” rather than the cause in this case. The deciding mechanism here is that 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.
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 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.
Question 718
A college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
The situation is that a college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior. This is the relevant test because 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.
Incorrect Answers
This check would help evaluate the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims”, but not the required result. For this case, create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
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, create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
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 disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
Question 719
A college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. The change review contains this proposal: “Assume deleting a Pod deletes every bound persistent disk or that deleting a PVC always preserves customer data indefinitely.” What risk matters most?
Explanation
Correct Answer
The situation is that a college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. Unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies. The shortcut creates this risk because 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.
Incorrect Answers
That outcome concerns the distinct objective “Investigate readiness failures separately from liveness-related restarts”; it is not the most direct consequence of this shortcut. The relevant consequence is that unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.
The situation is that a college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. 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 unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.
That outcome concerns the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance”; it is not the most direct consequence of this shortcut. The relevant consequence is that unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.
Question 720
A college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Acceptance evidence: Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior. This pairing is justified because 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.
Incorrect Answers
This action and check address the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure” instead of the stated acceptance requirement. The matching action is to review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Its confirming test is to create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
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 review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Its confirming test is to create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
This action and check address the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence” instead of the stated acceptance requirement. The matching action is to review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Its confirming test is to create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 70 - 10 Questions (Last Reviewed 08-Nov-2026)
- Linux Foundation KCNA Practice Test 71 - 10 Questions (Last Reviewed 07-Nov-2026)
- Linux Foundation KCNA Practice Test 72 - 10 Questions (Last Reviewed 06-Nov-2026)
- Linux Foundation KCNA Practice Test 73 - 10 Questions (Last Reviewed 05-Nov-2026)
- Linux Foundation KCNA Practice Test 74 - 10 Questions (Last Reviewed 04-Nov-2026)