CKA Storage Practice Question
An administrator creates a PersistentVolume named 'pv-nfs' with a reclaim policy of 'Retain'. After a user deletes the PVC bound to this PV, what state does the PV enter?
⚠ Common exam trap
Many exam-takers confuse 'Released' with 'Available', assuming the PV automatically becomes reusable after PVC deletion, but 'Retain' policy explicitly prevents automatic reclamation to protect data.
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
✓
Released
When a PVC bound to a PV with a reclaim policy of 'Retain' is deleted, the PV does not automatically become available for reuse. Instead, it enters the 'Released' state, indicating that the volume's data is still intact but the PV is no longer bound to a claim. The administrator must manually intervene to reclaim or delete the underlying storage before the PV can be made available again.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Available
Why it's wrong here
When a PersistentVolumeClaim (PVC) bound to a PersistentVolume (PV) with a Retain reclaim policy is deleted, the PV does not automatically revert to the Available phase. Instead, it transitions to Released to prevent other claims from immediately binding to it and potentially accessing or overwriting the previous user's leftover data. To make it Available again, an administrator must manually intervene to clean up the data and recreate or patch the PV resource.
- ✗
Failed
Why it's wrong here
While Failed is a valid Kubernetes PV phase, it only occurs when an automated reclamation process (such as Delete or Recycle) fails to clean up the underlying storage. Under a normal Retain policy deletion, no automated cleanup is attempted, meaning the volume transitions successfully to the Released phase without triggering any automated deletion failures.
- ✗
Bound
Why it's wrong here
The Bound phase indicates that the PersistentVolume is currently actively coupled with a specific PersistentVolumeClaim. Once the associated PVC is deleted by the user, this active binding is broken, meaning the PV can no longer remain in the Bound state and must transition to a state reflecting its unassigned status.
- ✓
Released
Why this is correct
Under the Retain reclaim policy, deleting the PVC leaves the actual storage asset intact along with all its data, transitioning the PV's status to Released. This phase explicitly signals to the cluster that the volume is no longer bound to a claim, but still contains sensitive or valuable data that must be manually managed or reclaimed by an administrator before it can be reused.
Go deeper
Related to this question
Learn chapter
Troubleshooting Storage Persistence
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
One of 726 original CKA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.