easymultiple choiceObjective-mapped

Exhibit

Application topology:
- 12 EC2 instances in one Region
- Instances process small jobs and send frequent messages to each other
- Observed inter-node latency: 2.8 ms to 4.1 ms
- Requirement: lowest possible latency between application nodes

Based on the exhibit, which AWS feature should the team use to minimize network latency between EC2 instances that exchange messages very frequently?

Question 1easymultiple choice
Full question →

Based on the exhibit, which AWS feature should the team use to minimize network latency between EC2 instances that exchange messages very frequently?

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

Distractor review

Use a spread placement group to maximize instance separation across hardware.

Spread placement groups increase isolation, but they do not optimize for the lowest possible latency between instances.

B

Best answer

Use a cluster placement group to place instances close together.

A cluster placement group is designed for workloads that need very low network latency and high packet-per-second performance between instances. The exhibit describes frequent small-message traffic and a need for the lowest possible latency, which makes a cluster placement group the right choice. It keeps instances physically close in the AWS network for faster communication.

C

Distractor review

Use a partition placement group to distribute instances across many partitions.

Partition placement groups are better for reducing correlated hardware failures in large distributed systems, not for minimizing latency between tightly coupled nodes.

D

Distractor review

Use multiple Auto Scaling groups to spread traffic across more subnets.

More Auto Scaling groups do not reduce latency between the existing instances. This is a placement problem, not a scaling problem.

Common exam trap

Common exam trap: usable hosts are not the same as total addresses

Subnetting questions often tempt you into counting all addresses. In normal IPv4 subnets, the network and broadcast addresses are not usable host addresses.

Technical deep dive

How to think about this question

Subnetting questions test whether you can identify the network, broadcast address, usable range, mask and correct subnet. Slow down enough to calculate the block size correctly.

KKey Concepts to Remember

  • CIDR notation defines the prefix length.
  • Block size helps identify subnet boundaries.
  • Network and broadcast addresses are not usable hosts in normal IPv4 subnets.
  • The required host count determines the smallest suitable subnet.

TExam Day Tips

  • Write the block size before choosing the subnet.
  • Check whether the question asks for hosts, subnets or a specific address range.
  • Do not confuse /24, /25, /26 and /27 host counts.

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?

CIDR notation defines the prefix length.

What is the correct answer to this question?

The correct answer is: Use a cluster placement group to place instances close together. — The correct feature is a cluster placement group. The workload exchanges many small messages between instances and explicitly needs the lowest latency possible, which is exactly what cluster placement groups are meant for. They place instances close together in a way that improves inter-instance network performance. This is more appropriate than changing instance count or spreading instances for fault isolation. Why others are wrong: Spread placement groups improve resilience by separating instances, but that separation adds the opposite of what this workload needs. Partition placement groups are for large distributed applications that want failure isolation across partitions. Multiple Auto Scaling groups can change capacity, but they do not address inter-node network latency or physical placement.

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.