CKA Storage Practice Question
A user creates a PersistentVolumeClaim with a storage class 'ssd' that does not exist in the cluster. What will happen when the PVC is created?
⚠ Common exam trap
Candidates often assume Kubernetes will fall back to a default StorageClass or automatically bind to an existing PV, but the system strictly requires the specified StorageClass to exist for dynamic provisioning and will not bypass this check.
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 PVC will remain in Pending state.
When a PersistentVolumeClaim (PVC) references a StorageClass that does not exist in the cluster, the PVC cannot be dynamically provisioned because the provisioner associated with that StorageClass is missing. Without a matching StorageClass, the system cannot create a new PersistentVolume (PV) for the PVC, and since no existing PV matches the claim (or the PVC is set to use dynamic provisioning), the PVC will remain in a Pending state indefinitely until the StorageClass is created or the PVC is deleted.
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 PVC will be deleted automatically after a timeout.
Why it's wrong here
A PersistentVolumeClaim (PVC) is a persistent API object in Kubernetes, and its lifecycle is managed through explicit user or controller actions, not by internal timeouts related to provisioning failures. Even if a PVC cannot be satisfied and remains in a `Pending` state indefinitely, the Kubernetes control plane will not automatically delete it. Automatic deletion mechanisms are typically reserved for ephemeral resources or those with defined `ttl` (time-to-live) controllers, which PVCs do not have in this context.
- ✗
The PVC will be automatically bound to any available PV.
Why it's wrong here
Automatic binding of a PersistentVolumeClaim (PVC) to an available PersistentVolume (PV) relies on specific matching criteria, including the requested StorageClass. If a PVC specifies a StorageClass that does not exist, the binding controller cannot find a suitable PV, even if other PVs are available. PVs with a different StorageClass name or no StorageClass at all will not satisfy a PVC explicitly requesting a non-existent StorageClass, preventing automatic binding.
- ✓
The PVC will remain in Pending state.
Why this is correct
When a PersistentVolumeClaim (PVC) is created referencing a StorageClass that does not exist within the cluster, the dynamic provisioning mechanism cannot proceed. The Kubernetes control plane is unable to locate a provisioner associated with the specified, non-existent StorageClass to create a new PersistentVolume (PV). Consequently, the PVC will remain in a `Pending` state indefinitely, waiting for a matching PV to become available or for the specified StorageClass to be created.
- ✗
The cluster will create the storage class automatically.
Why it's wrong here
Kubernetes is a declarative system that requires explicit definition of its resources, including StorageClasses. The cluster control plane does not possess any inherent capability or logic to automatically create StorageClass objects based on user requests for them. StorageClasses are administrative resources that must be pre-defined by a cluster administrator to enable and configure dynamic storage provisioning for various storage backends.
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
Learn chapter
Configuring Core Cluster Components
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.
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.
About these practice questions
This CKA question is part of Courseiva's 302-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 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.