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 83

Question 820

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: An operator needs to verify the CSI driver named csi.example.test is registered before assigning StorageClass fast-block to a workload. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Validate storage class capability, quotas and capacity before workload scheduling.
  2. Verify expansion support and back up data before resizing important volumes.
  3. Reconcile data-retention duties with reclaim settings before a PVC is deleted.
  4. Track CSI deployment readiness and upgrade compatibility with cluster releases.

Explanation

Correct Answer

D:

Track CSI deployment readiness and upgrade compatibility with cluster releases. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl get csidriver csi.example.test and inspect kubectl get storageclass fast-block -o yaml. The relevant mechanism is: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage.

Incorrect Answers

A:

That safeguard is relevant to: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. The current failure instead follows from: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Its prevention measure is “Track CSI deployment readiness and upgrade compatibility with cluster releases”.

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: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The matching preventive check is “Track CSI deployment readiness and upgrade compatibility with cluster releases”.

C:

The suggested review tracks a different technical risk: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. Here the sustained control must address: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Choose “Track CSI deployment readiness and upgrade compatibility with cluster releases”.

Question 821

At Horizon observability, in a disposable simulated environment during a monitored release window: An operator needs to verify the CSI driver named csi.lab.example is registered before assigning StorageClass balanced-block to a workload. 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 fulfillment apply -f ./storage/dispatch-api-pvc.yaml after confirming storageClassName: standard-block and requested capacity 20Gi.
  2. Run kubectl get csidriver csi.lab.example and inspect kubectl get storageclass balanced-block -o yaml.
  3. Run kubectl -n ledger apply -f ./storage/invoice-api-snapshot.yaml after verifying the snapshot class and source PVC.
  4. Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"10Gi"}}}}'.

Explanation

Correct Answer

B:

Run kubectl get csidriver csi.lab.example and inspect kubectl get storageclass balanced-block -o yaml. This is the appropriate command-line action or first safe diagnostic. The technical reason is: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Validate the result with: Run kubectl get pods -A to inspect the relevant CSI controller and node plugin health in addition to the registered driver. 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: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The action that directly addresses it is “Run kubectl get csidriver csi.lab.example and inspect kubectl get storageclass balanced-block -o yaml”.

C:

The offered action targets: VolumeSnapshot is a CSI extension object rather than a core PVC backup; controller and driver capabilities determine success. The case facts point instead to: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Implement “Run kubectl get csidriver csi.lab.example and inspect kubectl get storageclass balanced-block -o yaml” to address that specific condition.

D:

This alternative is a response to another technical cause: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The reported case instead depends on: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The action that directly addresses it is “Run kubectl get csidriver csi.lab.example and inspect kubectl get storageclass balanced-block -o yaml”.

Question 822

At Horizon observability, in a disposable simulated environment during a monitored release window: An operator needs to verify the CSI driver named csi.lab.example is registered before assigning StorageClass balanced-block to a workload. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model.
  2. PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps.
  3. StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage.
  4. The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior.

Explanation

Correct Answer

C:

StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. This explains the stated condition. The corresponding action is: Run kubectl get csidriver csi.lab.example and inspect kubectl get storageclass balanced-block -o yaml. The direct acceptance evidence is: Run kubectl get pods -A to inspect the relevant CSI controller and node plugin health in addition to the registered driver.

Incorrect Answers

A:

StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. That explanation applies to a different technical failure. Here the controlling principle is: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage.

B:

The offered statement is true for this other mechanism: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. It does not explain the facts described here, which follow from: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage.

D:

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

Question 823

At Horizon observability, in a disposable simulated environment during a monitored release window: An operator needs to verify the CSI driver named csi.lab.example is registered before assigning StorageClass balanced-block to a workload. 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 observability get pvc metrics-data and inspect capacity plus resize conditions until complete.
  2. Inspect provisioner, volumeBindingMode and allowVolumeExpansion for standard-block and compare with the planned PVC.
  3. Inspect provisioner, volumeBindingMode and allowVolumeExpansion for fast-block and compare with the planned PVC.
  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

D:

Run kubectl get pods -A to inspect the relevant CSI controller and node plugin health in addition to the registered driver. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The intended action is: Run kubectl get csidriver csi.lab.example and inspect kubectl get storageclass balanced-block -o yaml.

Incorrect Answers

A:

That test belongs to another control with this basis: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. In the current case, the governing reason is: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The direct verification is “Run kubectl get pods -A to inspect the relevant CSI controller and node plugin health in addition to the registered driver”.

