CV0-004 Cloud Architecture and Design Practice Question
A cloud architect is designing a shared file system for a machine learning cluster where multiple Linux virtual machines must read and write the same training data concurrently with POSIX semantics. The workload runs for several weeks and needs high aggregate throughput. Which storage solution should the architect select?
⚠ Common exam trap
The trap here is assuming that fast local SSDs or object storage can substitute for a shared POSIX file system, when neither provides concurrent file semantics across many nodes.
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
✓
A managed network file system that supports concurrent POSIX access and scales throughput with provisioned capacity.
A managed network file system is purpose-built for many clients mounting the same POSIX namespace concurrently. It provides shared file locking and metadata, and its throughput commonly scales with provisioned capacity, making it suitable for a long-running, high-throughput machine learning workload that requires consistent concurrent access.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
An object storage bucket accessed through a REST API for all training data reads and writes.
Why it's wrong here
Object storage is accessed through HTTP APIs and does not present a POSIX file system, so applications expecting standard file operations cannot use it directly without a gateway or FUSE layer that adds latency and complexity. It also does not provide the concurrent file locking and metadata semantics that a shared POSIX workload depends on.
- ✗
A local SSD on each virtual machine with a scheduled rsync job to synchronize data.
Why it's wrong here
Local SSDs are fast but isolated per instance, and periodic rsync creates windows where nodes see inconsistent data. Concurrent writes from multiple nodes can overwrite each other, and there is no shared locking. This approach cannot guarantee POSIX semantics or consistent views across the cluster during a multi-week training run.
- ✓
A managed network file system that supports concurrent POSIX access and scales throughput with provisioned capacity.
Why this is correct
A managed network file system designed for concurrent access provides the shared POSIX namespace the cluster needs, and its throughput often scales with provisioned capacity, which suits a multi-week, high-throughput training job. It supports many clients mounting the same file system simultaneously, so all virtual machines see consistent file metadata and can read and write in parallel.
- ✗
A block storage volume attached to each virtual machine individually.
Why it's wrong here
Block volumes are typically attached to a single instance at a time and do not provide a shared namespace across many machines. Even where multi-attach is possible, the guest operating system must manage a clustered file system to avoid corruption, adding complexity. This does not deliver the simple concurrent POSIX file access the machine learning cluster requires.
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.