CKA Storage Practice Question
A PersistentVolume is created with the following spec: persistentVolumeReclaimPolicy: Retain claimRef: namespace: default name: my-pvc After the PVC 'my-pvc' is deleted, what happens to the PV?
⚠ Common exam trap
It's easy for candidates to assume a 'Released' PV automatically becomes 'Available' for reuse, but Kubernetes requires manual intervention to clear the `claimRef` before the PV can be bound to a new PVC.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The PV enters Released state and must have its claimRef manually removed to be reused
When a PersistentVolume (PV) has a reclaim policy of 'Retain' and its bound PVC is deleted, the PV enters the 'Released' state. It is not automatically deleted or recycled; instead, its data is preserved but the PV cannot be reused until the `claimRef` field is manually removed by an administrator. This is because the `claimRef` still references the deleted PVC, preventing automatic re-binding.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The PV enters Released state and must have its claimRef manually removed to be reused
Why this is correct
Under the Retain reclaim policy, deleting a PersistentVolumeClaim does not delete the underlying PersistentVolume. Instead, the PV transitions to the Released phase, preserving its data. To make this volume eligible for binding to a new PVC, an administrator must manually edit the PV spec to remove the claimRef block, which still points to the deleted PVC.
- ✗
The PV is automatically deleted
Why it's wrong here
Automatic deletion of the PersistentVolume only occurs if the reclaim policy is explicitly set to Delete. With the Retain policy, Kubernetes purposefully preserves the PV and its associated storage asset in the external infrastructure to prevent accidental data loss. Administrators must manually clean up the resource and the backing storage when it is no longer needed.
- ✗
The PV remains Available and can be bound to a new PVC
Why it's wrong here
A PersistentVolume cannot immediately return to the Available state because its spec.claimRef still contains a reference to the deleted PVC. This safety mechanism prevents another claim from automatically binding to the volume and potentially accessing or overwriting sensitive leftover data. The PV remains in the Released state until manual administrative intervention occurs.
- ✗
The PV is recycled and its contents are wiped
Why it's wrong here
Wiping data and recycling the volume is the behavior of the Recycle reclaim policy, which performs a basic scrub (rm -rf) on the volume. However, the Recycle policy is deprecated in modern Kubernetes versions in favor of dynamic provisioning. Under the Retain policy, no automated data scrubbing or volume reuse occurs.
Go deeper
Related to this question
Key term
Persistent Volumes
A Persistent Volume is a piece of storage in a Kubernetes cluster that has been provisioned by an administrator and exists independently of any single pod that uses it.
Key term
Volumes
In Kubernetes, a volume is a storage resource that outlives the pod it belongs to, enabling data to persist across container restarts and be shared between containers in the same pod.
About these practice questions
Courseiva writes every CKA question from scratch — 726 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CKA practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CKA exam.