Practice Exams:

Linux Foundation KCNA Dumps

EXAM: Kubernetes and Cloud Native Associate
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

KCNA Premium Bundle


  • Premium File 333 Questions & Answers
  • Training Course 54 Lectures
  • Study Guide 410 Pages

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?

  1. Check that a supported CNI plugin assigns reachable Pod addresses across worker nodes before troubleshooting Service routing or DNS names. Acceptance evidence: Deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
  2. 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.
  3. 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.
  4. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Acceptance evidence: Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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?

  1. Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC.
  2. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails.
  3. Follow a project's published governance, issue templates, contributor guides and code of conduct when reporting bugs or proposing changes.
  4. Request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod.

Explanation

Correct Answer

A:

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

B:

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.

C:

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.

D:

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?

  1. Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
  2. Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
  3. StatefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
  4. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. Send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.
  2. Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.
  3. Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
  4. Create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. The change unnecessarily exposes a data service externally while the original DNS problem remains unresolved.
  2. The claim remains Pending and dependent Pods cannot mount the missing volume.
  3. A failed release can leave the service unavailable with no retained tested deployment revision.
  4. Unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Acceptance evidence: Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
  2. 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.
  3. 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.
  4. Inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup. Acceptance evidence: Run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance.
  2. Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes.
  3. Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC.
  4. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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?

  1. EndpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
  2. Open-source community processes provide transparent review and shared maintenance, but do not imply unreviewed external code should be merged into production.
  3. PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.
  4. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
  2. Deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
  3. Verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
  4. Create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. PersistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing.
  2. The route remains nonfunctional because nothing reconciles it into an application traffic proxy.
  3. The claim remains Pending and dependent Pods cannot mount the missing volume.
  4. Containers gain broad host exposure and compromise blast radius becomes larger than the application's needs.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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?

  1. Set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root. Acceptance evidence: Deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
  2. 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.
  3. 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.
  4. 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.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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