B:

This observation would test a different technical dependency: StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults. The current issue is governed by: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Its decisive check is “Run kubectl get pods -A to inspect the relevant CSI controller and node plugin health in addition to the registered driver”.

C:

The alternative verifies a different condition: StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults. The current case instead depends on: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Confirm that “Run kubectl get pods -A to inspect the relevant CSI controller and node plugin health in addition to the registered driver”.

Question 824

At Horizon observability, in a disposable simulated environment during a monitored release window: An operator needs to verify the CSI driver named csi.lab.example is registered before assigning StorageClass balanced-block to a workload. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Track CSI deployment readiness and upgrade compatibility with cluster releases.
  2. Periodically restore test snapshots and verify backup consistency for the application.
  3. Verify expansion support and back up data before resizing important volumes.
  4. Treat changing default storage provisioning as a cluster-wide controlled operation.

Explanation

Correct Answer

A:

Track CSI deployment readiness and upgrade compatibility with cluster releases. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl get csidriver csi.lab.example and inspect kubectl get storageclass balanced-block -o yaml. The relevant mechanism is: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage.

Incorrect Answers

B:

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: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Choose “Track CSI deployment readiness and upgrade compatibility with cluster releases”.

C:

That safeguard is relevant to: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The current failure instead follows from: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Its prevention measure is “Track CSI deployment readiness and upgrade compatibility with cluster releases”.

D:

This routine guards against another mechanism: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The recurring exposure in the current case is: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The matching preventive check is “Track CSI deployment readiness and upgrade compatibility with cluster releases”.

Question 825

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An operator needs to verify the CSI driver named csi.training.example is registered before assigning StorageClass standard-block to a workload. 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 fulfillment patch pvc dispatch-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"20Gi"}}}}'.
  2. Run kubectl -n observability apply -f ./storage/metrics-api-pvc.yaml after confirming storageClassName: balanced-block and requested capacity 10Gi.
  3. Run kubectl get csidriver csi.training.example and inspect kubectl get storageclass standard-block -o yaml.
  4. Run kubectl get storageclass balanced-block -o yaml.

Explanation

Correct Answer

C:

Run kubectl get csidriver csi.training.example and inspect kubectl get storageclass standard-block -o yaml. This is the appropriate command-line action or first safe diagnostic. The technical reason is: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Validate the result with: Run kubectl get pods -A to inspect the relevant CSI controller and node plugin health in addition to the registered driver. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

A:

The proposed action belongs to the mechanism: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. Here the stated fault follows a different mechanism: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The corrective choice is “Run kubectl get csidriver csi.training.example and inspect kubectl get storageclass standard-block -o yaml”.

B:

The offered action targets: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. The case facts point instead to: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Implement “Run kubectl get csidriver csi.training.example and inspect kubectl get storageclass standard-block -o yaml” to address that specific condition.

D:

The proposed action belongs to the mechanism: StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults. Here the stated fault follows a different mechanism: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The corrective choice is “Run kubectl get csidriver csi.training.example and inspect kubectl get storageclass standard-block -o yaml”.

Question 826

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An operator needs to verify the CSI driver named csi.training.example is registered before assigning StorageClass standard-block to a workload. 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. StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults.
  3. The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process.
  4. StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage.

Explanation

Correct Answer

D:

StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. This explains the stated condition. The corresponding action is: Run kubectl get csidriver csi.training.example and inspect kubectl get storageclass standard-block -o yaml. The direct acceptance evidence is: Run kubectl get pods -A to inspect the relevant CSI controller and node plugin health in addition to the registered driver.

Incorrect Answers

A:

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

B:

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: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The two mechanisms should not be conflated.

C:

The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. That explanation applies to a different technical failure. Here the controlling principle is: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage.

Question 827

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An operator needs to verify the CSI driver named csi.training.example is registered before assigning StorageClass standard-block to a workload. 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 pods -A to inspect the relevant CSI controller and node plugin health in addition to the registered driver.
  2. Run kubectl get storageclass and confirm the intended single default annotation.
  3. Run kubectl -n observability get pvc metrics-data and inspect capacity plus resize conditions until complete.
  4. Run kubectl -n observability get pvc metrics-data and confirm Bound status and the selected StorageClass.

Explanation

Correct Answer

A:

