Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 68
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.
Question 671
A retailer wants new database claims provisioned automatically by a managed disk driver. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC. This resolves the issue because a StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known. To verify, create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
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, a StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
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 StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
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 StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
Question 672
A retailer wants new database claims provisioned automatically by a managed disk driver. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known. It supports this action: Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC. To confirm, create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
Incorrect Answers
That statement explains the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership” rather than the cause in this case. The deciding mechanism here is that a StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
That statement explains the distinct objective “Use image provenance and policy controls without trusting mutable tags” rather than the cause in this case. The deciding mechanism here is that a StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
That statement explains the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims” rather than the cause in this case. The deciding mechanism here is that a StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
Question 673
A retailer wants new database claims provisioned automatically by a managed disk driver. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
Create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class. This is the relevant test because a StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
Incorrect Answers
This check would help evaluate the distinct objective “Explain metrics, logs and traces as complementary observability signals”, but not the required result. For this case, create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
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 claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
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 claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
Question 674
A retailer wants new database claims provisioned automatically by a managed disk driver. A shortcut is proposed: “Specify a StorageClass name that no storage provisioner supports and expect the PVC to become Bound instantly.” Which technical consequence follows most closely?
Explanation
Correct Answer
The claim remains Pending and dependent Pods cannot mount the missing volume. The shortcut creates this risk because a StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
Incorrect Answers
That outcome concerns the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability”; it is not the most direct consequence of this shortcut. The relevant consequence is that the claim remains Pending and dependent Pods cannot mount the missing volume.
That outcome concerns the distinct objective “Use rollout status and undo to validate and recover a Deployment release”; it is not the most direct consequence of this shortcut. The relevant consequence is that the claim remains Pending and dependent Pods cannot mount the missing volume.
That outcome concerns the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion”; it is not the most direct consequence of this shortcut. The relevant consequence is that the claim remains Pending and dependent Pods cannot mount the missing volume.
Question 675
A retailer wants new database claims provisioned automatically by a managed disk driver. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC. Acceptance evidence: Create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class. This pairing is justified because a StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
Incorrect Answers
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 choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC. Its confirming test is to create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
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 choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC. Its confirming test is to create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
This action and check address the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs” instead of the stated acceptance requirement. The matching action is to choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC. Its confirming test is to create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
Question 676
A university cluster defines a topology-aware StorageClass but a workload references an old unsupported class name. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
The situation is that a university cluster defines a topology-aware StorageClass but a workload references an old unsupported class name. Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC. This resolves the issue because a StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known. To verify, create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
Incorrect Answers
This option addresses the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”, not the immediate requirement. A DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count. For the stated case, a StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
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 StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
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 StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
Question 677
A university cluster defines a topology-aware StorageClass but a workload references an old unsupported class name. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
The situation is that a university cluster defines a topology-aware StorageClass but a workload references an old unsupported class name. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known. It supports this action: Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC. To confirm, create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
Incorrect Answers
That statement explains the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods” rather than the cause in this case. The deciding mechanism here is that a StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
That statement explains the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects” rather than the cause in this case. The deciding mechanism here is that a StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
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 StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
Question 678
A university cluster defines a topology-aware StorageClass but a workload references an old unsupported class name. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
The situation is that a university cluster defines a topology-aware StorageClass but a workload references an old unsupported class name. Create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class. This is the relevant test because a StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
Incorrect Answers
This check would help evaluate the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability”, but not the required result. For this case, create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
This check would help evaluate the distinct objective “Distinguish the CNI Pod network from Service discovery and routing”, but not the required result. For this case, create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
This check would help evaluate the distinct objective “Understand Prometheus pull-based metrics collection and exporters”, but not the required result. For this case, create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
Question 679
A university cluster defines a topology-aware StorageClass but a workload references an old unsupported class name. A shortcut is proposed: “Specify a StorageClass name that no storage provisioner supports and expect the PVC to become Bound instantly.” Which technical consequence follows most closely?
Explanation
Correct Answer
The situation is that a university cluster defines a topology-aware StorageClass but a workload references an old unsupported class name. The claim remains Pending and dependent Pods cannot mount the missing volume. The shortcut creates this risk because a StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
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 the claim remains Pending and dependent Pods cannot mount the missing volume.
That outcome concerns the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”; it is not the most direct consequence of this shortcut. The relevant consequence is that the claim remains Pending and dependent Pods cannot mount the missing volume.
That outcome concerns the distinct objective “Run images with least-privilege runtime security contexts”; it is not the most direct consequence of this shortcut. The relevant consequence is that the claim remains Pending and dependent Pods cannot mount the missing volume.
Question 680
A university cluster defines a topology-aware StorageClass but a workload references an old unsupported class name. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
The situation is that a university cluster defines a topology-aware StorageClass but a workload references an old unsupported class name. Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC. Acceptance evidence: Create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class. This pairing is justified because a StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
Incorrect Answers
This action and check address the distinct objective “Run images with least-privilege runtime security contexts” instead of the stated acceptance requirement. The matching action is to choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC. Its confirming test is to create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
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 choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC. Its confirming test is to create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
The situation is that a university cluster defines a topology-aware StorageClass but a workload references an old unsupported class name. 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 choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC. Its confirming test is to create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 70 - 10 Questions (Last Reviewed 08-Nov-2026)