CV0-004 Cloud Architecture and Design Practice Question
Which storage type is most appropriate for a shared file system that multiple virtual machines need to mount simultaneously with read/write access?
⚠ Common exam trap
CV0-004 often tests the confusion between block and file storage for shared access; candidates may pick block storage because it is common for VM disks, but block storage is not natively shared read/write across multiple VMs without a cluster file system.
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
✓
File storage
File storage (e.g., NFS, SMB, or a shared file system like Azure Files) is designed to be mounted simultaneously by multiple clients with read/write access, providing a shared namespace and file-level locking. Block storage typically attaches to a single VM at a time (unless using shared disks with cluster-aware file systems), and object storage is accessed via HTTP APIs, not mounted as a traditional file system. Archive storage is for long-term retention and is not suitable for active shared read/write workloads.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Archive storage
Why it's wrong here
Archive storage targets long-term retention of infrequently accessed data, with retrieval latency measured in hours and no concurrent mount capability, so it cannot serve a live shared file system. It is tempting because it offers cheap capacity for compliance backups and cold datasets, where slow rehydration is acceptable and simultaneous read/write access is never required.
- ✓
File storage
Why this is correct
File storage exposes SMB or NFS shares that many VMs can mount concurrently with read/write access, satisfying the simultaneous multi-mount constraint. Block storage attaches to a single instance, and object storage uses HTTP APIs rather than mountable file protocols.
- ✗
Object storage
Why it's wrong here
Object storage exposes an HTTP API, not a POSIX file system, so multiple VMs cannot mount it concurrently for read/write with file locking. It suits storing unstructured blobs accessed by applications, not shared concurrent file access.
- ✗
Block storage
Why it's wrong here
Block storage attaches as a single-volume device to one VM at a time; concurrent read/write mounting by several VMs requires a clustered or shared file system layer. It suits low-latency single-instance volumes such as database data files.
Go deeper
Related to this question
About these practice questions
One of 834 original CV0-004 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 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.