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 72

Question 710

A school cluster has PVCs referencing a storage system whose CSI node plugin is not running. Which engineering change and test jointly addresses the scenario?

  1. Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. Acceptance evidence: In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.
  2. 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.
  3. Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Acceptance evidence: Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
  4. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Acceptance evidence: Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

Explanation

Correct Answer

D:

The situation is that a school cluster has PVCs referencing a storage system whose CSI node plugin is not running. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Acceptance evidence: Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload. This pairing is justified because CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.

Incorrect Answers

A:

This action and check address the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards” instead of the stated acceptance requirement. The matching action is to verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Its confirming test is to inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

B:

The situation is that a school cluster has PVCs referencing a storage system whose CSI node plugin is not running. 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 verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Its confirming test is to inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

C:

The situation is that a school cluster has PVCs referencing a storage system whose CSI node plugin is not running. This action and check address the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods” instead of the stated acceptance requirement. The matching action is to verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Its confirming test is to inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

Question 711

A regional bank needs a safe cleanup policy for retired report volumes containing sensitive data. Which engineering approach is the most appropriate for this cloud-native case?

  1. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data.
  2. Request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod.
  3. Define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy.
  4. Pin validated production images by registry digest and promote the same signed artifact across environments.

Explanation

Correct Answer

A:

Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. This resolves the issue because 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. To verify, create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

Incorrect Answers

B:

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

C:

This option addresses the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”, not the immediate requirement. Ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding. For the stated case, 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.

D:

This option addresses the distinct objective “Use an immutable image digest for exact deployment provenance”, not the immediate requirement. Tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label. For the stated case, 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.

Question 712

A regional bank needs a safe cleanup policy for retired report volumes containing sensitive data. What infrastructure principle makes the correct treatment effective?

  1. A Service exposes port to clients and forwards to targetPort on selected endpoints; a mismatched targetPort can break delivery even with valid DNS and selectors.
  2. The scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.
  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 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.

Explanation

Correct Answer

D:

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. It supports this action: Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. To confirm, create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

Incorrect Answers

A:

That statement explains the distinct objective “Understand ports, targetPort and protocol mapping in a Service” rather than the cause in this case. The deciding mechanism here is that 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.

B:

That statement explains the distinct objective “Separate kube-scheduler decisions from kubelet execution” rather than the cause in this case. The deciding mechanism here is that 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.

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

Question 713

A regional bank needs a safe cleanup policy for retired report volumes containing sensitive data. What verification result would most convincingly distinguish a working solution from a claim?

  1. Delay a synthetic app response and compare EndpointSlice readiness with restart counts under controlled probe settings.
  2. Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
  3. Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
  4. Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.

Explanation

Correct Answer

B:

Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior. This is the relevant test because 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.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Understand readiness, liveness and startup probes as different signals”, but not the required result. For this case, create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

C:

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, create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

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 disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

Question 714

A regional bank needs a safe cleanup policy for retired report volumes containing sensitive data. The change review contains this proposal: “Assume deleting a Pod deletes every bound persistent disk or that deleting a PVC always preserves customer data indefinitely.” What risk matters most?

  1. Unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.
  2. A trusted community label is misused as a substitute for secure configuration and maintenance.
  3. Requests fail after a replica is replaced because the client bypassed the Service abstraction.
  4. Replacing a Pod can destroy state because no independent persistent volume was requested.

Explanation

Correct Answer

A:

Unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies. The shortcut creates this risk because 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.

Incorrect Answers

B:

That outcome concerns the distinct objective “Understand CNCF project maturity stages without equating them to security approval”; it is not the most direct consequence of this shortcut. The relevant consequence is that unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.

C:

That outcome concerns the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”; it is not the most direct consequence of this shortcut. The relevant consequence is that unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.

D:

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 unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.

Question 715

