SAA-C03 Design High-Performing Architectures Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Create a placement group with the 'spread' strategy to separate instances across underlying hardware for fault tolerance.

  Why it's wrong here

  Spread placement groups instead place each instance on its own distinct rack, each with independent power and networking hardware, to maximize fault isolation and availability. While this eliminates correlated hardware failures, it also ensures physically separated instances with longer network paths and higher inter-instance latency. For a synchronization-heavy workload, this placement inherently increases communication overhead and variability, directly counteracting the low-latency requirement.

  When this WOULD be correct

  When the question emphasizes high availability and fault isolation for a small number of critical instances (e.g., a few application servers) and explicitly states that low latency is not a primary concern, the 'spread' strategy would be correct.

• ✓

  Create a placement group with the 'cluster' strategy to place instances close together and reduce network latency.

  Why this is correct

  A cluster placement group is a hardware-level grouping within a single Availability Zone that places instances on the same high-speed, low-latency network segment. This strategy minimizes round-trip time and packet jitter between nodes, which is critical for tightly coupled workloads that frequently synchronize via message passing or shared state. Only cluster placement groups are specifically engineered to deliver the sub-millisecond, high-bandwidth interconnect (up to 100 Gbps with EFA/ENA) that such distributed applications require.

• ✗

  Use the default placement strategy and rely on Auto Scaling to keep instances from drifting to different locations.

  Why it's wrong here

  The default strategy does not guarantee physical co-location for low-latency networking. Auto Scaling changes the set of running instances over time and can introduce placement variation, so it cannot reliably eliminate network latency spikes caused by instance placement.

  When this WOULD be correct

  For a stateless web application that needs high availability and automatic scaling across multiple Availability Zones, using the default placement with Auto Scaling ensures resilience and load distribution without requiring low-latency inter-node communication.

• ✗

  Avoid placement groups and instead use Amazon S3 for inter-node messaging to minimize direct network traffic between instances.

  Why it's wrong here

  Amazon S3 is an object storage service, not a low-latency messaging bus; every inter-node communication would require an HTTP/S3 API call, adding connection setup, signing, and request processing overhead measured in tens to hundreds of milliseconds. This is orders of magnitude slower than direct instance-to-instance traffic over a VPC or a cluster placement group's network. Furthermore, S3's consistency model and per-object operations introduce additional complexity without solving the physical placement problem that causes network latency.

  When this WOULD be correct

  For a loosely coupled, asynchronous workload where instances need to share large files or state data without strict timing constraints, using Amazon S3 for inter-node messaging can reduce direct network traffic and simplify architecture.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.

Analysis generated from the official SAA-C03blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Go deeper

Related to this question