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 69

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.

Question 681

A small bank needs one transactional database writer on a block disk. What technical action should the platform team take in this situation?

  1. 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.
  2. Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC.
  3. Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane.
  4. Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped.

Explanation

Correct Answer

A:

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. This resolves the issue 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. To verify, use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.

Incorrect Answers

B:

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, PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.

C:

This option addresses the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”, not the immediate requirement. Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. For the stated case, PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.

D:

This option addresses the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, not the immediate requirement. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller. For the stated case, PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.

Question 682

A small bank needs one transactional database writer on a block disk. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.
  2. Continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.
  3. StatefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
  4. Healthy direct IP connectivity with failed name resolution suggests a DNS path issue; failed Pod-to-Pod IP traffic suggests a lower-level network problem.

Explanation

Correct Answer

A:

PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend. It supports this action: 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. To confirm, use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.

Incorrect Answers

B:

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 PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.

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 PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.

D:

That statement explains the distinct objective “Diagnose cluster DNS separately from Pod network reachability” rather than the cause in this case. The deciding mechanism here is that PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.

Question 683

A small bank needs one transactional database writer on a block disk. What acceptance check most directly confirms this requirement is met?

  1. Deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.
  2. Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
  3. Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
  4. Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.

Explanation

Correct Answer

C:

Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem. This is the relevant test 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

A:

This check would help evaluate the distinct objective “Correlate application rollout revisions with error spikes”, but not the required result. For this case, use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.

B:

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, use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.

D:

This check would help evaluate the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources”, but not the required result. For this case, use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.

Question 684

A small bank needs one transactional database writer on a block disk. The team suggests: “Mount a single node-attached block disk read-write on two different worker nodes simply by changing the PVC accessModes to ReadWriteMany.” Which failure should the reviewer anticipate?

  1. The operator may deploy unsupported changes without release provenance or a responsible maintenance path.
  2. Replicas can collide on storage ownership and application state ordering assumptions fail.
  3. Volume attachment fails or concurrent access risks data integrity when the backend cannot provide shared semantics.
  4. Pods may start but remain unable to communicate across nodes because the CNI dataplane was never established.

Explanation

Correct Answer

C:

Volume attachment fails or concurrent access risks data integrity when the backend cannot provide shared semantics. The shortcut creates this risk 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

A:

That outcome concerns the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects”; it is not the most direct consequence of this shortcut. The relevant consequence is that volume attachment fails or concurrent access risks data integrity when the backend cannot provide shared semantics.

B:

That outcome concerns the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims”; it is not the most direct consequence of this shortcut. The relevant consequence is that volume attachment fails or concurrent access risks data integrity when the backend cannot provide shared semantics.

D:

That outcome concerns the distinct objective “Distinguish the CNI Pod network from Service discovery and routing”; it is not the most direct consequence of this shortcut. The relevant consequence is that volume attachment fails or concurrent access risks data integrity when the backend cannot provide shared semantics.

Question 685

A small bank needs one transactional database writer on a block disk. Which engineering change and test jointly addresses the scenario?

  1. Grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. Acceptance evidence: With restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.
  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. Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Acceptance evidence: Test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
  4. 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.

Explanation

Correct Answer

B:

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

A:

This action and check address the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration” 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.

C:

This action and check address the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees” 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.

D:

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 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 686

A community library wants several read/write application replicas to share documents through supported network storage. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count.
  2. Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads.
  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.
  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

C:

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. This resolves the issue 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. To verify, use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.

Incorrect Answers

A:

This option addresses the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”, not the immediate requirement. A Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts. For the stated case, PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.

B:

This option addresses the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”, not the immediate requirement. A NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid. For the stated case, PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.

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, PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.

Question 687

A community library wants several read/write application replicas to share documents through supported network storage. Which platform mechanism explains why the suitable approach works?

  1. Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
  2. PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.
  3. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
  4. A NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

Explanation

Correct Answer

B:

The situation is that a community library wants several read/write application replicas to share documents through supported network storage. PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend. It supports this action: 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. To confirm, use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.

Incorrect Answers

A:

That statement explains the distinct objective “Use labels and selectors to connect resources predictably” rather than the cause in this case. The deciding mechanism here is that PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.

C:

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 PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.

D:

That statement explains the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads” rather than the cause in this case. The deciding mechanism here is that PV access modes express volume mount constraints and driver support; ReadWriteOnce normally restricts writable use to one node, while ReadWriteMany requires a capable backend.

Question 688

A community library wants several read/write application replicas to share documents through supported network storage. Which controlled observation would best validate the intended improvement?

  1. Bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.
  2. Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
  3. Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.
  4. Deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.

Explanation

Correct Answer

B:

The situation is that a community library wants several read/write application replicas to share documents through supported network storage. Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem. This is the relevant test 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

A:

This check would help evaluate the distinct objective “Distinguish ClusterRoles from Roles and binding scope”, but not the required result. For this case, use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.

C:

This check would help evaluate the distinct objective “Understand CSI drivers and volume attachment responsibilities”, but not the required result. For this case, use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.

D:

This check would help evaluate the distinct objective “Design a release rollback trigger from measurable service signals”, but not the required result. For this case, use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.

Question 689

A community library wants several read/write application replicas to share documents through supported network storage. An engineer proposes: “Mount a single node-attached block disk read-write on two different worker nodes simply by changing the PVC accessModes to ReadWriteMany.” What adverse outcome would be most direct?

  1. The Service still has no ready endpoints and clients continue to encounter unavailable responses.
  2. Replacing a Pod can destroy state because no independent persistent volume was requested.
  3. Volume attachment fails or concurrent access risks data integrity when the backend cannot provide shared semantics.
  4. The planned maintenance causes avoidable downtime because no safe application replica remains available.

Explanation

Correct Answer

C:

The situation is that a community library wants several read/write application replicas to share documents through supported network storage. Volume attachment fails or concurrent access risks data integrity when the backend cannot provide shared semantics. The shortcut creates this risk 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

A:

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 volume attachment fails or concurrent access risks data integrity when the backend cannot provide shared semantics.

B:

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 volume attachment fails or concurrent access risks data integrity when the backend cannot provide shared semantics.

D:

That outcome concerns the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance”; it is not the most direct consequence of this shortcut. The relevant consequence is that volume attachment fails or concurrent access risks data integrity when the backend cannot provide shared semantics.

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?

  1. 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.
  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. Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Acceptance evidence: Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
  4. Define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. Acceptance evidence: Deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.

Explanation

Correct Answer

A:

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

B:

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.

C:

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.

D:

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.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests