Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 70
Question 690
A community library wants several read/write application replicas to share documents through supported network storage. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a community library wants several read/write application replicas to share documents through supported network storage. Select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node. Acceptance evidence: Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem. This pairing is justified because PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.
Incorrect Answers
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 select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node. Its confirming test is to use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
This action and check address the distinct objective “Distinguish etcd persistence from running workload data” instead of the stated acceptance requirement. The matching action is to select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node. Its confirming test is to use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
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 select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node. Its confirming test is to use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
Question 691
A university runs a small stateful training database cluster whose members need persistent identities. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. This resolves the issue because statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy. To verify, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
Incorrect Answers
This option addresses the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions”, not the immediate requirement. Pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules. For the stated case, statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
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, statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
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, statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
Question 692
A university runs a small stateful training database cluster whose members need persistent identities. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
StatefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy. It supports this action: Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. To confirm, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
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 statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
That statement explains the distinct objective “Design a release rollback trigger from measurable service signals” rather than the cause in this case. The deciding mechanism here is that statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
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 statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
Question 693
A university runs a small stateful training database cluster whose members need persistent identities. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod. This is the relevant test because statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
Incorrect Answers
This check would help evaluate the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”, but not the required result. For this case, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
This check would help evaluate the distinct objective “Understand CSI drivers and volume attachment responsibilities”, but not the required result. For this case, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
This check would help evaluate the distinct objective “Use annotations for tool metadata rather than workload selection”, but not the required result. For this case, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
Question 694
A university runs a small stateful training database cluster whose members need persistent identities. An engineer proposes: “Use a Deployment with one shared writable volume and assume every stateful replica receives its own independent identity and durable disk.” What adverse outcome would be most direct?
Explanation
Correct Answer
Replicas can collide on storage ownership and application state ordering assumptions fail. The shortcut creates this risk because statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
Incorrect Answers
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 replicas can collide on storage ownership and application state ordering assumptions fail.
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 replicas can collide on storage ownership and application state ordering assumptions fail.
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 replicas can collide on storage ownership and application state ordering assumptions fail.
Question 695
A university runs a small stateful training database cluster whose members need persistent identities. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Acceptance evidence: Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod. This pairing is justified because statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
Incorrect Answers
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 select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Its confirming test is to scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
This action and check address the distinct objective “Define secure release governance with staged approvals and policy verification” instead of the stated acceptance requirement. The matching action is to select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Its confirming test is to scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
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 select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Its confirming test is to scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
Question 696
A hospital analytics service has three durable replicas that should not overwrite a shared data directory. What technical action should the platform team take in this situation?
Explanation
Correct Answer
The situation is that a hospital analytics service has three durable replicas that should not overwrite a shared data directory. Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. This resolves the issue because statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy. To verify, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
Incorrect Answers
This option addresses the distinct objective “Understand CSI drivers and volume attachment responsibilities”, not the immediate requirement. CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities. For the stated case, statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
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, statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
This option addresses the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, not the immediate requirement. FailedScheduling occurs before node binding; ImagePullBackOff occurs when a node's kubelet cannot obtain the container image. For the stated case, statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
Question 697
A hospital analytics service has three durable replicas that should not overwrite a shared data directory. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a hospital analytics service has three durable replicas that should not overwrite a shared data directory. StatefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy. It supports this action: Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. To confirm, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
Incorrect Answers
That statement explains the distinct objective “Understand readiness, liveness and startup probes as different signals” rather than the cause in this case. The deciding mechanism here is that statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
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 statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
The situation is that a hospital analytics service has three durable replicas that should not overwrite a shared data directory. 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 statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
Question 698
A hospital analytics service has three durable replicas that should not overwrite a shared data directory. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a hospital analytics service has three durable replicas that should not overwrite a shared data directory. Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod. This is the relevant test because statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
Incorrect Answers
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, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
The situation is that a hospital analytics service has three durable replicas that should not overwrite a shared data directory. This check would help evaluate the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”, but not the required result. For this case, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
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, scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
Question 699
A hospital analytics service has three durable replicas that should not overwrite a shared data directory. The team suggests: “Use a Deployment with one shared writable volume and assume every stateful replica receives its own independent identity and durable disk.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a hospital analytics service has three durable replicas that should not overwrite a shared data directory. Replicas can collide on storage ownership and application state ordering assumptions fail. The shortcut creates this risk because statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
Incorrect Answers
That outcome concerns the distinct objective “Externalize application configuration from an image while protecting secrets”; it is not the most direct consequence of this shortcut. The relevant consequence is that replicas can collide on storage ownership and application state ordering assumptions fail.
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 replicas can collide on storage ownership and application state ordering assumptions fail.
That outcome concerns the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions”; it is not the most direct consequence of this shortcut. The relevant consequence is that replicas can collide on storage ownership and application state ordering assumptions fail.
Question 700
A hospital analytics service has three durable replicas that should not overwrite a shared data directory. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a hospital analytics service has three durable replicas that should not overwrite a shared data directory. Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Acceptance evidence: Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod. This pairing is justified because statefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
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 select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Its confirming test is to scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
The situation is that a hospital analytics service has three durable replicas that should not overwrite a shared data directory. This action and check address the distinct objective “Define secure release governance with staged approvals and policy verification” instead of the stated acceptance requirement. The matching action is to select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Its confirming test is to scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
This action and check address the distinct objective “Use image provenance and policy controls without trusting mutable tags” instead of the stated acceptance requirement. The matching action is to select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Its confirming test is to scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- 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)