McAfee Secure

CNCF CKA Bundle

Exam Code: CKA

Exam Name Certified Kubernetes Administrator

Certification Provider: CNCF

Corresponding Certification: CKA

CNCF CKA Bundle $44.99
CKA Sample 1 CKA Sample 2 CKA Sample 3 CKA Sample 4 CKA Sample 5 CKA Sample 6 CKA Sample 7 CKA Sample 8 CKA Sample 9 CKA Sample 10

100% CNCF CKA Guaranteed Success With Testking Training Materials

Get Real CKA Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    CKA Questions & Answers

    58 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual CKA exam while allowing you to hone and measure every aspect of your test-taking ability.

  • CKA Video Course

    CKA Training Course

    138 Video Lectures

    CKA Video Course is developed by CNCF Professionals to help you pass the CKA exam.

    Description

    This course will improve your knowledge and skills required to pass Certified Kubernetes Administrator exam.
  • Study Guide

    CKA Study Guide

    268 PDF Pages

    Developed by industry experts, this 268-page guide spells out in painstaking detail all of the information you need to ace CKA exam.

Certified Kubernetes Administrator (CKA) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    58 Questions

    $124.99
  • CKA Video Course

    Training Course

    138 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    268 PDF Pages

    $29.99

CNCF CKA Practice Test 77

Question 760

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: The lab must designate StorageClass fast-block as default after existing default classes have been intentionally cleared. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Treat changing default storage provisioning as a cluster-wide controlled operation.
  2. Verify expansion support and back up data before resizing important volumes.
  3. Periodically restore test snapshots and verify backup consistency for the application.
  4. Maintain validated StorageClass definitions and review CSI driver compatibility during upgrades.

Explanation

Correct Answer

A:

Treat changing default storage provisioning as a cluster-wide controlled operation. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl annotate storageclass fast-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default. The relevant mechanism is: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior.

Incorrect Answers

B:

This routine guards against another mechanism: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The recurring exposure in the current case is: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The matching preventive check is “Treat changing default storage provisioning as a cluster-wide controlled operation”.

C:

The suggested review tracks a different technical risk: VolumeSnapshot is a CSI extension object rather than a core PVC backup; controller and driver capabilities determine success. Here the sustained control must address: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. Choose “Treat changing default storage provisioning as a cluster-wide controlled operation”.

D:

That safeguard is relevant to: StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults. The current failure instead follows from: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. Its prevention measure is “Treat changing default storage provisioning as a cluster-wide controlled operation”.

Question 761

At Horizon observability, in a disposable simulated environment during a monitored release window: The lab must designate StorageClass balanced-block as default after existing default classes have been intentionally cleared. Work only within the stated target and verify before declaring success. Which command or initial safe diagnostic step best addresses the stated lab task?

  1. Run kubectl -n ledger apply -f ./storage/invoice-api-pvc.yaml after confirming storageClassName: fast-block and requested capacity 5Gi.
  2. Run kubectl -n observability apply -f ./storage/metrics-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites.
  3. Run kubectl annotate storageclass balanced-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default.
  4. Run kubectl -n fulfillment apply -f ./storage/dispatch-api-pvc.yaml after confirming storageClassName: standard-block and requested capacity 20Gi.

Explanation

Correct Answer

C:

Run kubectl annotate storageclass balanced-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default. This is the appropriate command-line action or first safe diagnostic. The technical reason is: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. Validate the result with: Run kubectl get storageclass and confirm the intended single default annotation. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

A:

This alternative is a response to another technical cause: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. The reported case instead depends on: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The action that directly addresses it is “Run kubectl annotate storageclass balanced-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default”.

B:

The proposed action belongs to the mechanism: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. Here the stated fault follows a different mechanism: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The corrective choice is “Run kubectl annotate storageclass balanced-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default”.

D:

This alternative is a response to another technical cause: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. The reported case instead depends on: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The action that directly addresses it is “Run kubectl annotate storageclass balanced-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default”.

Question 762

At Horizon observability, in a disposable simulated environment during a monitored release window: The lab must designate StorageClass balanced-block as default after existing default classes have been intentionally cleared. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage.
  2. StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults.
  3. PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks.
  4. The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior.

Explanation

Correct Answer

D:

The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. This explains the stated condition. The corresponding action is: Run kubectl annotate storageclass balanced-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default. The direct acceptance evidence is: Run kubectl get storageclass and confirm the intended single default annotation.

Incorrect Answers

A:

StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. That explanation applies to a different technical failure. Here the controlling principle is: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior.

B:

The offered statement is true for this other mechanism: StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults. It does not explain the facts described here, which follow from: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior.

C:

This principle describes a separate cause: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The reported condition is governed by: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The two mechanisms should not be conflated.

Question 763