A regional bank needs a safe cleanup policy for retired report volumes containing sensitive data. Which implementation together with matching acceptance evidence best meets this case?

  1. 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.
  2. 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.
  3. Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Acceptance evidence: Compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
  4. 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.

Explanation

Correct Answer

D:

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. This pairing is justified because 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.

Incorrect Answers

A:

This action and check address the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources” instead of the stated acceptance requirement. The matching action is to review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Its confirming test is to create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

B:

This action and check address the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads” instead of the stated acceptance requirement. The matching action is to review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Its confirming test is to create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

C:

This action and check address the distinct objective “Use labels and selectors to connect resources predictably” instead of the stated acceptance requirement. The matching action is to review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Its confirming test is to create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

Question 716

A college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. Which engineering approach is the most appropriate for this cloud-native case?

  1. Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code.
  2. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data.
  3. Review Sandbox, Incubating and Graduated CNCF stages as community maturity signals while independently assessing a project's fitness, lifecycle and security.
  4. Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes.

Explanation

Correct Answer

B:

The situation is that a college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. This resolves the issue because 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. To verify, create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

Incorrect Answers

A:

This option addresses the distinct objective “Use Events and pod describe for failed volume mounting”, not the immediate requirement. Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure. For the stated case, 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.

C:

This option addresses the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, not the immediate requirement. CNCF maturity describes aspects of adoption and governance, not a blanket guarantee that every deployment or version is free of defects. For the stated case, 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.

D:

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

Question 717

A college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. What infrastructure principle makes the correct treatment effective?

  1. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known.
  2. Continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.
  3. 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.
  4. NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.

Explanation

Correct Answer

C:

The situation is that a college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. 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. It supports this action: Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. To confirm, create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

Incorrect Answers

A:

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

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

D:

That statement explains the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it” rather than the cause in this case. The deciding mechanism here is that 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.

Question 718

A college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. What verification result would most convincingly distinguish a working solution from a claim?

  1. Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
  2. Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.
  3. Create synthetic invalid quota, unschedulable node and missing-image cases and compare their event reasons and assigned node status.
  4. Create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.

Explanation

Correct Answer

B:

The situation is that a college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior. This is the relevant test because 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.

Incorrect Answers

A:

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 disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

C:

This check would help evaluate the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors”, but not the required result. For this case, create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

D:

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 disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

Question 719

A college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. The change review contains this proposal: “Assume deleting a Pod deletes every bound persistent disk or that deleting a PVC always preserves customer data indefinitely.” What risk matters most?

  1. Unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.
  2. The Service still has no ready endpoints and clients continue to encounter unavailable responses.
  3. Replacing a Pod can destroy state because no independent persistent volume was requested.
  4. A project can exhaust shared cluster capacity when declarative metadata is mistaken for enforced admission policy.

Explanation

Correct Answer

A:

The situation is that a college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. Unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies. The shortcut creates this risk because 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.

Incorrect Answers

B:

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 unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.

C:

The situation is that a college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. 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 unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.

D:

That outcome concerns the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance”; it is not the most direct consequence of this shortcut. The relevant consequence is that unexpected data loss or orphaned sensitive volumes can result from misunderstanding reclaim and retention policies.

Question 720

A college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. Which implementation together with matching acceptance evidence best meets this case?

  1. 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.
  2. 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.
  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. Use emptyDir for temporary sharing between containers within a Pod, and PVC-backed storage when data must survive Pod replacement. Acceptance evidence: Write a synthetic temporary file into emptyDir, restart a container and then recreate the Pod to compare lifetime semantics.

Explanation

Correct Answer

A:

The situation is that a college test deletes a StatefulSet Pod and expects its PVC to be gone without an explicit retention check. 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. This pairing is justified because 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.

Incorrect Answers

B:

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 review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Its confirming test is to create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

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 review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Its confirming test is to create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

D:

This action and check address the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence” instead of the stated acceptance requirement. The matching action is to review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Its confirming test is to create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests