A school district needs disk contents preserved after a PVC is deleted so staff can recover data manually. Which reclaim policy should the PV use?
Select an answer to reveal the explanation.
Short Explanation
Retain is the evidence locker: claim goes away, but the box of disks stays until a human checks it out and cleans up. Delete would toss the box. For forensics or precious recovery paths, Retain is the policy you want.
Full Explanation
A school district that needs disk contents preserved after PVC deletion so staff can recover data manually should use reclaimPolicy Retain on the PV. Retain is the evidence locker: the claim goes away, but the box of disks stays until a human checks it out and cleans up. That policy best matches forensic or precious recovery paths.
Delete does not snapshot then automatically recreate an identical PVC as a recovery feature. Recycle is deprecated legacy behavior, not the preferred modern CSI default that wipes and requeues every cloud disk. Always is not a reclaim policy that mirrors volumes to every node.
Exam caveat: after Retain, the PV usually sits Released until an admin clears claimRef and decides to reuse or destroy the backend. Leaving Released volumes around consumes quota and cloud spend—process them deliberately.
Operational check: set Retain on the critical class/PVs, delete a test PVC, verify the PV and data remain, practice the manual reclaim steps, and write them into the district storage runbook. Keep civic change tickets precise: record object names, namespaces, and before/after observations so the next on-call engineer can replay the fix without guesswork. Keep civic change tickets precise: record object names, namespaces, and before/after observations so the next on-call engineer can replay the fix without guesswork.