KCNA PersistentVolumeClaim (PVC) Practice Question
Which TWO of the following are valid reasons that a PersistentVolumeClaim (PVC) may remain in 'Pending' state?
⚠ Common exam trap
Candidates often assume only PV unavailability causes Pending, but a missing or misconfigured StorageClass is equally valid. The KCNA exam may test that PVCs using a non-existent StorageClass will also remain Pending.
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
✓
No PersistentVolume exists that matches the PVC's storage class and size requirements
A PersistentVolumeClaim (PVC) stays in 'Pending' state until a suitable PersistentVolume (PV) is available to bind. Two common reasons are: (1) No existing PV matches the PVC's storage class and size requirements (static provisioning failure), and (2) The PVC references a StorageClass that does not exist, preventing dynamic provisioning. Other reasons like pod scheduling or dynamic provisioner unavailability are not among the two correct answers.
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 pod that references the PVC is not scheduled yet
Why it's wrong here
The pod that references the PVC is not scheduled yet – Incorrect. PVC binding is independent of pod scheduling; the PVC can bind before the pod is scheduled.
- ✓
No PersistentVolume exists that matches the PVC's storage class and size requirements
Why this is correct
No PersistentVolume exists that matches the PVC's storage class and size requirements – Correct. If no matching PV exists, the PVC cannot bind and remains Pending.
- ✓
The PVC is using a StorageClass that does not exist
Why this is correct
The PVC is using a StorageClass that does not exist – Correct. If the specified StorageClass does not exist, dynamic provisioning cannot create a PV, leaving the PVC Pending.
- ✗
The PVC's access mode is 'ReadWriteMany' but the underlying storage only supports 'ReadWriteOnce'
Why it's wrong here
The PVC's access mode is 'ReadWriteMany' but the underlying storage only supports 'ReadWriteOnce' – Incorrect. While this would prevent binding, it is a specific subset of 'no matching PV' and not a general reason listed as correct here.
- ✗
The cluster's dynamic provisioner is unavailable or misconfigured
Why it's wrong here
The cluster's dynamic provisioner is unavailable or misconfigured – Incorrect. Although true, the question requires exactly two correct answers; B and C are the intended correct reasons.
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
About these practice questions
One of 833 original KCNA 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 KCNA 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 KCNA exam.