- A
Update the backend service auto scaling policy to use a combination of CPU and memory utilization metrics with a step scaling policy, and increase the cooldown period to allow tasks to stabilize before additional scaling actions.
Multiple metrics and step scaling with proper cooldown prevent premature scaling and handle spikes better.
- B
Reduce the target CPU utilization for the backend auto scaling policy from 70% to 50% to trigger scaling earlier and keep CPU lower.
Why wrong: Lower threshold might cause more frequent scaling but doesn't address the root cause of errors during scaling events.
- C
Change the backend service from Fargate to EC2 launch type and use larger instance types to provide more CPU capacity.
Why wrong: Fargate abstracts instances; changing launch type is unnecessary. CPU can be increased by increasing task size.
- D
Increase the desired count of the frontend service to 4 tasks to handle more requests and reduce the load on the backend service.
Why wrong: Frontend tasks do not reduce backend CPU load; the backend is the bottleneck.
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 runs a containerized microservices application on Amazon ECS with Fargate launch type. The application consists of a frontend service and a backend service. The backend service is CPU-intensive and experiences high load during business hours. The operations team observes that the frontend service sometimes returns 503 errors during peak load. The team has already configured an ECS service auto scaling policy for the backend service based on average CPU utilization with a target value of 70%. The backend service is currently running 4 tasks, and the frontend is running 2 tasks. The errors seem to correlate with the backend scaling up. Which solution should the team implement to improve the application's performance and reduce errors?
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
Update the backend service auto scaling policy to use a combination of CPU and memory utilization metrics with a step scaling policy, and increase the cooldown period to allow tasks to stabilize before additional scaling actions.
Option A is correct because the 503 errors during backend scale-up are likely caused by the backend tasks not being fully ready to handle traffic immediately after launch. By using a combination of CPU and memory utilization metrics with a step scaling policy, the team can make scaling decisions more responsive to actual load patterns. Increasing the cooldown period prevents additional scaling actions from being triggered prematurely, giving new tasks time to stabilize and reducing the window where the backend is overwhelmed, which in turn reduces frontend timeouts.
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.
- ✓
Update the backend service auto scaling policy to use a combination of CPU and memory utilization metrics with a step scaling policy, and increase the cooldown period to allow tasks to stabilize before additional scaling actions.
Why this is correct
Multiple metrics and step scaling with proper cooldown prevent premature scaling and handle spikes better.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Reduce the target CPU utilization for the backend auto scaling policy from 70% to 50% to trigger scaling earlier and keep CPU lower.
Why it's wrong here
Lower threshold might cause more frequent scaling but doesn't address the root cause of errors during scaling events.
- ✗
Change the backend service from Fargate to EC2 launch type and use larger instance types to provide more CPU capacity.
Why it's wrong here
Fargate abstracts instances; changing launch type is unnecessary. CPU can be increased by increasing task size.
- ✗
Increase the desired count of the frontend service to 4 tasks to handle more requests and reduce the load on the backend service.
Why it's wrong here
Frontend tasks do not reduce backend CPU load; the backend is the bottleneck.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume the solution is to scale earlier (Option B) or add more frontend capacity (Option D), when the real issue is the instability during the scaling event itself, which is addressed by stabilizing the scaling process with step policies and cooldowns.
Detailed technical explanation
How to think about this question
Under the hood, ECS Service Auto Scaling uses the Application Auto Scaling service, which relies on CloudWatch alarms. A step scaling policy allows you to define different scaling adjustments based on the magnitude of the breach (e.g., a larger add when CPU is >80% vs. >70%), providing finer control. The cooldown period (default 300 seconds) prevents runaway scaling by blocking additional scale-out actions until the period expires, which is critical when tasks have a long startup time or require warm-up (e.g., loading models or connecting to databases). In real-world scenarios, a backend service that takes 60–90 seconds to become healthy after launch can cause a cascade of 503 errors if new tasks are added but immediately overwhelmed by traffic before they are ready.
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 — study guide chapter
Learn the concepts, then practise the questions
- →
Continuous Improvement for Existing Solutions practice questions
Targeted practice on this topic area only
- →
All SAP-C02 questions
1,746 questions across all exam domains
- →
AWS Certified Solutions Architect Professional SAP-C02 study guide
Full concept coverage aligned to exam objectives
- →
SAP-C02 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SAP-C02 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Design Solutions for Organizational Complexity practice questions
Practise SAP-C02 questions linked to Design Solutions for Organizational Complexity.
Design for New Solutions practice questions
Practise SAP-C02 questions linked to Design for New Solutions.
Continuous Improvement for Existing Solutions practice questions
Practise SAP-C02 questions linked to Continuous Improvement for Existing Solutions.
Accelerate Workload Migration and Modernization practice questions
Practise SAP-C02 questions linked to Accelerate Workload Migration and Modernization.
SAA-C03 VPC practice questions
Practise SAP-C02 questions linked to SAA-C03 VPC.
SAA-C03 S3 lifecycle policy questions
Practise SAP-C02 questions linked to SAA-C03 S3 lifecycle policy questions.
SAA-C03 RDS Multi-AZ questions
Practise SAP-C02 questions linked to SAA-C03 RDS Multi-AZ questions.
SAA-C03 IAM policy practice questions
Practise SAP-C02 questions linked to SAA-C03 IAM policy.
SAA-C03 Route 53 failover questions
Practise SAP-C02 questions linked to SAA-C03 Route 53 failover questions.
SAA-C03 CloudFront practice questions
Practise SAP-C02 questions linked to SAA-C03 CloudFront.
SAA-C03 NAT gateway questions
Practise SAP-C02 questions linked to SAA-C03 NAT gateway questions.
SAA-C03 VPC endpoint questions
Practise SAP-C02 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Start a free SAP-C02 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 SAP-C02 question test?
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: Update the backend service auto scaling policy to use a combination of CPU and memory utilization metrics with a step scaling policy, and increase the cooldown period to allow tasks to stabilize before additional scaling actions. — Option A is correct because the 503 errors during backend scale-up are likely caused by the backend tasks not being fully ready to handle traffic immediately after launch. By using a combination of CPU and memory utilization metrics with a step scaling policy, the team can make scaling decisions more responsive to actual load patterns. Increasing the cooldown period prevents additional scaling actions from being triggered prematurely, giving new tasks time to stabilize and reducing the window where the backend is overwhelmed, which in turn reduces frontend timeouts.
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 →
Last reviewed: Jun 11, 2026
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.