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 79

Question 780

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: PersistentVolume pv-dispatch contains data that must not be deleted automatically when its claim is released. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Document binding compatibility and do not reuse retained data without controlled reclamation.
  2. Reconcile data-retention duties with reclaim settings before a PVC is deleted.
  3. Verify expansion support and back up data before resizing important volumes.
  4. Plan StatefulSet volume retention and recovery separately from controller deletion.

Explanation

Correct Answer

B:

Reconcile data-retention duties with reclaim settings before a PVC is deleted. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl patch persistentvolume pv-dispatch --type=merge -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}' before releasing the claim. The relevant mechanism is: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process.

Incorrect Answers

A:

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: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. Choose “Reconcile data-retention duties with reclaim settings before a PVC is deleted”.

C:

This routine guards against another mechanism: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The recurring exposure in the current case is: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. The matching preventive check is “Reconcile data-retention duties with reclaim settings before a PVC is deleted”.

D:

The suggested review tracks a different technical risk: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. Here the sustained control must address: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. Choose “Reconcile data-retention duties with reclaim settings before a PVC is deleted”.

Question 781

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: An unbound PVC invoice-data in namespace ledger should select existing compatible PV pv-ledger by its exact name in this isolated lab. 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.training.example and inspect kubectl get storageclass standard-block -o yaml.
  2. Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"resources":{"requests":{"storage":"10Gi"}}}}'.
  3. Run kubectl annotate storageclass fast-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default.
  4. Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"volumeName":"pv-ledger"}}' after checking capacity, access modes and storage class compatibility.

Explanation

Correct Answer

D:

Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"volumeName":"pv-ledger"}}' after checking capacity, access modes and storage class compatibility. This is the appropriate command-line action or first safe diagnostic. The technical reason is: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. Validate the result with: Run kubectl -n ledger get pvc invoice-data and kubectl get pv pv-ledger to confirm matched binding. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

A:

The offered action targets: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. The case facts point instead to: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. Implement “Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"volumeName":"pv-ledger"}}' after checking capacity, access modes and storage class compatibility” to address that specific condition.

B:

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: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The action that directly addresses it is “Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"volumeName":"pv-ledger"}}' after checking capacity, access modes and storage class compatibility”.

C:

The proposed action belongs to the mechanism: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. Here the stated fault follows a different mechanism: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The corrective choice is “Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"volumeName":"pv-ledger"}}' after checking capacity, access modes and storage class compatibility”.

Question 782

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: An unbound PVC invoice-data in namespace ledger should select existing compatible PV pv-ledger by its exact name in this isolated lab. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks.
  2. StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage.
  3. A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner.
  4. StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model.

Explanation

Correct Answer

A:

PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. This explains the stated condition. The corresponding action is: Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"volumeName":"pv-ledger"}}' after checking capacity, access modes and storage class compatibility. The direct acceptance evidence is: Run kubectl -n ledger get pvc invoice-data and kubectl get pv pv-ledger to confirm matched binding.

Incorrect Answers

B:

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: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks.

C:

The offered statement is true for this other mechanism: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. It does not explain the facts described here, which follow from: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks.

D:

This principle describes a separate cause: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. The reported condition is governed by: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The two mechanisms should not be conflated.

Question 783

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: An unbound PVC invoice-data in namespace ledger should select existing compatible PV pv-ledger by its exact name in this isolated lab. Work only within the stated target and verify before declaring success. Which observation best verifies the requested outcome rather than an unrelated state?

  1. Run kubectl -n fulfillment get pvc dispatch-data and inspect capacity plus resize conditions until complete.
  2. Run kubectl -n ledger get pvc invoice-data and kubectl get pv pv-ledger to confirm matched binding.
  3. Run kubectl -n observability get pvc metrics-data and confirm Bound status and the selected StorageClass.
  4. Run kubectl -n ledger get pvc invoice-data and confirm Bound status and the selected StorageClass.

Explanation

Correct Answer

B:

Run kubectl -n ledger get pvc invoice-data and kubectl get pv pv-ledger to confirm matched binding. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The intended action is: Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"volumeName":"pv-ledger"}}' after checking capacity, access modes and storage class compatibility.

Incorrect Answers

A:

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: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. Confirm that “Run kubectl -n ledger get pvc invoice-data and kubectl get pv pv-ledger to confirm matched binding”.

C:

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: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. Its decisive check is “Run kubectl -n ledger get pvc invoice-data and kubectl get pv pv-ledger to confirm matched binding”.

D:

The alternative verifies a different condition: A PVC expresses a namespaced storage request and dynamic provisioning depends on a compatible StorageClass and provisioner. The current case instead depends on: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. Confirm that “Run kubectl -n ledger get pvc invoice-data and kubectl get pv pv-ledger to confirm matched binding”.