Run kubectl get pods -A to inspect the relevant CSI controller and node plugin health in addition to the registered driver. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The intended action is: Run kubectl get csidriver csi.training.example and inspect kubectl get storageclass standard-block -o yaml.

Incorrect Answers

B:

The alternative verifies a different condition: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The current case instead depends on: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Confirm that “Run kubectl get pods -A to inspect the relevant CSI controller and node plugin health in addition to the registered driver”.

C:

That test belongs to another control with this basis: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. In the current case, the governing reason is: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The direct verification is “Run kubectl get pods -A to inspect the relevant CSI controller and node plugin health in addition to the registered driver”.

D:

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: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Its decisive check is “Run kubectl get pods -A to inspect the relevant CSI controller and node plugin health in addition to the registered driver”.

Question 828

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An operator needs to verify the CSI driver named csi.training.example is registered before assigning StorageClass standard-block to a workload. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Periodically restore test snapshots and verify backup consistency for the application.
  2. Track CSI deployment readiness and upgrade compatibility with cluster releases.
  3. Validate storage class capability, quotas and capacity before workload scheduling.
  4. Document binding compatibility and do not reuse retained data without controlled reclamation.

Explanation

Correct Answer

B:

Track CSI deployment readiness and upgrade compatibility with cluster releases. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl get csidriver csi.training.example and inspect kubectl get storageclass standard-block -o yaml. The relevant mechanism is: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage.

Incorrect Answers

A:

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: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Choose “Track CSI deployment readiness and upgrade compatibility with cluster releases”.

C:

This routine guards against another mechanism: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. The recurring exposure in the current case is: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The matching preventive check is “Track CSI deployment readiness and upgrade compatibility with cluster releases”.

D:

The suggested review tracks a different technical risk: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. Here the sustained control must address: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Choose “Track CSI deployment readiness and upgrade compatibility with cluster releases”.

Question 829

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: A reviewed StatefulSet manifest ./storage/invoice-api-statefulset.yaml gives app invoice-api a per-replica volumeClaimTemplate in namespace ledger. 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 describe pod invoice-api and compare volume claim names with container mount paths.
  2. Run kubectl -n observability apply -f ./storage/metrics-api-snapshot.yaml after verifying the snapshot class and source PVC.
  3. Run kubectl -n fulfillment describe pod dispatch-api and compare volume claim names with container mount paths.
  4. Run kubectl -n ledger apply -f ./storage/invoice-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites.

Explanation

Correct Answer

D:

Run kubectl -n ledger apply -f ./storage/invoice-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites. This is the appropriate command-line action or first safe diagnostic. The technical reason is: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. Validate the result with: Run kubectl -n ledger get statefulset invoice-api and inspect generated PVCs and their Bound status. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

A:

The offered action targets: Pod volume definitions and volumeMount references must agree; a valid PVC cannot help a container with an invalid mount path or volume name. The case facts point instead to: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. Implement “Run kubectl -n ledger apply -f ./storage/invoice-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites” to address that specific condition.

B:

This alternative is a response to another technical cause: VolumeSnapshot is a CSI extension object rather than a core PVC backup; controller and driver capabilities determine success. The reported case instead depends on: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. The action that directly addresses it is “Run kubectl -n ledger apply -f ./storage/invoice-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites”.

C:

The proposed action belongs to the mechanism: Pod volume definitions and volumeMount references must agree; a valid PVC cannot help a container with an invalid mount path or volume name. Here the stated fault follows a different mechanism: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. The corrective choice is “Run kubectl -n ledger apply -f ./storage/invoice-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites”.

Question 830

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: A reviewed StatefulSet manifest ./storage/invoice-api-statefulset.yaml gives app invoice-api a per-replica volumeClaimTemplate in namespace ledger. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model.
  2. The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior.
  3. StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults.
  4. VolumeSnapshot is a CSI extension object rather than a core PVC backup; controller and driver capabilities determine success.

Explanation

Correct Answer

A:

StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. This explains the stated condition. The corresponding action is: Run kubectl -n ledger apply -f ./storage/invoice-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites. The direct acceptance evidence is: Run kubectl -n ledger get statefulset invoice-api and inspect generated PVCs and their Bound status.

Incorrect Answers

B:

The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. That explanation applies to a different technical failure. Here the controlling principle is: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model.

C:

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: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model.

D:

This principle describes a separate cause: VolumeSnapshot is a CSI extension object rather than a core PVC backup; controller and driver capabilities determine success. The reported condition is governed by: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. The two mechanisms should not be conflated.