CKA Storage Practice Question
What is the default reclaim policy for a PersistentVolume?
⚠ Common exam trap
Watch out — candidates often confuse the default reclaim policy with 'Delete' because many cloud-provisioned StorageClasses set reclaimPolicy: Delete by default, but the PV itself defaults to 'Retain' when created statically or without a StorageClass.
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
✓
Retain
The default reclaim policy for a PersistentVolume (PV) in Kubernetes is 'Retain'. This means that when a PersistentVolumeClaim (PVC) bound to the PV is deleted, the PV will not be automatically deleted or recycled; instead, it remains in a 'Released' state, preserving the underlying storage and data for manual administrator intervention. This is defined in the PV's spec.persistentVolumeReclaimPolicy field, which defaults to 'Retain' if not explicitly set.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Recycle
Why it's wrong here
While the Recycle policy performs a basic scrub (running an rm -rf equivalent) on the volume to make it available again for another claim, it is not the default. Furthermore, this policy is deprecated in modern Kubernetes versions in favor of dynamic provisioning, and it is only supported by a limited number of volume plugins like HostPath and NFS.
- ✗
None
Why it's wrong here
Kubernetes does not allow a PersistentVolume to exist without an associated reclaim policy. If a reclaim policy is not explicitly specified in the PersistentVolume's YAML definition, the control plane automatically assigns a default policy to ensure the lifecycle of the underlying storage is managed predictably when a PersistentVolumeClaim is deleted.
- ✓
Retain
Why this is correct
The Retain reclaim policy is the default behavior for manually created PersistentVolumes. When a PersistentVolumeClaim is deleted, the PersistentVolume still exists and is marked as Released, preserving all data on the external storage asset so that an administrator can manually recover, clean, or reuse the volume.
- ✗
Delete
Why it's wrong here
The Delete policy automatically removes both the PersistentVolume object from Kubernetes and the associated storage asset in the external infrastructure, such as an AWS EBS volume or GCP Persistent Disk, when the claim is deleted. Although this is the default policy for volumes created dynamically via StorageClasses, it is not the default for manually created PersistentVolumes.
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.