CKA Storage Practice Question
An administrator is preparing a StorageClass for a stateful application. The cluster's default StorageClass uses immediate binding, which causes PersistentVolumes to be provisioned before the consuming Pod is scheduled. The administrator wants volumes to be provisioned only after the scheduler has selected a node, so that topology-aware constraints (such as zone-local disks) can be honored. Which change to the StorageClass should the administrator make?
⚠ Common exam trap
The trap here is assuming that adding a topology key directly to the StorageClass controls provisioning location, when topology awareness is actually driven by volumeBindingMode and the CSI driver's topology support.
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
✓
Set volumeBindingMode to WaitForFirstConsumer in the StorageClass specification.
WaitForFirstConsumer is the volumeBindingMode value that defers both binding and dynamic provisioning until a Pod using the PVC is scheduled, letting the scheduler choose a node that satisfies the Pod's topology constraints. Immediate binding provisions too early for zone-local storage. The other options either use unrelated StorageClass fields or fields that do not exist.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set volumeBindingMode to Immediate and add a nodeSelector to the StorageClass.
Why it's wrong here
Immediate binding provisions the volume as soon as the PVC is created, before any Pod is scheduled, so the scheduler cannot influence the volume's topology. StorageClass objects do not support a nodeSelector field; node selection belongs to the Pod spec. This combination does not achieve delayed, topology-aware provisioning.
- ✗
Add a topologyKey field to the StorageClass and set it to kubernetes.io/hostname.
Why it's wrong here
StorageClass has no topologyKey field; topology keys are used in Pod affinity rules and in CSI topology specifications, not directly in a StorageClass. Adding an unsupported field would be rejected or ignored. The correct mechanism to defer provisioning until scheduling is volumeBindingMode, not a topology key.
- ✓
Set volumeBindingMode to WaitForFirstConsumer in the StorageClass specification.
Why this is correct
WaitForFirstConsumer delays binding and provisioning until a Pod using the PVC is scheduled, allowing the scheduler to consider the Pod's node affinity and topology constraints. This prevents provisioning a volume in the wrong zone. It is the correct field for topology-aware dynamic provisioning and directly addresses the scenario's requirement.
- ✗
Set reclaimPolicy to Retain and set allowVolumeExpansion to true.
Why it's wrong here
Retain controls what happens to the PV after the PVC is deleted, and allowVolumeExpansion permits resizing. Neither affects when provisioning occurs relative to Pod scheduling. These settings are unrelated to delaying binding until the scheduler picks a node, so they do not solve the topology problem described.
Go deeper
Related to this question
Learn chapter
Storage Basics and Volumes
Key term
Storage Classes
A Storage Class in Kubernetes is a template that defines how persistent storage is provisioned automatically, including the type of storage, performance characteristics, and provisioning policies.
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
This CKA question is part of Courseiva's 726-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CNCF exam blueprint
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.