SAA-C03 Design High-Performing Architectures Practice Question
A trading analytics system deploys multiple EC2 instances that exchange very frequent, low-latency, east-west messages. The application team wants the instances to be placed to minimize network latency and variability. Which AWS feature should they use?
⚠ Common exam trap
Watch out — candidates often confuse the 'spread' placement group's high availability benefit with low-latency requirements, not realizing that spreading instances across racks increases network hops and latency.
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
✓
EC2 Placement Groups with the "cluster" strategy
The cluster placement group is the correct choice because it places instances into a low-latency, high-bandwidth group within a single Availability Zone, which minimizes network latency and variability for east-west traffic. This strategy is specifically designed for applications that require very frequent, low-latency communication between instances, such as trading analytics systems.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
EC2 Placement Groups with the "cluster" strategy
Why this is correct
A cluster placement group launches a group of instances into a single Availability Zone using the same underlying infrastructure segments, which lets them communicate over a low-latency, high-bandwidth, non-blocking network path. For a trading analytics workload that needs consistent inter-instance latency and minimal jitter, this placement strategy provides the closest possible physical proximity and dedicated interconnect performance. Because all instances share the same logical and physical network segment, packet round-trip times become both shorter and more predictable.
- ✗
EC2 Placement Groups with the "spread" strategy
Why it's wrong here
Spread placement groups are designed to reduce the risk of correlated failures by placing instances on distinct underlying hardware (for example, different racks). That separation can increase network latency compared to cluster placement groups, which are optimized for lowest latency.
- ✗
Auto Scaling cooldown adjustments only
Why it's wrong here
Cooldown controls how quickly Auto Scaling scales in or out after a scaling event. It does not influence where instances are physically placed on the underlying hardware, so it cannot reduce network latency variability between instances.
- ✗
Switching the instances to a larger instance size without any placement group
Why it's wrong here
Resizing to a larger instance size can increase the available CPU and per-instance network bandwidth, but it does nothing to control the physical distance or network path between the communicating instances. In a default VPC placement, instances may land on different hardware racks or even in different AZs, so network latency and jitter remain variable regardless of instance size. The higher bandwidth might mask throughput constraints, but it does not reduce the round-trip delay caused by traversing aggregation or core network switches, which is the actual source of latency variance.
Go deeper
Related to this question
About these practice questions
One of 935 original SAA-C03 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.