- A
The pod that references the PVC is not scheduled yet
Why wrong: 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.
- B
No PersistentVolume exists that matches the PVC's storage class and size requirements
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.
- C
The PVC is using a StorageClass that does not exist
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.
- D
The PVC's access mode is 'ReadWriteMany' but the underlying storage only supports 'ReadWriteOnce'
Why wrong: 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.
- E
The cluster's dynamic provisioner is unavailable or misconfigured
Why wrong: 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.
PersistentVolumeClaim Pending — Reasons and Solutions
This KCNA practice question tests your understanding of kubernetes fundamentals. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. A key principle to apply: persistentVolumeClaim (PVC). Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which TWO of the following are valid reasons that a PersistentVolumeClaim (PVC) may remain in 'Pending' state?
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.
Key principle: PersistentVolumeClaim (PVC)
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.
Related concept
PersistentVolumeClaim (PVC)
- ✓
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.
Related concept
PersistentVolumeClaim (PVC)
- ✗
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.
Common exam traps
Common exam trap: answer the scenario, not the keyword
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.
Detailed technical explanation
How to think about this question
Under the hood, the Kubernetes PersistentVolume controller continuously reconciles PVCs and PVs. When a PVC is created, the controller checks for a matching PV based on storage class, access modes, and capacity. If no match is found, the PVC remains in Pending state. If a StorageClass with a dynamic provisioner is specified, the provisioner must be available and correctly configured; otherwise, the PVC will also remain Pending. In real-world scenarios, misconfigured cloud provider credentials or missing CSI driver plugins often cause dynamic provisioning to fail, leaving PVCs stuck in Pending.
KKey Concepts to Remember
- PersistentVolumeClaim (PVC)
- StorageClass
- Pending State
- Dynamic Provisioning
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
PersistentVolumeClaim (PVC)
Real-world example
How this comes up in practice
A practitioner preparing for the KCNA exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. PersistentVolumeClaim (PVC) Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
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 |
What to study next
Got this wrong? Here's your next step.
Review persistentVolumeClaim (PVC), then practise related KCNA questions on the same topic to reinforce the concept.
- →
Kubernetes Fundamentals — study guide chapter
Learn the concepts, then practise the questions
- →
Kubernetes Fundamentals practice questions
Targeted practice on this topic area only
- →
All KCNA questions
997 questions across all exam domains
- →
Kubernetes and Cloud Native Associate KCNA study guide
Full concept coverage aligned to exam objectives
- →
KCNA practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related KCNA practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Kubernetes Fundamentals practice questions
Practise KCNA questions linked to Kubernetes Fundamentals.
Container Orchestration practice questions
Practise KCNA questions linked to Container Orchestration.
Cloud Native Architecture practice questions
Practise KCNA questions linked to Cloud Native Architecture.
Cloud Native Observability practice questions
Practise KCNA questions linked to Cloud Native Observability.
Cloud Native Application Delivery practice questions
Practise KCNA questions linked to Cloud Native Application Delivery.
KCNA fundamentals practice questions
Practise KCNA questions linked to KCNA fundamentals.
KCNA scenario practice questions
Practise KCNA questions linked to KCNA scenario.
KCNA troubleshooting practice questions
Practise KCNA questions linked to KCNA troubleshooting.
Practice this exam
Start a free KCNA practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this KCNA question test?
Kubernetes Fundamentals — This question tests Kubernetes Fundamentals — PersistentVolumeClaim (PVC).
What is the correct answer to this question?
The correct answer is: 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.
What should I do if I get this KCNA question wrong?
Review persistentVolumeClaim (PVC), then practise related KCNA questions on the same topic to reinforce the concept.
What is the key concept behind this question?
PersistentVolumeClaim (PVC)
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More KCNA practice questions
- Which CNCF project provides a graduated service mesh implementation that includes features like traffic management, secu…
- A pod in the 'production' namespace is in a CrashLoopBackOff state. The pod has been running successfully for several da…
- You need to ensure that a pod runs on a node with SSD storage. How can you achieve this?
- Match each Kubernetes resource to its primary purpose.
- Match each Kubernetes security concept to its definition.
- Which three of the following are valid methods to create or update resources in Kubernetes? (Choose three.)
Last reviewed: Jul 4, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.