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 74

Question 730

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: A reviewed claim manifest ./storage/dispatch-api-pvc.yaml in namespace fulfillment requests 20Gi through existing StorageClass standard-block. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps.
  2. Pod volume definitions and volumeMount references must agree; a valid PVC cannot help a container with an invalid mount path or volume name.
  3. StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage.
  4. A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner.

Explanation

Correct Answer

D:

A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. This explains the stated condition. The corresponding action is: Run kubectl -n fulfillment apply -f ./storage/dispatch-api-pvc.yaml after confirming storageClassName: standard-block and requested capacity 20Gi. The direct acceptance evidence is: Run kubectl -n fulfillment get pvc dispatch-data and confirm Bound status and the selected StorageClass.

Incorrect Answers

A:

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: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner.

B:

This principle describes a separate 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 condition is governed by: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. The two mechanisms should not be conflated.

C:

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: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner.

Question 731

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: A reviewed claim manifest ./storage/dispatch-api-pvc.yaml in namespace fulfillment requests 20Gi through existing StorageClass standard-block. 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 confirm Bound status and the selected StorageClass.
  2. Run kubectl -n ledger get pvc invoice-data and inspect capacity plus resize conditions until complete.
  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

A:

Run kubectl -n fulfillment get pvc dispatch-data and confirm Bound status and the selected StorageClass. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. The intended action is: Run kubectl -n fulfillment apply -f ./storage/dispatch-api-pvc.yaml after confirming storageClassName: standard-block and requested capacity 20Gi.

Incorrect Answers

B:

The alternative verifies a different condition: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The current case instead depends on: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. Confirm that “Run kubectl -n fulfillment get pvc dispatch-data and confirm Bound status and the selected StorageClass”.

C:

That test belongs to another control with this basis: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. In the current case, the governing reason is: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. The direct verification is “Run kubectl -n fulfillment get pvc dispatch-data and confirm Bound status and the selected StorageClass”.

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: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. Its decisive check is “Run kubectl -n fulfillment get pvc dispatch-data and confirm Bound status and the selected StorageClass”.

Question 732

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: A reviewed claim manifest ./storage/dispatch-api-pvc.yaml in namespace fulfillment requests 20Gi through existing StorageClass standard-block. 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. Validate storage class capability, quotas and capacity before workload scheduling.
  3. Track CSI deployment readiness and upgrade compatibility with cluster releases.
  4. Maintain validated StorageClass definitions and review CSI driver compatibility during upgrades.

Explanation

Correct Answer

B:

Validate storage class capability, quotas and capacity before workload scheduling. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n fulfillment apply -f ./storage/dispatch-api-pvc.yaml after confirming storageClassName: standard-block and requested capacity 20Gi. The relevant mechanism is: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner.

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: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. Choose “Validate storage class capability, quotas and capacity before workload scheduling”.

C:

This routine guards against another mechanism: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The recurring exposure in the current case is: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. The matching preventive check is “Validate storage class capability, quotas and capacity before workload scheduling”.

D:

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: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. Choose “Validate storage class capability, quotas and capacity before workload scheduling”.

Question 733

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: An existing dynamically provisioned PVC invoice-data in ledger must be expanded to 5Gi; the StorageClass supports volume expansion. 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-pvc.yaml after confirming storageClassName: balanced-block and requested capacity 10Gi.
  2. Run kubectl patch persistentvolume pv-dispatch --type=merge -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}' before releasing the claim.
  3. Run kubectl get csidriver csi.example.test and inspect kubectl get storageclass fast-block -o yaml.
  4. Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"5Gi"}}}}'.

Explanation

Correct Answer

D:

Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"5Gi"}}}}'. This is the appropriate command-line action or first safe diagnostic. The technical reason is: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. Validate the result with: Run kubectl -n ledger get pvc invoice-data and inspect capacity plus resize conditions until complete. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

A:

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: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. Implement “Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"5Gi"}}}}'” to address that specific condition.

B:

This alternative is a response to another technical cause: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. The reported case instead depends on: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The action that directly addresses it is “Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"5Gi"}}}}'”.

C:

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: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The corrective choice is “Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"5Gi"}}}}'”.

Question 734

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: An existing dynamically provisioned PVC invoice-data in ledger must be expanded to 5Gi; the StorageClass supports volume expansion. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps.
  2. VolumeSnapshot is a CSI extension object rather than a core PVC backup; controller and driver capabilities determine success.
  3. StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults.
  4. A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner.

Explanation

Correct Answer

A:

PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. This explains the stated condition. The corresponding action is: Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"5Gi"}}}}'. The direct acceptance evidence is: Run kubectl -n ledger get pvc invoice-data and inspect capacity plus resize conditions until complete.

Incorrect Answers

B:

VolumeSnapshot is a CSI extension object rather than a core PVC backup; controller and driver capabilities determine success. That explanation applies to a different technical failure. Here the controlling principle is: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps.

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: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps.

D:

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: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The two mechanisms should not be conflated.

Question 735

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: An existing dynamically provisioned PVC invoice-data in ledger must be expanded to 5Gi; the StorageClass supports volume expansion. 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 pod invoice-api -o yaml and verify claimed volumes match container mount names.
  2. Run kubectl -n ledger get pvc invoice-data and inspect capacity plus resize conditions until complete.
  3. Run kubectl -n fulfillment get volumesnapshot dispatch-snapshot -o yaml and confirm readyToUse: true before relying on it.
  4. Run kubectl get storageclass and confirm the intended single default annotation.

Explanation

Correct Answer

B:

Run kubectl -n ledger get pvc invoice-data and inspect capacity plus resize conditions until complete. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The intended action is: Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"5Gi"}}}}'.

Incorrect Answers

A:

The alternative verifies a different condition: 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 case instead depends on: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. Confirm that “Run kubectl -n ledger get pvc invoice-data and inspect capacity plus resize conditions until complete”.

C:

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: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. Its decisive check is “Run kubectl -n ledger get pvc invoice-data and inspect capacity plus resize conditions until complete”.

D:

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: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. Confirm that “Run kubectl -n ledger get pvc invoice-data and inspect capacity plus resize conditions until complete”.

Question 736

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: An existing dynamically provisioned PVC invoice-data in ledger must be expanded to 5Gi; the StorageClass supports volume expansion. 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. Periodically restore test snapshots and verify backup consistency for the application.
  3. Verify expansion support and back up data before resizing important volumes.
  4. Document binding compatibility and do not reuse retained data without controlled reclamation.

Explanation

Correct Answer

C:

Verify expansion support and back up data before resizing important volumes. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"5Gi"}}}}'. The relevant mechanism is: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps.

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: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. Its prevention measure is “Verify expansion support and back up data before resizing important volumes”.

B:

This routine guards against another mechanism: VolumeSnapshot is a CSI extension object rather than a core PVC backup; controller and driver capabilities determine success. The recurring exposure in the current case is: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The matching preventive check is “Verify expansion support and back up data before resizing important volumes”.

D:

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: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. Its prevention measure is “Verify expansion support and back up data before resizing important volumes”.

Question 737

At Horizon observability, in a disposable simulated environment during a monitored release window: An existing dynamically provisioned PVC metrics-data in observability must be expanded to 10Gi; the StorageClass supports volume expansion. 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 patch pvc metrics-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"10Gi"}}}}'.
  2. Run kubectl -n fulfillment apply -f ./storage/dispatch-api-snapshot.yaml after verifying the snapshot class and source PVC.
  3. Run kubectl -n observability apply -f ./storage/metrics-api-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites.
  4. Run kubectl get csidriver csi.lab.example and inspect kubectl get storageclass balanced-block -o yaml.

Explanation

Correct Answer

A:

Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"10Gi"}}}}'. This is the appropriate command-line action or first safe diagnostic. The technical reason is: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. Validate the result with: Run kubectl -n observability get pvc metrics-data and inspect capacity plus resize conditions until complete. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