Question 784

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: An unbound PVC invoice-data in namespace ledger should select existing compatible PV pv-ledger by its exact name in this isolated lab. 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. Treat changing default storage provisioning as a cluster-wide controlled operation.
  3. Document binding compatibility and do not reuse retained data without controlled reclamation.
  4. Validate storage class capability, quotas and capacity before workload scheduling.

Explanation

Correct Answer

C:

Document binding compatibility and do not reuse retained data without controlled reclamation. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n ledger patch pvc invoice-data --type=merge -p '{"spec":{"volumeName":"pv-ledger"}}' after checking capacity, access modes and storage class compatibility. The relevant mechanism is: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks.

Incorrect Answers

A:

That safeguard is relevant to: The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process. The current failure instead follows from: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. Its prevention measure is “Document binding compatibility and do not reuse retained data without controlled reclamation”.

B:

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: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The matching preventive check is “Document binding compatibility and do not reuse retained data without controlled reclamation”.

D:

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 volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. Its prevention measure is “Document binding compatibility and do not reuse retained data without controlled reclamation”.

Question 785

At Horizon observability, in a disposable simulated environment during a monitored release window: An unbound PVC metrics-data in namespace observability should select existing compatible PV pv-metrics by its exact name in this isolated lab. 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":{"volumeName":"pv-metrics"}}' after checking capacity, access modes and storage class compatibility.
  2. Run kubectl -n ledger describe pod invoice-api and compare volume claim names with container mount paths.
  3. Run kubectl annotate storageclass balanced-block storageclass.kubernetes.io/is-default-class='true' --overwrite after reconciling any previous default.
  4. Run kubectl -n observability apply -f ./storage/metrics-api-snapshot.yaml after verifying the snapshot class and source PVC.

Explanation

Correct Answer

A:

Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"volumeName":"pv-metrics"}}' after checking capacity, access modes and storage class compatibility. This is the appropriate command-line action or first safe diagnostic. The technical reason is: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. Validate the result with: Run kubectl -n observability get pvc metrics-data and kubectl get pv pv-metrics to confirm matched binding. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

B:

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: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The corrective choice is “Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"volumeName":"pv-metrics"}}' after checking capacity, access modes and storage class compatibility”.

C:

The offered action targets: The default class admission behavior can assign storageClassName to new PVCs that omit it; concurrent defaults create ambiguous behavior. The case facts point instead to: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. Implement “Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"volumeName":"pv-metrics"}}' after checking capacity, access modes and storage class compatibility” to address that specific condition.

D:

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: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The action that directly addresses it is “Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"volumeName":"pv-metrics"}}' after checking capacity, access modes and storage class compatibility”.

Question 786

At Horizon observability, in a disposable simulated environment during a monitored release window: An unbound PVC metrics-data in namespace observability should select existing compatible PV pv-metrics by its exact name in this isolated lab. 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. PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks.
  3. PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps.
  4. The reclaim policy controls the fate of backing storage after PVC release; Retain requires an explicit cleanup and reuse process.

Explanation

Correct Answer

B:

PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. This explains the stated condition. The corresponding action is: Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"volumeName":"pv-metrics"}}' after checking capacity, access modes and storage class compatibility. The direct acceptance evidence is: Run kubectl -n observability get pvc metrics-data and kubectl get pv pv-metrics to confirm matched binding.

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: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks.

C:

This principle describes a separate cause: PVC expansion requests larger provisioned storage without deleting the claim; the CSI driver and filesystem may require additional expansion steps. The reported condition is governed by: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The two mechanisms should not be conflated.

D:

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: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks.

Question 787

At Horizon observability, in a disposable simulated environment during a monitored release window: An unbound PVC metrics-data in namespace observability should select existing compatible PV pv-metrics by its exact name in this isolated lab. 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 statefulset metrics-api and inspect generated PVCs and their Bound status.
  2. Run kubectl -n observability get pod metrics-api -o yaml and verify claimed volumes match container mount names.
  3. Run kubectl -n observability get pvc metrics-data and kubectl get pv pv-metrics to confirm matched binding.
  4. Run kubectl -n fulfillment get pvc dispatch-data and inspect capacity plus resize conditions until complete.

Explanation

Correct Answer

C:

Run kubectl -n observability get pvc metrics-data and kubectl get pv pv-metrics to confirm matched binding. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The intended action is: Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"volumeName":"pv-metrics"}}' after checking capacity, access modes and storage class compatibility.

Incorrect Answers

A:

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: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The direct verification is “Run kubectl -n observability get pvc metrics-data and kubectl get pv pv-metrics to confirm matched binding”.

