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.

• ✗

  Use a spread placement group to distribute instances across multiple underlying hardware to improve overall availability.

  Why it's wrong here

  Spread placement groups are optimized for fault isolation across distinct underlying hardware. They intentionally reduce the likelihood of all instances sharing the same failure domain, which typically increases the variability in network paths rather than minimizing latency/jitter between instances.

• ✓

  Use a cluster placement group so the instances are placed close together to reduce latency and jitter.

  Why this is correct

  A cluster placement group is the optimal choice because it launches instances in a single Availability Zone on the same underlying hardware and low-latency network backbone. This physical proximity minimizes network hop count and inter-instance communication latency, while the consistent network path reduces jitter—variation in packet delivery times—which is critical for a jitter-sensitive trading analytics system. The group is designed specifically for tightly coupled, high-performance workloads that require high-throughput, low-latency inter-node traffic, and when combined with enhanced networking, it can achieve microsecond-level latency and high bandwidth. Note that this comes at the cost of fault isolation, as a single hardware failure can affect all instances, but for this performance-driven use case, that trade-off is acceptable.

• ✗

  Use no placement group and rely on the Auto Scaling group to balance instance placement automatically.

  Why it's wrong here

  Auto Scaling helps with capacity and scaling, but it does not guarantee proximity of instances for low-latency inter-node traffic. Without a placement group, placement is determined by normal scheduling, which may not keep instances close together.

• ✗

  Use a partition placement group so each instance is assigned to separate failure domains for low variance.

  Why it's wrong here

  Partition placement groups are designed to distribute instances across partitions for capacity scaling with fault isolation (each partition is its own failure domain). They are not intended to keep instances in a tightly coupled network layout, so they do not best satisfy jitter-sensitive, low-latency requirements.

Go deeper

Related to this question