B:

The proposed action belongs to the mechanism: VolumeSnapshot is a CSI extension object rather than a core PVC backup; controller and driver capabilities determine success. Here the stated fault follows a different mechanism: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The corrective choice is “Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"10Gi"}}}}'”.

C:

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: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. Implement “Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"10Gi"}}}}'” to address that specific condition.

D:

This alternative is a response to another technical cause: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The reported case instead depends on: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The action that directly addresses it is “Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"10Gi"}}}}'”.

Question 738

At Horizon observability, in a disposable simulated environment during a monitored release window: An existing dynamically provisioned PVC metrics-data in observability must be expanded to 10Gi; the StorageClass supports volume expansion. 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. PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps.
  3. The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior.
  4. A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner.

Explanation

Correct Answer

B:

PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. This explains the stated condition. The corresponding action is: Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"10Gi"}}}}'. The direct acceptance evidence is: Run kubectl -n observability get pvc metrics-data and inspect capacity plus resize conditions until complete.

Incorrect Answers

A:

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: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps.

C:

This principle describes a separate cause: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The reported condition is governed by: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The two mechanisms should not be conflated.

D:

A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. That explanation applies to a different technical failure. Here the controlling principle is: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps.

Question 739

At Horizon observability, in a disposable simulated environment during a monitored release window: An existing dynamically provisioned PVC metrics-data in observability must be expanded to 10Gi; the StorageClass supports volume expansion. 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 volumesnapshot invoice-snapshot -o yaml and confirm readyToUse: true before relying on it.
  2. Run kubectl get pv pv-dispatch -o jsonpath='{.spec.persistentVolumeReclaimPolicy}' and confirm Retain.
  3. Run kubectl -n observability get pvc metrics-data and inspect capacity plus resize conditions until complete.
  4. Run kubectl -n fulfillment get pvc dispatch-data and kubectl get pv pv-dispatch to confirm matched binding.

Explanation

Correct Answer

C:

Run kubectl -n observability get pvc metrics-data and inspect capacity plus resize conditions until complete. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The intended action is: Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"10Gi"}}}}'.

Incorrect Answers

A:

That test belongs to another control with this basis: VolumeSnapshot is a CSI extension object rather than a core PVC backup; controller and driver capabilities determine success. In the current case, the governing reason is: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The direct verification is “Run kubectl -n observability get pvc metrics-data and inspect capacity plus resize conditions until complete”.

B:

This observation would test a different technical dependency: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. The current issue is governed by: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. Its decisive check is “Run kubectl -n observability get pvc metrics-data and inspect capacity plus resize conditions until complete”.

D:

That test belongs to another control with this basis: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. In the current case, the governing reason is: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The direct verification is “Run kubectl -n observability get pvc metrics-data and inspect capacity plus resize conditions until complete”.

Question 740

At Horizon observability, in a disposable simulated environment during a monitored release window: An existing dynamically provisioned PVC metrics-data in observability must be expanded to 10Gi; the StorageClass supports volume expansion. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Reconcile data-retention duties with reclaim settings before a PVC is deleted.
  2. Validate storage class capability, quotas and capacity before workload scheduling.
  3. Periodically restore test snapshots and verify backup consistency for the application.
  4. Verify expansion support and back up data before resizing important volumes.

Explanation

Correct Answer

D:

Verify expansion support and back up data before resizing important volumes. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"10Gi"}}}}'. The relevant mechanism is: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps.

Incorrect Answers

A:

This routine guards against another mechanism: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. The recurring exposure in the current case is: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The matching preventive check is “Verify expansion support and back up data before resizing important volumes”.

B:

The suggested review tracks a different technical risk: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. Here the sustained control must address: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. Choose “Verify expansion support and back up data before resizing important volumes”.

C:

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: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. Its prevention measure is “Verify expansion support and back up data before resizing important volumes”.