EX280 Storage And Persistent Volumes Practice Question
Which TWO conditions will prevent a pod from successfully mounting a PersistentVolumeClaim?
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 is in a Pending state because it failed to bind or provision.
Mismatched access modes and failure of the CSI driver to attach the volume to the node will prevent pod mounting.
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 is running in the default project.
Why it's wrong here
Project location does not block mounting.
- ✓
The PVC is in a Pending state because it failed to bind or provision.
Why this is correct
An unbound PVC cannot be mounted by a pod.
- ✓
The volume is already attached to another node and cannot be multi-attached (RWO constraint).
Why this is correct
RWO attachment conflicts prevent pod scheduling/mounting on new nodes.
- ✗
The StorageClass has allowVolumeExpansion set to true.
Why it's wrong here
Expansion permissions do not block mounting.
- ✗
The pod namespace has excess CPU limits.
Why it's wrong here
CPU limits do not prevent volume mounting.
About these practice questions
One of 509 original EX280 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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed August 2026 · checked against the official Red Hat exam blueprint
This EX280 practice question is part of Courseiva's free Red Hat 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 EX280 exam.