At Horizon observability, in a disposable simulated environment during a monitored release window: The lab must designate StorageClass balanced-block as default after existing default classes have been intentionally cleared. Work only within the stated target and verify before declaring success. Which observation best verifies the requested outcome rather than an unrelated state?

  1. Run kubectl get storageclass and confirm the intended single default annotation.
  2. Run kubectl -n ledger get pvc invoice-data and confirm Bound status and the selected StorageClass.
  3. Run kubectl get pods -A to inspect the relevant CSI controller and node plugin health in addition to the registered driver.
  4. Inspect provisioner, volumeBindingMode and allowVolumeExpansion for fast-block and compare with the planned PVC.

Explanation

Correct Answer

A:

Run kubectl get storageclass and confirm the intended single default annotation. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The intended action is: Run kubectl annotate storageclass balanced-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default.

Incorrect Answers

B:

This observation would test a different technical dependency: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. The current issue is governed by: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. Its decisive check is “Run kubectl get storageclass and confirm the intended single default annotation”.

C:

The alternative verifies a different condition: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The current case instead depends on: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. Confirm that “Run kubectl get storageclass and confirm the intended single default annotation”.

D:

That test belongs to another control with this basis: StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults. In the current case, the governing reason is: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The direct verification is “Run kubectl get storageclass and confirm the intended single default annotation”.

Question 764

At Horizon observability, in a disposable simulated environment during a monitored release window: The lab must designate StorageClass balanced-block as default after existing default classes have been intentionally cleared. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Verify expansion support and back up data before resizing important volumes.
  2. Treat changing default storage provisioning as a cluster-wide controlled operation.
  3. Track CSI deployment readiness and upgrade compatibility with cluster releases.
  4. Plan StatefulSet volume retention and recovery separately from controller deletion.

Explanation

Correct Answer

B:

Treat changing default storage provisioning as a cluster-wide controlled operation. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl annotate storageclass balanced-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default. The relevant mechanism is: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior.

Incorrect Answers

A:

This routine guards against another mechanism: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The recurring exposure in the current case is: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The matching preventive check is “Treat changing default storage provisioning as a cluster-wide controlled operation”.

C:

That safeguard is relevant to: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The current failure instead follows from: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. Its prevention measure is “Treat changing default storage provisioning as a cluster-wide controlled operation”.

D:

This routine guards against another mechanism: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. The recurring exposure in the current case is: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The matching preventive check is “Treat changing default storage provisioning as a cluster-wide controlled operation”.

Question 765

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: The lab must designate StorageClass standard-block as default after existing default classes have been intentionally cleared. Work only within the stated target and verify before declaring success. Which command or initial safe diagnostic step best addresses the stated lab task?

  1. Run kubectl get csidriver csi.example.test and inspect kubectl get storageclass fast-block -o yaml.
  2. Run kubectl -n fulfillment apply -f ./storage/dispatch-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites.
  3. Run kubectl get storageclass standard-block -o yaml.
  4. Run kubectl annotate storageclass standard-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default.

Explanation

Correct Answer

D:

Run kubectl annotate storageclass standard-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default. This is the appropriate command-line action or first safe diagnostic. The technical reason is: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. Validate the result with: Run kubectl get storageclass and confirm the intended single default annotation. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

A:

The proposed action belongs to the mechanism: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Here the stated fault follows a different mechanism: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The corrective choice is “Run kubectl annotate storageclass standard-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default”.

B:

The offered action targets: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. The case facts point instead to: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. Implement “Run kubectl annotate storageclass standard-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default” to address that specific condition.

C:

This alternative is a response to another technical cause: StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults. The reported case instead depends on: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The action that directly addresses it is “Run kubectl annotate storageclass standard-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default”.

Question 766

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: The lab must designate StorageClass standard-block as default after existing default classes have been intentionally cleared. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior.
  2. A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner.
  3. PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks.
  4. StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage.

Explanation

Correct Answer

A:

The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. This explains the stated condition. The corresponding action is: Run kubectl annotate storageclass standard-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default. The direct acceptance evidence is: Run kubectl get storageclass and confirm the intended single default annotation.

Incorrect Answers

B:

This principle describes a separate cause: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. The reported condition is governed by: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The two mechanisms should not be conflated.

C:

PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. That explanation applies to a different technical failure. Here the controlling principle is: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior.

D:

The offered statement is true for this other mechanism: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. It does not explain the facts described here, which follow from: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior.

Question 767

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: The lab must designate StorageClass standard-block as default after existing default classes have been intentionally cleared. Work only within the stated target and verify before declaring success. Which observation best verifies the requested outcome rather than an unrelated state?

  1. Run kubectl -n fulfillment get pvc dispatch-data and inspect capacity plus resize conditions until complete.
  2. Run kubectl get storageclass and confirm the intended single default annotation.
  3. Run kubectl -n fulfillment get pod dispatch-api -o yaml and verify claimed volumes match container mount names.
  4. Run kubectl get pods -A to inspect the relevant CSI controller and node plugin health in addition to the registered driver.

