hardmultiple choiceObjective-mapped

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?

Question 1hardmultiple choice
Full question →

Based on the exhibit, which storage design best supports the application servers' shared working directory requirement?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

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

Distractor review

Attach one gp3 EBS volume to each instance and synchronize the files with cron jobs.

Separate EBS volumes are local to each instance, so they do not provide a shared workspace or immediate consistency across nodes.

C

Distractor review

Store the artifacts in S3 and have each node read them directly from S3 as a filesystem.

S3 is object storage, not a shared POSIX filesystem, so it does not satisfy the low-latency shared directory requirement.

D

Distractor review

Use instance store on each instance because it provides the fastest local file access.

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 trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

Related practice questions

Related SAA-C03 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Mount Amazon EFS on every EC2 instance and use it as the shared workspace. — The exhibit shows a true shared-filesystem requirement: multiple EC2 instances must read and write the same workspace, the data must persist through scale events, and the files must be visible to other nodes immediately. Amazon EFS is the AWS-native service built for that use case. It gives shared POSIX access across instances and Availability Zones, which makes it suitable for distributed build or processing pipelines that need a common directory. Why others are wrong: A separate EBS volume per instance does not create a shared directory, so each node would still be isolated. S3 is durable and scalable, but it is not a POSIX filesystem and does not provide the same low-latency shared-directory semantics. Instance store is very fast, but it is ephemeral and local, so it fails both the persistence and cross-node sharing requirements shown in the exhibit.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.