The answer is to mount Amazon EFS on every EC2 instance and use it as the shared workspace. This is correct because Amazon EFS provides a fully managed, NFS-based shared file system that can be mounted concurrently on multiple EC2 instances across multiple Availability Zones, allowing all application servers to read and write files simultaneously without any additional synchronization logic. On the SAA-C03 exam, this scenario tests your ability to distinguish between block storage (EBS), object storage (S3), and shared file storage (EFS) when the requirement is a low-latency, POSIX-compliant shared working directory for EC2 instances. A common trap is choosing EBS Multi-Attach, which is limited to a single Availability Zone and a maximum of 16 Nitro-based instances, whereas EFS scales elastically across AZs. Remember the memory tip: if the question says “shared working directory” or “concurrent access from multiple EC2 instances across AZs,” think EFS—it’s the only AWS storage service that gives you a shared file system without managing the file server yourself.
SAA-C03 Practice Question: EFS provides shared, elastic, NFS file storage.
This SAA-C03 practice question tests your understanding of design high-performing architectures. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. A key principle to apply: eFS provides shared, elastic, NFS file storage.. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Deployment notes for a media-processing Auto Scaling group:
- 6 EC2 instances across 2 Availability Zones
- Each node compiles project artifacts and writes them to /workspace/output
- Other nodes must immediately see the same files for the next pipeline stage
- Files must persist when an instance is replaced or scaled in/out
- Logs show failures such as:
[ERROR] missing artifact: /workspace/output/frame_2048.png
[WARN] local copy not found after instance termination
Based on the exhibit, which storage design best supports the application servers' shared working directory requirement?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Deployment notes for a media-processing Auto Scaling group:
- 6 EC2 instances across 2 Availability Zones
- Each node compiles project artifacts and writes them to /workspace/output
- Other nodes must immediately see the same files for the next pipeline stage
- Files must persist when an instance is replaced or scaled in/out
- Logs show failures such as:
[ERROR] missing artifact: /workspace/output/frame_2048.png
[WARN] local copy not found after instance termination
A
Mount Amazon EFS on every EC2 instance and use it as the shared workspace.
EFS provides shared, persistent, POSIX-compliant file access across multiple EC2 instances and Availability Zones. That matches the requirement that all nodes see the same workspace immediately and that files survive instance replacement. It is the right choice when the application needs a common filesystem rather than an object store or local-only disk.
B
Attach one gp3 EBS volume to each instance and synchronize the files with cron jobs.
Why wrong: Separate EBS volumes are local to each instance, so they do not provide a shared workspace or immediate consistency across nodes.
C
Store the artifacts in S3 and have each node read them directly from S3 as a filesystem.
Why wrong: S3 is object storage, not a shared POSIX filesystem, so it does not satisfy the low-latency shared directory requirement.
D
Use instance store on each instance because it provides the fastest local file access.
Why wrong: Instance store is fast, but it is ephemeral and local to one machine, so other nodes cannot share it and replacements lose data.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Mount Amazon EFS on every EC2 instance and use it as the shared workspace.
Amazon EFS provides a fully managed, NFS-based shared file system that can be mounted concurrently on multiple EC2 instances across multiple Availability Zones. This directly satisfies the requirement for a shared working directory where all application servers can read and write files simultaneously without additional synchronization logic.
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Mount Amazon EFS on every EC2 instance and use it as the shared workspace.
Why this is correct
EFS provides shared, persistent, POSIX-compliant file access across multiple EC2 instances and Availability Zones. That matches the requirement that all nodes see the same workspace immediately and that files survive instance replacement. It is the right choice when the application needs a common filesystem rather than an object store or local-only disk.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
EFS provides shared, elastic, NFS file storage.
✗
Attach one gp3 EBS volume to each instance and synchronize the files with cron jobs.
Why it's wrong here
Separate EBS volumes are local to each instance, so they do not provide a shared workspace or immediate consistency across nodes.
✗
Store the artifacts in S3 and have each node read them directly from S3 as a filesystem.
Why it's wrong here
S3 is object storage, not a shared POSIX filesystem, so it does not satisfy the low-latency shared directory requirement.
✗
Use instance store on each instance because it provides the fastest local file access.
Why it's wrong here
Instance store is fast, but it is ephemeral and local to one machine, so other nodes cannot share it and replacements lose data.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is confusing shared file storage (EFS) with block storage (EBS) or object storage (S3), leading candidates to choose EBS with synchronization or S3 as a filesystem, both of which lack the native shared file system semantics required for concurrent read/write access across multiple instances.
Detailed technical explanation
How to think about this question
Amazon EFS uses the NFSv4.1 protocol and provides strong data consistency for read-after-write operations within a region. Under the hood, EFS distributes file data across multiple Availability Zones using a burst credit model for throughput, and its performance mode (General Purpose vs. Max I/O) can be tuned based on workload patterns. In a real-world scenario, a shared working directory for CI/CD build artifacts or media transcoding pipelines benefits from EFS's automatic scaling and concurrent access without the need for custom replication scripts.
KKey Concepts to Remember
EFS provides shared, elastic, NFS file storage.
EFS is POSIX-compliant, allowing multiple EC2 instances to access the same files.
Data on EFS is persistent and highly available.
EFS automatically scales storage capacity and performance.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
EFS provides shared, elastic, NFS file storage.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Review eFS provides shared, elastic, NFS file storage., then practise related SAA-C03 questions on the same topic to reinforce the concept.
The correct answer is: Mount Amazon EFS on every EC2 instance and use it as the shared workspace. — Amazon EFS provides a fully managed, NFS-based shared file system that can be mounted concurrently on multiple EC2 instances across multiple Availability Zones. This directly satisfies the requirement for a shared working directory where all application servers can read and write files simultaneously without additional synchronization logic.
What should I do if I get this SAA-C03 question wrong?
Review eFS provides shared, elastic, NFS file storage., then practise related SAA-C03 questions on the same topic to reinforce the concept.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
What is the key concept behind this question?
EFS provides shared, elastic, NFS file storage.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Based on the exhibit, which storage design best supports the application servers' shared working directory requirement?
hard
✓ A.Mount Amazon EFS on every EC2 instance and use it as the shared workspace.
B.Attach one gp3 EBS volume to each instance and synchronize the files with cron jobs.
C.Store the artifacts in S3 and have each node read them directly from S3 as a filesystem.
D.Use instance store on each instance because it provides the fastest local file access.
Why A: Amazon EFS provides a fully managed, NFS-based shared file system that can be mounted concurrently on multiple EC2 instances across multiple Availability Zones. This directly satisfies the requirement for a shared working directory where all application servers can read and write files simultaneously without additional synchronization overhead.
Last reviewed: Jun 11, 2026
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This SAA-C03 practice question is part of Courseiva's free Amazon Web Services 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 SAA-C03 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.