Explanation

Correct Answer

B:

Run kubectl get storageclass and confirm the intended single default annotation. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The intended action is: Run kubectl annotate storageclass standard-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default.

Incorrect Answers

A:

This observation would test a different technical dependency: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The current issue is governed by: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. Its decisive check is “Run kubectl get storageclass and confirm the intended single default annotation”.

C:

That test belongs to another control with this basis: Pod volume definitions and volumeMount references must agree; a valid PVC cannot help a container with an invalid mount path or volume name. In the current case, the governing reason is: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The direct verification is “Run kubectl get storageclass and confirm the intended single default annotation”.

D:

This observation would test a different technical dependency: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The current issue is governed by: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. Its decisive check is “Run kubectl get storageclass and confirm the intended single default annotation”.

Question 768

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: The lab must designate StorageClass standard-block as default after existing default classes have been intentionally cleared. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Maintain validated StorageClass definitions and review CSI driver compatibility during upgrades.
  2. Periodically restore test snapshots and verify backup consistency for the application.
  3. Treat changing default storage provisioning as a cluster-wide controlled operation.
  4. Track CSI deployment readiness and upgrade compatibility with cluster releases.

Explanation

Correct Answer

C:

Treat changing default storage provisioning as a cluster-wide controlled operation. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl annotate storageclass standard-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default. The relevant mechanism is: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior.

Incorrect Answers

A:

The suggested review tracks a different technical risk: StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults. Here the sustained control must address: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. Choose “Treat changing default storage provisioning as a cluster-wide controlled operation”.

B:

That safeguard is relevant to: VolumeSnapshot is a CSI extension object rather than a core PVC backup; controller and driver capabilities determine success. The current failure instead follows from: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. Its prevention measure is “Treat changing default storage provisioning as a cluster-wide controlled operation”.

D:

The suggested review tracks a different technical risk: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Here the sustained control must address: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. Choose “Treat changing default storage provisioning as a cluster-wide controlled operation”.

Question 769

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: PersistentVolume pv-ledger contains data that must not be deleted automatically when its claim is released. Work only within the stated target and verify before declaring success. Which command or initial safe diagnostic step best addresses the stated lab task?

  1. Run kubectl patch persistentvolume pv-ledger --type=merge -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}' before releasing the claim.
  2. Run kubectl -n ledger describe pod invoice-api and compare volume claim names with container mount paths.
  3. Run kubectl -n fulfillment patch pvc dispatch-data --type=merge -p '{"spec":{"volumeName":"pv-dispatch"}}' after checking capacity, access modes and storage class compatibility.
  4. Run kubectl get storageclass fast-block -o yaml.

Explanation

Correct Answer

A:

Run kubectl patch persistentvolume pv-ledger --type=merge -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}' before releasing the claim. This is the appropriate command-line action or first safe diagnostic. The technical reason is: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. Validate the result with: Run kubectl get pv pv-ledger -o jsonpath='{.spec.persistentVolumeReclaimPolicy}' and confirm Retain. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

B:

This alternative is a response to another technical cause: Pod volume definitions and volumeMount references must agree; a valid PVC cannot help a container with an invalid mount path or volume name. The reported case instead depends on: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. The action that directly addresses it is “Run kubectl patch persistentvolume pv-ledger --type=merge -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}' before releasing the claim”.

C:

The proposed action belongs to the mechanism: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. Here the stated fault follows a different mechanism: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. The corrective choice is “Run kubectl patch persistentvolume pv-ledger --type=merge -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}' before releasing the claim”.

D:

The offered action targets: StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults. The case facts point instead to: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. Implement “Run kubectl patch persistentvolume pv-ledger --type=merge -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}' before releasing the claim” to address that specific condition.

Question 770

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: PersistentVolume pv-ledger contains data that must not be deleted automatically when its claim is released. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults.
  2. The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process.
  3. StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model.
  4. StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage.

Explanation

Correct Answer

B:

The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. This explains the stated condition. The corresponding action is: Run kubectl patch persistentvolume pv-ledger --type=merge -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}' before releasing the claim. The direct acceptance evidence is: Run kubectl get pv pv-ledger -o jsonpath='{.spec.persistentVolumeReclaimPolicy}' and confirm Retain.

Incorrect Answers

A:

This principle describes a separate cause: StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults. The reported condition is governed by: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. The two mechanisms should not be conflated.

C:

The offered statement is true for this other mechanism: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. It does not explain the facts described here, which follow from: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process.

D:

This principle describes a separate cause: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The reported condition is governed by: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. The two mechanisms should not be conflated.