CKA Storage Practice Question
A pod is unable to start because the PersistentVolumeClaim it references is still in 'Pending' state. What is the most likely cause?
⚠ Common exam trap
Many candidates confuse 'Pending' state for a PVC with pod scheduling issues, thinking it is a resource constraint on the node, rather than recognizing it as a storage binding or provisioning failure.
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 PersistentVolumeClaim's storage class does not exist or cannot provision a volume
A PersistentVolumeClaim (PVC) remains in 'Pending' state when it cannot find a suitable PersistentVolume (PV) to bind to or when its storage class cannot dynamically provision one. The most common cause is that the referenced storage class does not exist, is misspelled, or lacks a provisioner that can create the volume, leaving the PVC unbound and the pod unable to start.
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 PersistentVolumeClaim's storage class does not exist or cannot provision a volume
Why this is correct
When a PersistentVolumeClaim references a non-existent or misconfigured StorageClass, the dynamic volume provisioner cannot fulfill the request. Consequently, the PVC remains stuck in a Pending state indefinitely. Because the Pod's volume mount depends on a successfully bound PVC, the Kubernetes scheduler cannot assign the Pod to a node, preventing it from starting.
- ✗
The pod's YAML has a syntax error
Why it's wrong here
If the Pod's YAML manifest contained a syntax error, the Kubernetes API server would reject the creation request entirely during the validation phase. In this scenario, the Pod object would never be instantiated in the cluster. This differs from a Pod that successfully registers but is blocked from starting due to an unbound storage dependency.
- ✗
The pod is using a hostPath volume
Why it's wrong here
A hostPath volume mounts a file or directory from the host node's filesystem directly into the Pod. This type of volume bypasses the PersistentVolumeClaim and PersistentVolume subsystem entirely, as it is defined directly within the Pod's volume specification. Therefore, a PVC issue cannot block a Pod that relies solely on hostPath storage.
- ✗
The node has insufficient CPU resources
Why it's wrong here
Insufficient CPU resources on a node will cause the scheduler to mark the Pod as unschedulable, resulting in a FailedScheduling event. However, this resource constraint does not impact the lifecycle or binding process of a PersistentVolumeClaim. PVC binding occurs independently of node CPU capacity, meaning a PVC can successfully bind even if no nodes have the resources to run the Pod.
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
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
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.