The correct answer is to add a step scaling policy that adds 4 tasks when CPU exceeds 80% for 1 minute. This works because target tracking policies are inherently reactive and smooth, designed to maintain a steady-state average, but they lag during rapid CPU spikes—step scaling provides an immediate, fixed-capacity boost the moment a breach threshold is met, directly improving ECS auto scaling responsiveness during CPU spikes. On the AWS Certified Solutions Architect Professional SAP-C02 exam, this scenario tests your understanding of combining scaling strategies: target tracking for baseline stability and step scaling for burst absorption. A common trap is assuming a lower target tracking threshold or shorter cooldown alone will fix the lag, but step scaling is the only mechanism that adds capacity instantly without waiting for metric averages to stabilize. Memory tip: think “Target for the trend, Step for the spike.”
SAP-C02 Continuous Improvement for Existing Solutions Practice Question
This SAP-C02 practice question tests your understanding of continuous improvement for existing solutions. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
A company is running a containerized microservices application on Amazon ECS with Fargate launch type. The application experiences increased latency during peak hours. Upon investigation, the CPU utilization of the tasks reaches 90%. The ECS service is configured with a target tracking scaling policy based on average CPU at 70%. However, scaling is not keeping up with demand. What should a solutions architect do to improve the responsiveness of the scaling?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Add a step scaling policy that adds 4 tasks when CPU exceeds 80% for 1 minute.
Option C is correct because adding a step scaling policy provides a more aggressive and immediate scaling response when CPU exceeds 80% for 1 minute, which complements the existing target tracking policy. Target tracking scaling policies are reactive and may not scale quickly enough during rapid demand spikes, whereas step scaling can add a fixed number of tasks instantly when a breach occurs, reducing latency during peak hours.
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.
✗
Increase the task-level CPU limit to 2048 units.
Why it's wrong here
Increasing CPU limit per task does not change scaling behavior.
✗
Decrease the target tracking value to 50% average CPU.
Why it's wrong here
Lowering threshold may cause frequent scaling but not necessarily faster response to spikes.
✓
Add a step scaling policy that adds 4 tasks when CPU exceeds 80% for 1 minute.
Why this is correct
Step scaling can add capacity in larger increments, improving response to spikes.
Related concept
Read the scenario before looking for a memorised answer.
✗
Decrease the scale-in cooldown period to 60 seconds.
Why it's wrong here
Scale-in cooldown affects termination, not launch speed.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume decreasing the target tracking threshold (Option B) will make scaling faster, but they overlook that target tracking is inherently gradual and cannot match the immediate response of a step scaling policy during sudden load spikes.
Detailed technical explanation
How to think about this question
Under the hood, Amazon ECS target tracking scaling policies use a proportional-integral-derivative (PID) controller algorithm that adjusts capacity gradually to maintain the target metric, which can lag behind sudden traffic bursts. Step scaling policies, in contrast, allow you to define discrete thresholds and immediate capacity adjustments (e.g., add 4 tasks) without waiting for the PID controller to react, making them ideal for handling unpredictable spikes. In real-world scenarios, combining both policies is a common pattern: target tracking handles steady-state load, while step scaling provides a safety net for rapid demand changes.
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
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
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.
Continuous Improvement for Existing Solutions — This question tests Continuous Improvement for Existing Solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Add a step scaling policy that adds 4 tasks when CPU exceeds 80% for 1 minute. — Option C is correct because adding a step scaling policy provides a more aggressive and immediate scaling response when CPU exceeds 80% for 1 minute, which complements the existing target tracking policy. Target tracking scaling policies are reactive and may not scale quickly enough during rapid demand spikes, whereas step scaling can add a fixed number of tasks instantly when a breach occurs, reducing latency during peak hours.
What should I do if I get this SAP-C02 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 →
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 SAP-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 SAP-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.