hardmulti selectObjective-mapped

The web tier of an online scheduling app runs on an Auto Scaling group behind an ALB. Traffic spikes every weekday at 13:00 when a corporate newsletter is sent. CloudWatch shows CPU averages 18% outside that window, and the current fleet uses larger instances than the load test requires. The application is stateless and can scale out in a few minutes. Which two changes should the architect recommend? Select two.

Question 1hardmulti select
Full question →

The web tier of an online scheduling app runs on an Auto Scaling group behind an ALB. Traffic spikes every weekday at 13:00 when a corporate newsletter is sent. CloudWatch shows CPU averages 18% outside that window, and the current fleet uses larger instances than the load test requires. The application is stateless and can scale out in a few minutes. Which two changes should the architect recommend? Select two.

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

Best answer

Use scheduled scaling to raise desired capacity before the known newsletter window and lower it afterward.

Scheduled scaling eliminates unnecessary baseline capacity during predictable low-demand periods and ensures extra instances are ready before the spike.

B

Best answer

Reduce the instance size to the smallest tested type that still meets peak load.

Right-sizing lowers per-instance cost while preserving performance, as long as the smaller type still passes the real load test.

C

Distractor review

Keep the current oversized instances to avoid any scaling activity.

This preserves idle capacity and directly conflicts with the goal of reducing cost in a workload with predictable demand patterns.

D

Distractor review

Replace the Auto Scaling group with Spot Instances only.

Spot Instances can be interrupted, which is risky for a customer-facing web tier that must remain available during newsletter traffic spikes.

E

Distractor review

Disable ALB health checks to save a small amount of traffic.

Health checks are essential for availability and replacement behavior; removing them does not meaningfully optimize cost and harms resilience.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

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?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Use scheduled scaling to raise desired capacity before the known newsletter window and lower it afterward. — Because the spike is predictable, scheduled scaling is the most efficient way to raise capacity only when needed and shrink it afterward. Right-sizing the instances also removes unnecessary baseline spend because the current fleet is larger than the tested requirement. Together, those changes cut idle cost without compromising the app's ability to handle the newsletter burst. Why others are wrong: Keeping oversized instances wastes money by maintaining excess capacity all day. Spot Instances are a poor fit for the front-end tier because interruptions can affect user traffic during a known spike. Disabling health checks undermines reliability and does not provide meaningful cost savings.

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.