SAA-C03 Design Secure Architectures Practice Question
Exhibit
Application topology: - 4 Amazon EC2 instances run in a single Availability Zone - Each node exchanges small TCP messages with every other node - 99th percentile message latency increased after adding two more nodes - Instances currently launch in the default placement CloudWatch note: Network throughput is not saturated, but packet round-trip time between instances is higher than expected.
Based on the exhibit, what should the architect recommend to reduce inter-node latency for this workload?
⚠ Common exam trap
It's easy for candidates to confuse placement group types, assuming 'spread' or 'partition' can also reduce latency, when only cluster placement groups are designed for low-latency, high-throughput networking within a single AZ.
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
✓
Launch the instances in a cluster placement group within the same Availability Zone.
A cluster placement group provides the lowest possible latency and highest packet-per-second performance by ensuring instances are placed in close physical proximity within a single Availability Zone. This is ideal for tightly coupled, high-performance computing workloads that require low inter-node latency.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a spread placement group so each instance is placed on separate hardware.
Why it's wrong here
A spread placement group places each EC2 instance on its own distinct hardware, maximizing availability for small fault domains, but it intentionally scatters instances across different racks and often switches. That physical separation increases hop distance and network latency between application nodes, which is the opposite of what a cluster placement group would provide for this low-latency messaging workload. It also limits the number of instances you can place in a single Availability Zone, making it impractical for a large, tightly coupled fleet.
When this WOULD be correct
When the question emphasizes high availability and fault tolerance, such as avoiding simultaneous failures from a single rack or hardware, and latency is not the primary concern.
- ✓
Launch the instances in a cluster placement group within the same Availability Zone.
Why this is correct
A cluster placement group places instances close together in a single Availability Zone, which is the best choice for workloads that exchange many small messages and need very low network latency. This design is common for tightly coupled compute, analytics, and HPC-style applications. Because the workload is not bandwidth-saturated but latency-sensitive, proximity matters more than broader distribution.
- ✗
Move the instances into different Availability Zones to improve fault tolerance.
Why it's wrong here
Moving instances into different Availability Zones does improve fault tolerance, but this workload is latency-sensitive and relies on frequent, small inter-instance messages. Cross-AZ traffic traverses more physical network distance and typically adds round-trip latency, which directly undermines the application's performance. Furthermore, inter-AZ traffic incurs data-transfer costs, so it is also the wrong economic choice for a tightly coupled workload that should stay within one place.
When this WOULD be correct
When the requirement is to maximize fault tolerance and high availability, such as for a multi-AZ deployment of a critical application that must survive an AZ failure, even at the cost of higher latency.
- ✗
Use a partition placement group to balance traffic across partitions.
Why it's wrong here
Partition placement groups help isolate groups of instances from one another for availability and scale. They are not the best option when the primary goal is the lowest possible latency between all nodes in the same application.
When this WOULD be correct
For a large-scale distributed data processing workload (e.g., Hadoop, Kafka) that needs to tolerate rack-level failures while maintaining high throughput, a partition placement group would be correct. The question would emphasize fault isolation across racks rather than minimizing latency.
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.
✓Launch the instances in a cluster placement group within the same Availability Zone.Correct answer▾
Why this is correct
A cluster placement group places instances close together in a single Availability Zone, which is the best choice for workloads that exchange many small messages and need very low network latency. This design is common for tightly coupled compute, analytics, and HPC-style applications. Because the workload is not bandwidth-saturated but latency-sensitive, proximity matters more than broader distribution.
✗Use a spread placement group so each instance is placed on separate hardware.Wrong answer — click to see why▾
Why this is wrong here
A spread placement group places instances on separate hardware to reduce correlated failures, but it does not minimize inter-node latency; in fact, it may increase latency due to physical separation.
★ When this WOULD be the correct answer
When the question emphasizes high availability and fault tolerance, such as avoiding simultaneous failures from a single rack or hardware, and latency is not the primary concern.
Why candidates choose this
Candidates may confuse 'separate hardware' with 'closer proximity,' assuming that spreading instances reduces network hops, but spread groups actually increase physical distance between instances.
✗Move the instances into different Availability Zones to improve fault tolerance.Wrong answer — click to see why▾
Why this is wrong here
Moving instances into different Availability Zones increases inter-node latency due to physical separation, which contradicts the goal of reducing latency.
★ When this WOULD be the correct answer
When the requirement is to maximize fault tolerance and high availability, such as for a multi-AZ deployment of a critical application that must survive an AZ failure, even at the cost of higher latency.
Why candidates choose this
Candidates may confuse fault tolerance with performance optimization, or assume that distributing across AZs always improves reliability without considering latency trade-offs.
✗Use a partition placement group to balance traffic across partitions.Wrong answer — click to see why▾
Why this is wrong here
A partition placement group spreads instances across logical partitions, each on separate racks, to reduce correlated failures for large distributed workloads like HDFS or Cassandra. It does not minimize inter-node latency, which requires the low-latency, high-bandwidth network of a cluster placement group within a single AZ.
★ When this WOULD be the correct answer
For a large-scale distributed data processing workload (e.g., Hadoop, Kafka) that needs to tolerate rack-level failures while maintaining high throughput, a partition placement group would be correct. The question would emphasize fault isolation across racks rather than minimizing latency.
Why candidates choose this
Candidates may confuse partition placement groups with cluster placement groups, thinking that 'partition' implies grouping instances together for performance, or they may overvalue fault tolerance features without recognizing the primary latency requirement.
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
About these practice questions
This SAA-C03 question is part of Courseiva's 935-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.