In Kubernetes, the Manual Reclamation Policy for Persistent Volume Claims (PVCs) is typically recognized as which of the following?

In Kubernetes, the Manual Reclamation Policy for Persistent Volume Claims (PVCs) is typically recognized as which of the following?

• A. Delete
• B. Recycle
• C. Archive
• D. Retain

Answer: (A)

Reclaiming storage in Kubernetes is controlled by the PV reclaimPolicy, which decides what happens to the underlying storage when the bound PVC is deleted or released. If the policy is Delete, deleting the PVC triggers the PV and its backing storage to be removed from the cluster. This automatic cleanup matches the idea of manual reclamation, where you expect the storage asset to be cleaned up without manual intervention. Retain would keep the PV and its data, requiring manual cleanup later. Recycle is deprecated in modern clusters and not commonly used. Archive isn’t a valid Kubernetes reclaim policy.

Reclaiming storage in Kubernetes is controlled by the PV reclaimPolicy, which decides what happens to the underlying storage when the bound PVC is deleted or released. If the policy is Delete, deleting the PVC triggers the PV and its backing storage to be removed from the cluster. This automatic cleanup matches the idea of manual reclamation, where you expect the storage asset to be cleaned up without manual intervention.

Retain would keep the PV and its data, requiring manual cleanup later. Recycle is deprecated in modern clusters and not commonly used. Archive isn’t a valid Kubernetes reclaim policy.