mediummultiple choiceObjective-mapped

A team runs an EC2-based API on a single Auto Scaling group (ASG). Over the last month, they observed: - Average CPU utilization is ~15%. - p95 latency is stable and within the performance target. - The attached EBS volumes are gp3, provisioned with high baseline IOPS/throughput “just to be safe,” but CloudWatch shows consistently low utilization of those provisioned IOPS/throughput limits. They want to reduce monthly cost while maintaining current performance. Which action is the best cost-optimized choice?

Question 1mediummultiple choice
Full question →

A team runs an EC2-based API on a single Auto Scaling group (ASG). Over the last month, they observed: - Average CPU utilization is ~15%. - p95 latency is stable and within the performance target. - The attached EBS volumes are gp3, provisioned with high baseline IOPS/throughput “just to be safe,” but CloudWatch shows consistently low utilization of those provisioned IOPS/throughput limits. They want to reduce monthly cost while maintaining current performance. Which action is the best cost-optimized choice?

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

Stop resizing EBS and only scale out the ASG during peak traffic, because changing EBS performance settings risks latency spikes.

The problem includes both overprovisioned gp3 performance and underutilized CPU. Only scaling out during peaks increases compute cost and does not address the consistently low gp3 IOPS/throughput utilization that is already wasting money.

B

Best answer

Right-size both the compute and the gp3 volumes: reduce the EC2 instance size (via the ASG launch template/desired capacity configuration) and update gp3 IOPS/throughput settings to match observed utilization while keeping p95 latency targets.

The metrics indicate headroom that is not being used (low CPU, stable latency, and low gp3 utilization). The most direct cost optimization is to reduce overprovisioned spend by right-sizing the instance type and tuning gp3 IOPS/throughput to match actual demand. Because performance and latency are already stable, these changes are the most likely to reduce cost without degrading performance.

C

Distractor review

Switch the instances to EC2 Spot immediately, because Spot always lowers costs without adding operational risk or affecting performance.

Spot can reduce costs, but it introduces possible interruptions and capacity variability. The prompt does not state the workload can safely handle interruptions, and it does not guarantee that performance will remain stable under Spot interruptions/replacements.

D

Distractor review

Move the workload to a larger instance class and keep the gp3 settings unchanged to avoid operational tuning work.

Using larger instances increases compute cost and does not address the unnecessary gp3 provisioned IOPS/throughput that is already underutilized. This contradicts the goal of reducing cost while maintaining performance.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

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?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Right-size both the compute and the gp3 volumes: reduce the EC2 instance size (via the ASG launch template/desired capacity configuration) and update gp3 IOPS/throughput settings to match observed utilization while keeping p95 latency targets. — Given low CPU (~15%), stable p95 latency, and gp3 volumes provisioned far above observed utilization, the best cost-optimized approach is right-sizing. Reduce the EC2 instance size (ASG/launch template configuration) and tune gp3 IOPS/throughput down to match current usage patterns, targeting cost reduction while maintaining the existing performance envelope. Scaling out during peaks or avoiding EBS changes does not resolve the waste from low gp3 utilization. Spot is not guaranteed safe without considering interruption tolerance. Moving to larger instances increases cost and leaves the overprovisioned gp3 settings in place.

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.