You have a PersistentVolumeClaim with accessModes set to ReadWriteOnce. You try to mount it as read-write on two pods running on different nodes. What is the likely outcome?

medium📝 Troubleshoot Q14 of 15

Kubernetes - Persistent Storage

ABoth pods mount the volume read-write successfully.

BOnly one pod mounts the volume read-write; the other fails to mount.

CBoth pods mount the volume read-only.

DBoth pods fail to mount the volume.

Step-by-Step Solution

Solution:

Step 1: Recall ReadWriteOnce limitation
ReadWriteOnce allows only one node to mount the volume as read-write at a time.
Step 2: Analyze mounting on two nodes
Since pods are on different nodes, only one pod can mount read-write; the other pod's mount will fail.
Final Answer:
Only one pod mounts the volume read-write; the other fails to mount. -> Option B
Quick Check:
ReadWriteOnce = single node writer [OK]

Quick Trick: ReadWriteOnce limits to one node writer [OK]

Common Mistakes:

Assuming both pods can mount read-write
Thinking volume auto-switches to read-only
Believing both pods fail to mount

Master "Persistent Storage" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Kubernetes Quizzes

You have a PersistentVolumeClaim with accessModes set to ReadWriteOnce. You try to mount it as read-write on two pods running on different nodes. What is the likely outcome?

Step 1: Recall ReadWriteOnce limitation

Step 2: Analyze mounting on two nodes

Final Answer:

Quick Check:

Want More Practice?