This CKA practice question tests your understanding of storage. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. 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.
A DevOps team needs to provide persistent storage to a set of pods that all require read-write access to the same data simultaneously. Which volume type should they use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
PersistentVolumeClaim with ReadWriteMany
A PersistentVolumeClaim with ReadWriteMany (RWX) is the correct choice because it allows multiple pods to mount the same volume simultaneously with read-write access. This access mode is supported by network-based storage backends like NFS, GlusterFS, or CephFS, which provide the necessary concurrency controls for shared access across pods.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
PersistentVolumeClaim with ReadWriteMany
Why this is correct
ReadWriteMany allows multiple pods to read and write simultaneously, which is required here.
Related concept
Read the scenario before looking for a memorised answer.
✗
hostPath
Why it's wrong here
hostPath is node-specific and not suitable for multi-pod access across nodes.
✗
emptyDir
Why it's wrong here
emptyDir is ephemeral and tied to a pod's lifecycle; it cannot be shared across pods on different nodes.
✗
PersistentVolumeClaim with ReadWriteOnce
Why it's wrong here
ReadWriteOnly allows only one node to mount the volume as read-write, not multiple pods.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse ReadWriteOnce (RWO) with multi-pod access, forgetting that RWO explicitly limits the volume to a single pod mount, while ReadWriteMany (RWX) is required for simultaneous shared access.
Detailed technical explanation
How to think about this question
Under the hood, ReadWriteMany (RWX) relies on distributed filesystems or network-attached storage that implement file-level locking and consistency mechanisms (e.g., NFSv4 with delegation, CephFS with MDS). In real-world scenarios, you must ensure the underlying storage provider supports RWX; for example, many cloud CSI drivers (like AWS EBS) only support RWO, while Azure Files or NFS-based PVs support RWX. A common subtlety is that even with RWX, application-level concurrency control (e.g., file locking) may still be needed to prevent data corruption.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
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
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this CKA question in full detail.
Storage — This question tests Storage — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: PersistentVolumeClaim with ReadWriteMany — A PersistentVolumeClaim with ReadWriteMany (RWX) is the correct choice because it allows multiple pods to mount the same volume simultaneously with read-write access. This access mode is supported by network-based storage backends like NFS, GlusterFS, or CephFS, which provide the necessary concurrency controls for shared access across pods.
What should I do if I get this CKA question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 →
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.
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.
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.