B:

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: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. Its decisive check is “Run kubectl -n observability get pvc metrics-data and kubectl get pv pv-metrics to confirm matched binding”.

D:

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: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The direct verification is “Run kubectl -n observability get pvc metrics-data and kubectl get pv pv-metrics to confirm matched binding”.

Question 788

At Horizon observability, in a disposable simulated environment during a monitored release window: An unbound PVC metrics-data in namespace observability should select existing compatible PV pv-metrics by its exact name in this isolated lab. 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. Track CSI deployment readiness and upgrade compatibility with cluster releases.
  3. Periodically restore test snapshots and verify backup consistency for the application.
  4. Document binding compatibility and do not reuse retained data without controlled reclamation.

Explanation

Correct Answer

D:

Document binding compatibility and do not reuse retained data without controlled reclamation. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n observability patch pvc metrics-data --type=merge -p '{"spec":{"volumeName":"pv-metrics"}}' after checking capacity, access modes and storage class compatibility. The relevant mechanism is: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks.

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 volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The matching preventive check is “Document binding compatibility and do not reuse retained data without controlled reclamation”.

B:

The suggested review tracks a different technical risk: StorageClass provisioner names must correspond to installed CSI provisioning components; the class object alone cannot create storage. Here the sustained control must address: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. Choose “Document binding compatibility and do not reuse retained data without controlled reclamation”.

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 volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. Its prevention measure is “Document binding compatibility and do not reuse retained data without controlled reclamation”.

Question 789

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An unbound PVC dispatch-data in namespace fulfillment should select existing compatible PV pv-dispatch by its exact name in this isolated lab. 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-statefulset.yaml after confirming the StatefulSet's Service and StorageClass prerequisites.
  2. Run kubectl -n fulfillment patch pvc dispatch-data --type=merge -p '{"spec":{"volumeName":"pv-dispatch"}}' after checking capacity, access modes and storage class compatibility.
  3. Run kubectl patch persistentvolume pv-ledger --type=merge -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}' before releasing the claim.
  4. Run kubectl -n ledger apply -f ./storage/invoice-api-snapshot.yaml after verifying the snapshot class and source PVC.

Explanation

Correct Answer

B:

Run kubectl -n fulfillment patch pvc dispatch-data --type=merge -p '{"spec":{"volumeName":"pv-dispatch"}}' after checking capacity, access modes and storage class compatibility. This is the appropriate command-line action or first safe diagnostic. The technical reason is: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. Validate the result with: Run kubectl -n fulfillment get pvc dispatch-data and kubectl get pv pv-dispatch to confirm matched binding. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

A:

The proposed action belongs to the mechanism: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. Here the stated fault follows a different mechanism: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The corrective choice is “Run kubectl -n fulfillment patch pvc dispatch-data --type=merge -p '{"spec":{"volumeName":"pv-dispatch"}}' after checking capacity, access modes and storage class compatibility”.

C:

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 volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The action that directly addresses it is “Run kubectl -n fulfillment patch pvc dispatch-data --type=merge -p '{"spec":{"volumeName":"pv-dispatch"}}' after checking capacity, access modes and storage class compatibility”.

D:

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 volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The corrective choice is “Run kubectl -n fulfillment patch pvc dispatch-data --type=merge -p '{"spec":{"volumeName":"pv-dispatch"}}' after checking capacity, access modes and storage class compatibility”.

Question 790

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An unbound PVC dispatch-data in namespace fulfillment should select existing compatible PV pv-dispatch by its exact name in this isolated lab. 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. StorageClasses specify provisioning behavior separately from an individual claim, including binding policy and reclaim defaults.
  3. PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks.
  4. Pod volume definitions and volumeMount references must agree; a valid PVC cannot help a container with an invalid mount path or volume name.

Explanation

Correct Answer

C:

PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. This explains the stated condition. The corresponding action is: Run kubectl -n fulfillment patch pvc dispatch-data --type=merge -p '{"spec":{"volumeName":"pv-dispatch"}}' after checking capacity, access modes and storage class compatibility. The direct acceptance evidence is: Run kubectl -n fulfillment get pvc dispatch-data and kubectl get pv pv-dispatch to confirm matched binding.

Incorrect Answers

A:

The offered statement is true for this other mechanism: StatefulSets give stable identities and can generate per-Pod PVCs; a shared Deployment volume would not automatically provide this ownership model. It does not explain the facts described here, which follow from: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks.

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: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks. The two mechanisms should not be conflated.

D:

The offered statement is true for this other mechanism: Pod volume definitions and volumeMount references must agree; a valid PVC cannot help a container with an invalid mount path or volume name. It does not explain the facts described here, which follow from: PVC volumeName prebinding requests a specific PV but does not bypass binding compatibility and availability checks.