Courseiva

CV0-004 Cloud Architecture and Design Practice Question

A cloud administrator needs to provide a shared file system that can be accessed by multiple Linux-based virtual machines in the same VPC. Which storage type should be used?

⚠ Common exam trap

The trap is assuming block storage (EBS) can be shared like a file system, or that object storage (S3) is a drop-in shared file system — the exam expects recognition that 'shared file system across multiple Linux VMs' maps to file storage (EFS/NFS).

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 provides a shared, hierarchical file system (e.g., NFS, SMB) that multiple Linux VMs in the same VPC can mount simultaneously, making it ideal for shared access. In AWS, this is Amazon EFS (Elastic File System), which supports concurrent NFS mounts across EC2 instances. Block and object storage do not natively provide a shared POSIX file system for multiple Linux hosts.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Object storage

    Why it's wrong here

    Object storage exposes an HTTP API of buckets and keys, not a mountable POSIX file system that Linux VMs can mount concurrently. It is tempting because it scales cheaply and is ideal for backups, media and static content, and would be correct when applications access data via REST rather than shared file semantics.

  • ✗

    Archive storage

    Why it's wrong here

    Archive storage is a retrieval tier for infrequently accessed data with long restore latency, so it cannot serve as a live shared file system for running Linux VMs. It is tempting because it is inexpensive for long-term retention, and would be correct for compliance archives or cold backups rather than active shared workloads.

  • ✗

    Block storage

    Why it's wrong here

    Block storage presents a raw volume attached to a single instance, so it cannot be mounted concurrently by several Linux VMs as a shared POSIX file system. It is tempting because block volumes deliver high IOPS for databases, and would be the right choice for a single VM needing low-latency disk performance rather than shared access.

  • ✓

    File storage

    Why this is correct

    File storage provides a shared, POSIX-compliant file system mountable concurrently by multiple Linux instances within the same VPC, matching the requirement. Block storage attaches to a single instance, and object storage lacks native shared-mount semantics.

Quick reference

AWS S3 Storage Class Comparison

Storage ClassMin DurationRetrievalUse Case
S3 StandardNoneImmediateFrequently accessed data
S3 Standard-IA30 daysImmediateInfrequent access, rapid retrieval
S3 One Zone-IA30 daysImmediateNon-critical infrequent data
S3 Intelligent-TieringNoneImmediate–hoursUnknown or changing access patterns
S3 Glacier Instant90 daysMillisecondsArchive with instant retrieval
S3 Glacier Flexible90 daysMinutes–hoursArchive, flexible retrieval
S3 Glacier Deep Archive180 daysHoursLong-term compliance archive

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 →

How Courseiva writes practice questions · Editorial policy

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.