Scheduled scaling is the correct choice because it directly addresses predictable traffic patterns by allowing you to define time-based capacity adjustments that align with known daily cycles. This policy works by automatically increasing the desired capacity of your Auto Scaling group during business hours and decreasing it at night, ensuring performance meets demand while optimizing costs through reduced instance count during off-peak periods. On the AWS Certified SysOps Administrator Associate SOA-C02 exam, this scenario tests your ability to distinguish between reactive policies like dynamic scaling and proactive policies like scheduled scaling; a common trap is choosing a dynamic policy for predictable loads, which would add unnecessary latency and complexity. Remember that scheduled scaling is ideal when the traffic pattern is both regular and known in advance, making it the most efficient and hands-off approach. A useful memory tip: if you can set your watch by the traffic, schedule your scaling.
SOA-C02 Cost and Performance Optimization Practice Question
This SOA-C02 practice question tests your understanding of cost and performance optimization. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. A key principle to apply: scheduled scaling adjusts capacity at predefined times.. 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.
A company runs a web application on Amazon EC2 instances that are part of an Auto Scaling group. The application's traffic is predictable with regular peaks during business hours and low traffic at night. The SysOps administrator wants to optimize costs while ensuring that performance meets demand. The administrator also needs to minimize manual intervention. Which scaling policy should be used?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "minimum / minimize"
Why it matters: Asks for the least resource use — fewest addresses, smallest subnet, lowest overhead. Eliminate over-provisioned options even if they would technically work.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Scheduled scaling
Scheduled scaling is the correct choice because the traffic pattern is predictable with regular peaks during business hours and low traffic at night. This policy allows the administrator to define specific times to increase or decrease the desired capacity of the Auto Scaling group, matching capacity to demand without manual intervention and optimizing costs by reducing instances during off-peak hours.
Key principle: Scheduled scaling adjusts capacity at predefined times.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Scheduled scaling
Why this is correct
Scheduled scaling adjusts capacity at predefined times, matching predictable patterns with no manual effort after setup.
Clue confirmation
The clue word "minimum / minimize" in the question point toward this answer.
Related concept
Scheduled scaling adjusts capacity at predefined times.
✗
Target tracking scaling
Why it's wrong here
Target tracking adjusts capacity based on a metric threshold (e.g., CPU), which is reactive and may not perfectly time the morning peak.
✗
Simple scaling
Why it's wrong here
Simple scaling adds or removes instances based on CloudWatch alarms, but it is reactive and may have cool-down periods that cause delays.
✗
Manual scaling
Why it's wrong here
Manual scaling requires the administrator to adjust the desired capacity by hand, which is not automated and prone to human error.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse target tracking scaling with scheduled scaling, assuming dynamic metric-based policies are always optimal, but for predictable patterns, scheduled scaling provides more precise cost control and avoids unnecessary scaling events.
Detailed technical explanation
How to think about this question
Scheduled scaling in AWS Auto Scaling uses cron-like expressions (e.g., '0 8 * * 1-5' for 8 AM weekdays) to set a specific capacity at a future time. Under the hood, it creates a scheduled action that modifies the desired capacity of the Auto Scaling group at the specified time, overriding any other scaling policies during that period. This approach is ideal for predictable workloads, such as a retail website that sees traffic spikes during lunch hours, as it avoids the latency of metric-based scaling and ensures capacity is ready before demand arrives.
KKey Concepts to Remember
Scheduled scaling adjusts capacity at predefined times.
It is ideal for predictable traffic patterns.
Eliminates manual intervention after initial setup.
Proactively scales capacity up or down.
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
Scheduled scaling adjusts capacity at predefined times.
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.
Review scheduled scaling adjusts capacity at predefined times., then practise related SOA-C02 questions on the same topic to reinforce the concept.
Cost and Performance Optimization — This question tests Cost and Performance Optimization — Scheduled scaling adjusts capacity at predefined times..
What is the correct answer to this question?
The correct answer is: Scheduled scaling — Scheduled scaling is the correct choice because the traffic pattern is predictable with regular peaks during business hours and low traffic at night. This policy allows the administrator to define specific times to increase or decrease the desired capacity of the Auto Scaling group, matching capacity to demand without manual intervention and optimizing costs by reducing instances during off-peak hours.
What should I do if I get this SOA-C02 question wrong?
Review scheduled scaling adjusts capacity at predefined times., then practise related SOA-C02 questions on the same topic to reinforce the concept.
Are there clue words in this question I should notice?
Yes — watch for: "minimum / minimize". Asks for the least resource use — fewest addresses, smallest subnet, lowest overhead. Eliminate over-provisioned options even if they would technically work.
What is the key concept behind this question?
Scheduled scaling adjusts capacity at predefined times.
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 →
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.
This SOA-C02 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 SOA-C02 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.