CV0-004 Deployment Practice Question
A cloud administrator is deploying a new application to a Kubernetes cluster using a Deployment manifest. The application requires persistent storage that must survive pod restarts and be accessible by a single pod at a time. Which Kubernetes resource should be used to define the storage?
⚠ Common exam trap
A common mix-up: candidates confuse configuration or ephemeral volumes with persistent storage, especially when the application needs data to survive pod restarts.
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
✓
PersistentVolumeClaim with accessMode ReadWriteOnce
A PersistentVolumeClaim with ReadWriteOnce provides durable storage accessible by a single node, which is appropriate for a single pod. It decouples storage from the pod lifecycle, ensuring data persists across restarts. The other options are either ephemeral, node-specific, or meant for configuration, not persistent storage.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
ConfigMap mounted as a volume
Why it's wrong here
A ConfigMap is used to inject configuration data into pods, not for persistent storage. Mounting a ConfigMap as a volume provides read-only files that are updated when the ConfigMap changes, but it does not offer durable, writable storage. It cannot satisfy the need for persistent storage that survives pod restarts.
- ✗
emptyDir volume mounted in the pod spec
Why it's wrong here
An emptyDir volume is ephemeral and tied to the pod's lifecycle. When the pod is restarted or deleted, the data is lost. It does not provide persistent storage across pod restarts. Therefore, it fails the requirement for data durability and is not suitable for stateful applications.
- ✗
hostPath volume pointing to a directory on the node
Why it's wrong here
A hostPath volume mounts a directory from the host node into the pod. While data persists on the node, it is not portable across nodes and can cause issues if the pod is rescheduled. It also does not guarantee exclusive access by a single pod and is not recommended for production persistent storage.
- ✓
PersistentVolumeClaim with accessMode ReadWriteOnce
Why this is correct
A PersistentVolumeClaim (PVC) with ReadWriteOnce allows a single node to mount the volume for read-write access, which is suitable for a single pod. It provides persistent storage that survives pod restarts. This is the standard way to request durable storage in Kubernetes and meets the requirement.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CV0-004 question from scratch — 834 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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 September 2026 · checked against the official CompTIA exam blueprint
This CV0-004 practice question is part of Courseiva's free CompTIA 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 CV0-004 exam.