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 84

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.

Question 831

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 observation best verifies the requested outcome rather than an unrelated state?

  1. Run kubectl get pv pv-ledger -o jsonpath='{.spec.persistentVolumeReclaimPolicy}' and confirm Retain.
  2. Run kubectl -n ledger get statefulset invoice-api and inspect generated PVCs and their Bound status.
  3. Run kubectl -n ledger get pod invoice-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 -n ledger get statefulset invoice-api and inspect generated PVCs and their Bound status. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. The intended action is: Run kubectl -n ledger apply -f ./storage/invoice-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites.

Incorrect Answers

A:

The alternative verifies a different condition: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. The current 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. Confirm that “Run kubectl -n ledger get statefulset invoice-api and inspect generated PVCs and their Bound status”.

C:

This observation would test a different technical dependency: Pod volume definitions and volumeMount references must agree; a valid PVC cannot help a container with an invalid mount path or volume name. The current issue is governed by: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. Its decisive check is “Run kubectl -n ledger get statefulset invoice-api and inspect generated PVCs and their Bound status”.

D:

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: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. Confirm that “Run kubectl -n ledger get statefulset invoice-api and inspect generated PVCs and their Bound status”.

Question 832

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 operational control most directly prevents this failure or configuration drift?

  1. Add Pod schema checks and mount-level acceptance tests to storage workload releases.
  2. Validate storage class capability, quotas and capacity before workload scheduling.
  3. Plan StatefulSet volume retention and recovery separately from controller deletion.
  4. Verify expansion support and back up data before resizing important volumes.

Explanation

Correct Answer

C:

Plan StatefulSet volume retention and recovery separately from controller deletion. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n ledger apply -f ./storage/invoice-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites. The relevant mechanism is: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model.

Incorrect Answers

A:

That safeguard is relevant to: Pod volume definitions and volumeMount references must agree; a valid PVC cannot help a container with an invalid mount path or volume name. The current failure instead follows from: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. Its prevention measure is “Plan StatefulSet volume retention and recovery separately from controller deletion”.

B:

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: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. The matching preventive check is “Plan StatefulSet volume retention and recovery separately from controller deletion”.

D:

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: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. Its prevention measure is “Plan StatefulSet volume retention and recovery separately from controller deletion”.

Question 833

At Horizon observability, in a disposable simulated environment during a monitored release window: A reviewed StatefulSet manifest ./storage/metrics-api-statefulset.yaml gives app metrics-api a per-replica volumeClaimTemplate in namespace observability. 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 observability apply -f ./storage/metrics-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites.
  2. Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"volumeName":"pv-metrics"}}' after checking capacity, access modes and storage class compatibility.
  3. Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"5Gi"}}}}'.
  4. Run kubectl -n observability apply -f ./storage/metrics-api-pvc.yaml after confirming storageClassName: balanced-block and requested capacity 10Gi.

Explanation

Correct Answer

A:

Run kubectl -n observability apply -f ./storage/metrics-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 observability get statefulset metrics-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

B:

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: 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 observability apply -f ./storage/metrics-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites”.

C:

The offered action targets: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. 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 observability apply -f ./storage/metrics-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites” to address that specific condition.

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: 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 observability apply -f ./storage/metrics-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites”.

Question 834

At Horizon observability, in a disposable simulated environment during a monitored release window: A reviewed StatefulSet manifest ./storage/metrics-api-statefulset.yaml gives app metrics-api a per-replica volumeClaimTemplate in namespace observability. 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. StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model.
  3. VolumeSnapshot is a CSI extension object rather than a core PVC backup; controller and driver capabilities determine success.
  4. StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults.

Explanation

Correct Answer

B:

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 observability apply -f ./storage/metrics-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites. The direct acceptance evidence is: Run kubectl -n observability get statefulset metrics-api and inspect generated PVCs and their Bound status.

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

C:

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.

D:

StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults. 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.

Question 835

At Horizon observability, in a disposable simulated environment during a monitored release window: A reviewed StatefulSet manifest ./storage/metrics-api-statefulset.yaml gives app metrics-api a per-replica volumeClaimTemplate in namespace observability. 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 ledger get pvc invoice-data and inspect capacity plus resize conditions until complete.
  2. Run kubectl -n ledger get volumesnapshot invoice-snapshot -o yaml and confirm readyToUse: true before relying on it.
  3. Run kubectl -n observability get statefulset metrics-api and inspect generated PVCs and their Bound status.
  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

C:

Run kubectl -n observability get statefulset metrics-api and inspect generated PVCs and their Bound status. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. The intended action is: Run kubectl -n observability apply -f ./storage/metrics-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites.

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: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. The direct verification is “Run kubectl -n observability get statefulset metrics-api and inspect generated PVCs and their Bound status”.

B:

This observation would test a different technical dependency: VolumeSnapshot is a CSI extension object rather than a core PVC backup; controller and driver capabilities determine success. The current issue is governed by: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. Its decisive check is “Run kubectl -n observability get statefulset metrics-api and inspect generated PVCs and their Bound status”.

D:

That test belongs to another control with this basis: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. In the current case, the governing reason is: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. The direct verification is “Run kubectl -n observability get statefulset metrics-api and inspect generated PVCs and their Bound status”.

Question 836

At Horizon observability, in a disposable simulated environment during a monitored release window: A reviewed StatefulSet manifest ./storage/metrics-api-statefulset.yaml gives app metrics-api a per-replica volumeClaimTemplate in namespace observability. 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. Reconcile data-retention duties with reclaim settings before a PVC is deleted.
  3. Validate storage class capability, quotas and capacity before workload scheduling.
  4. Plan StatefulSet volume retention and recovery separately from controller deletion.

Explanation

Correct Answer

D:

Plan StatefulSet volume retention and recovery separately from controller deletion. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n observability apply -f ./storage/metrics-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites. The relevant mechanism is: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model.

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: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. The matching preventive check is “Plan StatefulSet volume retention and recovery separately from controller deletion”.

B:

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: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. Choose “Plan StatefulSet volume retention and recovery separately from controller deletion”.

C:

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: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. Its prevention measure is “Plan StatefulSet volume retention and recovery separately from controller deletion”.

Question 837

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: A reviewed StatefulSet manifest ./storage/dispatch-api-statefulset.yaml gives app dispatch-api a per-replica volumeClaimTemplate in namespace fulfillment. 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 -n observability apply -f ./storage/metrics-api-pvc.yaml after confirming storageClassName: balanced-block and requested capacity 10Gi.
  4. Run kubectl get csidriver csi.training.example and inspect kubectl get storageclass standard-block -o yaml.

Explanation

Correct Answer

B:

Run kubectl -n fulfillment apply -f ./storage/dispatch-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 fulfillment get statefulset dispatch-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 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: 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 fulfillment apply -f ./storage/dispatch-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites”.

C:

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: 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 fulfillment apply -f ./storage/dispatch-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites”.

D:

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: 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 fulfillment apply -f ./storage/dispatch-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites”.

Question 838

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: A reviewed StatefulSet manifest ./storage/dispatch-api-statefulset.yaml gives app dispatch-api a per-replica volumeClaimTemplate in namespace fulfillment. 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. StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage.
  3. StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model.
  4. The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior.

Explanation

Correct Answer

C:

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 fulfillment apply -f ./storage/dispatch-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites. The direct acceptance evidence is: Run kubectl -n fulfillment get statefulset dispatch-api and inspect generated PVCs and their Bound status.

Incorrect Answers

A:

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.

B:

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

D:

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

Question 839

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: A reviewed StatefulSet manifest ./storage/dispatch-api-statefulset.yaml gives app dispatch-api a per-replica volumeClaimTemplate in namespace fulfillment. 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 ledger get pvc invoice-data and inspect capacity plus resize conditions until complete.
  2. Run kubectl -n fulfillment get volumesnapshot dispatch-snapshot -o yaml and confirm readyToUse: true before relying on it.
  3. Inspect provisioner, volumeBindingMode and allowVolumeExpansion for fast-block and compare with the planned PVC.
  4. Run kubectl -n fulfillment get statefulset dispatch-api and inspect generated PVCs and their Bound status.

Explanation

Correct Answer

D:

Run kubectl -n fulfillment get statefulset dispatch-api and inspect generated PVCs and their Bound status. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. The intended action is: Run kubectl -n fulfillment apply -f ./storage/dispatch-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites.

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: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. Its decisive check is “Run kubectl -n fulfillment get statefulset dispatch-api and inspect generated PVCs and their Bound status”.

B:

The alternative verifies a different condition: VolumeSnapshot is a CSI extension object rather than a core PVC backup; controller and driver capabilities determine success. The current 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. Confirm that “Run kubectl -n fulfillment get statefulset dispatch-api and inspect generated PVCs and their Bound status”.

C:

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: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. The direct verification is “Run kubectl -n fulfillment get statefulset dispatch-api and inspect generated PVCs and their Bound status”.

Question 840

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: A reviewed StatefulSet manifest ./storage/dispatch-api-statefulset.yaml gives app dispatch-api a per-replica volumeClaimTemplate in namespace fulfillment. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Plan StatefulSet volume retention and recovery separately from controller deletion.
  2. Document binding compatibility and do not reuse retained data without controlled reclamation.
  3. Add Pod schema checks and mount-level acceptance tests to storage workload releases.
  4. Periodically restore test snapshots and verify backup consistency for the application.

Explanation

Correct Answer

A:

Plan StatefulSet volume retention and recovery separately from controller deletion. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n fulfillment apply -f ./storage/dispatch-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites. The relevant mechanism is: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model.

Incorrect Answers

B:

That safeguard is relevant to: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The current failure instead follows from: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. Its prevention measure is “Plan StatefulSet volume retention and recovery separately from controller deletion”.

C:

This routine guards against another mechanism: Pod volume definitions and volumeMount references must agree; a valid PVC cannot help a container with an invalid mount path or volume name. The recurring exposure in the current case is: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. The matching preventive check is “Plan StatefulSet volume retention and recovery separately from controller deletion”.

D:

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: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. Choose “Plan StatefulSet volume retention and recovery separately from controller deletion”.