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 67

Question 660

A data science team sees DiskPressure on a node that stopped starting new containers. What pair of supported action and practical verification should be approved?

  1. Route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller. Acceptance evidence: In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
  2. Read Pod Events and node assignment to distinguish a Pod that cannot be scheduled from a scheduled Pod whose image cannot be pulled. Acceptance evidence: Create two controlled faulty workloads, one requiring an impossible node label and one referencing a missing image tag, then compare Events.
  3. Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. Acceptance evidence: Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
  4. Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Acceptance evidence: Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

Explanation

Correct Answer

D:

The situation is that a data science team sees DiskPressure on a node that stopped starting new containers. Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Acceptance evidence: Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible. This pairing is justified because a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

Incorrect Answers

A:

This action and check address the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” instead of the stated acceptance requirement. The matching action is to inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Its confirming test is to simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

B:

This action and check address the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors” instead of the stated acceptance requirement. The matching action is to inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Its confirming test is to simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

C:

This action and check address the distinct objective “Enforce workload service account token boundaries and avoid needless mounts” instead of the stated acceptance requirement. The matching action is to inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Its confirming test is to simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

Question 661

A public health app needs claim-backed state that survives ordinary Pod replacement. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads.
  2. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data.
  3. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling.
  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

D:

Request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. This resolves the issue because a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory. To verify, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.

Incorrect Answers

A:

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, a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.

B:

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 PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.

C:

This option addresses the distinct objective “Explain the container runtime interface without conflating it with the control plane”, not the immediate requirement. A supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface. For the stated case, a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.

Question 662

A public health app needs claim-backed state that survives ordinary Pod replacement. Which platform mechanism explains why the suitable approach works?

  1. A PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
  2. Kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.
  3. CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.
  4. Mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.

Explanation

Correct Answer

A:

A PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory. It supports this action: Request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. To confirm, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.

Incorrect Answers

B:

That statement explains the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments” rather than the cause in this case. The deciding mechanism here is that a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.

C:

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 a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.

D:

That statement explains the distinct objective “Enforce workload service account token boundaries and avoid needless mounts” rather than the cause in this case. The deciding mechanism here is that a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.

Question 663

A public health app needs claim-backed state that survives ordinary Pod replacement. Which controlled observation would best validate the intended improvement?

  1. Test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.
  2. Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
  3. Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
  4. Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

Explanation

Correct Answer

C:

Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence. This is the relevant test 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 check would help evaluate the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules”, but not the required result. For this case, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.

B:

This check would help evaluate the distinct objective “Use an immutable image digest for exact deployment provenance”, but not the required result. For this case, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.

D:

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 small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.

Question 664

A public health app needs claim-backed state that survives ordinary Pod replacement. An engineer proposes: “Write critical records to a container filesystem and assume a PVC will be created automatically without any claim.” What adverse outcome would be most direct?

  1. Controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.
  2. PersistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing.
  3. Replacing a Pod can destroy state because no independent persistent volume was requested.
  4. Unnecessary networking changes can disrupt unrelated services while the original name lookup error persists.

Explanation

Correct Answer

C:

Replacing a Pod can destroy state because no independent persistent volume was requested. The shortcut creates this risk 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:

That outcome concerns the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacing a Pod can destroy state because no independent persistent volume was requested.

B:

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 replacing a Pod can destroy state because no independent persistent volume was requested.

D:

That outcome concerns the distinct objective “Diagnose cluster DNS separately from Pod network reachability”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacing a Pod can destroy state because no independent persistent volume was requested.

Question 665

A public health app needs claim-backed state that survives ordinary Pod replacement. What pair of supported action and practical verification should be approved?

  1. Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Acceptance evidence: Check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
  2. Inspect kubelet-reported Pod and container conditions when a scheduled workload fails to start, while keeping cluster resources managed through the API. Acceptance evidence: Describe a scheduled Pod with ImagePullBackOff and compare its assigned node against kubelet-related Events.
  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. 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.

Explanation

Correct Answer

D:

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 “Recognize NetworkPolicy isolation only when the CNI enforces it” 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 “Recognize the kubelet role in local Pod lifecycle management” 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.

C:

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

A college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. What technical action should the platform team take in this situation?

  1. Request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod.
  2. Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC.
  3. Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes.
  4. Follow a project's published governance, issue templates, contributor guides and code of conduct when reporting bugs or proposing changes.

Explanation

Correct Answer

A:

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. This resolves the issue because a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory. To verify, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.

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, a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.

C:

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 PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.

D:

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 PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.

Question 667

A college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. A PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.
  2. Declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
  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. Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.

Explanation

Correct Answer

A:

The situation is that a college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. A PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory. It supports this action: Request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. To confirm, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.

Incorrect Answers

B:

That statement explains the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” rather than the cause in this case. The deciding mechanism here is that a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.

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 PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.

D:

That statement explains the distinct objective “Distinguish the CNI Pod network from Service discovery and routing” rather than the cause in this case. The deciding mechanism here is that a PVC requests storage and binds to a compatible PV; the Pod references the namespaced claim rather than assuming a fixed node directory.

Question 668

A college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. What acceptance check most directly confirms this requirement is met?

  1. Create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
  2. Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
  3. Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
  4. Run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

Explanation

Correct Answer

B:

The situation is that a college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence. This is the relevant test 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 check would help evaluate the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk”, but not the required result. For this case, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.

C:

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, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.

D:

This check would help evaluate the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”, but not the required result. For this case, create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.

Question 669

A college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. The team suggests: “Write critical records to a container filesystem and assume a PVC will be created automatically without any claim.” Which failure should the reviewer anticipate?

  1. Healthy desired-state definitions are lost while the node connectivity or capacity cause remains unresolved.
  2. Replacing a Pod can destroy state because no independent persistent volume was requested.
  3. PersistentVolumeClaims remain Pending or Pods fail to mount because the required driver integration is missing.
  4. The application never becomes operational because packaging metadata is confused with cluster reconciliation.

Explanation

Correct Answer

B:

The situation is that a college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. Replacing a Pod can destroy state because no independent persistent volume was requested. The shortcut creates this risk 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:

That outcome concerns the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacing a Pod can destroy state because no independent persistent volume was requested.

C:

The situation is that a college experiment creates a database Pod but forgets to define any PersistentVolumeClaim. 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 replacing a Pod can destroy state because no independent persistent volume was requested.

D:

That outcome concerns the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”; it is not the most direct consequence of this shortcut. The relevant consequence is that replacing a Pod can destroy state because no independent persistent volume was requested.

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.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests