- A
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
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
Keep the current oversized instances to avoid any scaling activity.
Why wrong: This preserves idle capacity and directly conflicts with the goal of reducing cost in a workload with predictable demand patterns.
- D
Replace the Auto Scaling group with Spot Instances only.
Why wrong: Spot Instances can be interrupted, which is risky for a customer-facing web tier that must remain available during newsletter traffic spikes.
- E
Disable ALB health checks to save a small amount of traffic.
Why wrong: Health checks are essential for availability and replacement behavior; removing them does not meaningfully optimize cost and harms resilience.
SAA-C03 Design Secure Architectures Practice Question
This SAA-C03 practice question tests your understanding of design secure architectures. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Use scheduled scaling to raise desired capacity before the known newsletter window and lower it afterward.
Option A is correct because the traffic spike is predictable (every weekday at 13:00), making scheduled scaling the most cost-effective and reliable approach. Scheduled scaling allows you to increase the desired capacity of the Auto Scaling group before the newsletter window and decrease it afterward, ensuring the application can handle the load without relying on dynamic scaling policies that might lag behind the sudden spike. This avoids over-provisioning during non-peak hours while guaranteeing capacity exactly when needed.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 scheduled scaling to raise desired capacity before the known newsletter window and lower it afterward.
Why this is correct
Scheduled scaling eliminates unnecessary baseline capacity during predictable low-demand periods and ensures extra instances are ready before the spike.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
Reduce the instance size to the smallest tested type that still meets peak load.
Why this is correct
Right-sizing lowers per-instance cost while preserving performance, as long as the smaller type still passes the real load test.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Keep the current oversized instances to avoid any scaling activity.
Why it's wrong here
This preserves idle capacity and directly conflicts with the goal of reducing cost in a workload with predictable demand patterns.
When this WOULD be correct
If the application had a long startup time (e.g., 30 minutes) and could not tolerate any scaling delay, keeping oversized instances would ensure consistent performance without scaling risk.
- ✗
Replace the Auto Scaling group with Spot Instances only.
Why it's wrong here
Spot Instances can be interrupted, which is risky for a customer-facing web tier that must remain available during newsletter traffic spikes.
When this WOULD be correct
A question where the workload is fault-tolerant, can handle interruptions (e.g., batch processing, stateless distributed jobs), and cost optimization is the primary goal. For example: 'A data processing job runs nightly and can resume from checkpoints. Which instance type minimizes cost?'
- ✗
Disable ALB health checks to save a small amount of traffic.
Why it's wrong here
Health checks are essential for availability and replacement behavior; removing them does not meaningfully optimize cost and harms resilience.
When this WOULD be correct
In a scenario where health checks are causing unnecessary instance replacements due to brief, non-critical blips (e.g., a batch processing job that temporarily spikes CPU but recovers quickly), and the application has its own internal health monitoring, disabling ALB health checks could reduce cost and churn.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.
✓Use scheduled scaling to raise desired capacity before the known newsletter window and lower it afterward.Correct answer▾
Why this is correct
Scheduled scaling eliminates unnecessary baseline capacity during predictable low-demand periods and ensures extra instances are ready before the spike.
✗Keep the current oversized instances to avoid any scaling activity.Wrong answer — click to see why▾
Why this is wrong here
Keeping oversized instances wastes cost because the app is stateless and can scale out quickly; smaller instances with scheduled scaling handle the spike more efficiently.
★ When this WOULD be the correct answer
If the application had a long startup time (e.g., 30 minutes) and could not tolerate any scaling delay, keeping oversized instances would ensure consistent performance without scaling risk.
Why candidates choose this
Candidates may think larger instances provide a safety margin and avoid scaling complexity, overlooking the cost savings from right-sizing and scheduled scaling.
✗Replace the Auto Scaling group with Spot Instances only.Wrong answer — click to see why▾
Why this is wrong here
Spot Instances can be interrupted with little notice, making them unsuitable for a workload that must handle predictable traffic spikes reliably. The application requires consistent capacity during the newsletter window, and Spot Instances alone cannot guarantee that.
★ When this WOULD be the correct answer
A question where the workload is fault-tolerant, can handle interruptions (e.g., batch processing, stateless distributed jobs), and cost optimization is the primary goal. For example: 'A data processing job runs nightly and can resume from checkpoints. Which instance type minimizes cost?'
Why candidates choose this
Candidates know Spot Instances are cheaper and may assume they can replace On-Demand instances entirely, overlooking the risk of interruptions during critical peak times.
✗Disable ALB health checks to save a small amount of traffic.Wrong answer — click to see why▾
Why this is wrong here
Disabling ALB health checks would prevent the ALB from routing traffic away from unhealthy instances, risking failed requests and reduced availability, which is unacceptable for a production scheduling app.
★ When this WOULD be the correct answer
In a scenario where health checks are causing unnecessary instance replacements due to brief, non-critical blips (e.g., a batch processing job that temporarily spikes CPU but recovers quickly), and the application has its own internal health monitoring, disabling ALB health checks could reduce cost and churn.
Why candidates choose this
Candidates may think that disabling health checks saves a trivial amount of traffic and reduces scaling activity, overlooking the critical role health checks play in maintaining high availability.
Analysis generated from the official SAA-C03blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume dynamic scaling (e.g., step scaling or target tracking) is always the best choice, but for predictable, recurring traffic patterns, scheduled scaling is more efficient because it proactively adds capacity before the load arrives, avoiding the latency of scaling in response to metrics.
Detailed technical explanation
How to think about this question
Scheduled scaling works by creating recurring actions that modify the Auto Scaling group's desired capacity at specific times, using cron-like expressions (e.g., '0 13 * * 1-5' for weekdays at 13:00 UTC). Under the hood, the Auto Scaling service adjusts the desired capacity before the scheduled time to allow instances to warm up, ensuring they are ready to serve traffic when the spike hits. In real-world scenarios, combining scheduled scaling with dynamic scaling (e.g., target tracking) provides a safety net if the spike is larger than expected.
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.
TExam Day Tips
- 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.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Design Secure Architectures — study guide chapter
Learn the concepts, then practise the questions
- →
Design Secure Architectures practice questions
Targeted practice on this topic area only
- →
All SAA-C03 questions
1,040 questions across all exam domains
- →
SAA-C03 study guide
Full concept coverage aligned to exam objectives
- →
SAA-C03 practice test guide
How to use practice tests most effectively before exam day
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.
Design Secure Architectures practice questions
Practise SAA-C03 questions linked to Design Secure Architectures.
Design Resilient Architectures practice questions
Practise SAA-C03 questions linked to Design Resilient Architectures.
Design High-Performing Architectures practice questions
Practise SAA-C03 questions linked to Design High-Performing Architectures.
Design Cost-Optimized Architectures practice questions
Practise SAA-C03 questions linked to Design Cost-Optimized Architectures.
SAA-C03 VPC practice questions
Practise SAA-C03 questions linked to SAA-C03 VPC.
SAA-C03 S3 lifecycle policy questions
Practise SAA-C03 questions linked to SAA-C03 S3 lifecycle policy questions.
SAA-C03 RDS Multi-AZ questions
Practise SAA-C03 questions linked to SAA-C03 RDS Multi-AZ questions.
SAA-C03 IAM policy practice questions
Practise SAA-C03 questions linked to SAA-C03 IAM policy.
SAA-C03 Route 53 failover questions
Practise SAA-C03 questions linked to SAA-C03 Route 53 failover questions.
SAA-C03 CloudFront practice questions
Practise SAA-C03 questions linked to SAA-C03 CloudFront.
SAA-C03 NAT gateway questions
Practise SAA-C03 questions linked to SAA-C03 NAT gateway questions.
SAA-C03 VPC endpoint questions
Practise SAA-C03 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Start a free SAA-C03 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SAA-C03 question test?
Design Secure Architectures — This question tests Design Secure Architectures — 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. — Option A is correct because the traffic spike is predictable (every weekday at 13:00), making scheduled scaling the most cost-effective and reliable approach. Scheduled scaling allows you to increase the desired capacity of the Auto Scaling group before the newsletter window and decrease it afterward, ensuring the application can handle the load without relying on dynamic scaling policies that might lag behind the sudden spike. This avoids over-provisioning during non-peak hours while guaranteeing capacity exactly when needed.
What should I do if I get this SAA-C03 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More SAA-C03 practice questions
- A content publishing system uses Lambda functions that call an unreliable third-party API. Failed events must be retaine…
- A startup runs two EC2-based workloads in the same AWS Region. Its customer-facing API is always on, and its nightly vid…
- A warehouse integration service must use shared file storage across Linux EC2 instances in multiple Availability Zones.…
- A team runs a stateless web app on Amazon EC2 behind an Application Load Balancer. During traffic spikes, new EC2 instan…
- A service in private subnets downloads product images from Amazon S3 and stores job state in DynamoDB. A NAT Gateway is…
- A static site is hosted in Amazon S3 and delivered by CloudFront. After a frontend release, the same JavaScript bundles…
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.