- A
The service has reached the maximum number of tasks defined in the auto scaling configuration; increase the maximum tasks.
The max tasks is 10 and the service is at 10, so scaling cannot occur. Increasing the max allows scaling.
- B
The scaling policy is not properly configured; recreate it with a lower target value.
Why wrong: The policy is configured and the metric is above target, but scaling is blocked by the max.
- C
The CloudWatch metric is not being emitted correctly; check the metric namespace.
Why wrong: The metric is showing, so it is being emitted.
- D
The ECS service is using Fargate, which does not support target tracking scaling policies.
Why wrong: Fargate supports target tracking scaling policies.
Quick Answer
The answer is that the auto scaling is not working because the ECS Fargate service has already reached the maximum task limit of 10 defined in the auto scaling configuration. Even though the target tracking scaling policy is set to a 50% CPU target and actual utilization is at 70%, the scaling policy cannot trigger a scale-out event because it is blocked by the hard cap on the maximum number of tasks. This scenario tests your understanding of how ECS Service Auto Scaling respects the min/max boundaries, a common pitfall on the AWS Certified DevOps Engineer Professional DOP-C02 exam where engineers often overlook that a scaling policy cannot exceed the configured maximum. The fix is straightforward: increase the maximum tasks in the auto scaling configuration to allow further scale-out. Remember the trap: a scaling policy can only request tasks within the range you set—if you hit the max, scaling stops regardless of demand. Memory tip: “Max tasks = scaling ceiling; hit it, and your policy is just a wish.”
DOP-C02 Incident and Event Response Practice Question
This DOP-C02 practice question tests your understanding of incident and event response. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 microservices application on Amazon ECS with Fargate. The application includes a service that processes messages from an Amazon SQS queue. Recently, the processing time has increased, and the SQS queue depth is growing. The CloudWatch metrics show that the ECS service's CPU utilization is consistently around 70%, memory utilization is 80%, and the number of running tasks is at the maximum allowed (10). The service is configured with a target tracking scaling policy based on CPU utilization with a target value of 50%. However, the auto scaling does not seem to be adding tasks. The engineer checks the ECS service events and finds no scaling activity. What is the MOST likely reason the auto scaling is not working, and what action should be taken to resolve the issue?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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
The service has reached the maximum number of tasks defined in the auto scaling configuration; increase the maximum tasks.
The auto scaling is not adding tasks because the ECS service has already reached the maximum number of tasks defined in the auto scaling configuration (10). With CPU utilization at 70% and the target tracking policy set to 50%, the policy would normally trigger scale-out actions, but since the maximum task count is already hit, no scaling activity occurs. The engineer must increase the maximum tasks in the auto scaling configuration to allow further scale-out.
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.
- ✓
The service has reached the maximum number of tasks defined in the auto scaling configuration; increase the maximum tasks.
Why this is correct
The max tasks is 10 and the service is at 10, so scaling cannot occur. Increasing the max allows scaling.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The scaling policy is not properly configured; recreate it with a lower target value.
Why it's wrong here
The policy is configured and the metric is above target, but scaling is blocked by the max.
- ✗
The CloudWatch metric is not being emitted correctly; check the metric namespace.
Why it's wrong here
The metric is showing, so it is being emitted.
- ✗
The ECS service is using Fargate, which does not support target tracking scaling policies.
Why it's wrong here
Fargate supports target tracking scaling policies.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may assume the scaling policy itself is misconfigured or that Fargate lacks support for target tracking, when in reality the issue is the hard cap on the maximum number of tasks preventing any scale-out action.
Trap categories for this question
Command / output trap
The metric is showing, so it is being emitted.
Detailed technical explanation
How to think about this question
Target tracking scaling policies in ECS work by creating CloudWatch alarms that monitor the specified metric (e.g., CPU utilization) and adjust the desired count of tasks. When the desired count equals the maximum task count, the policy cannot increase further, and scaling activity stops. This is a common pitfall where operators forget to set an adequate maximum task limit, especially under variable load. In production, it's critical to monitor the 'ServiceAutoScalingMaxCapacity' and set it based on peak load estimates.
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.
- →
Incident and Event Response — study guide chapter
Learn the concepts, then practise the questions
- →
Incident and Event Response practice questions
Targeted practice on this topic area only
- →
All DOP-C02 questions
1,740 questions across all exam domains
- →
AWS Certified DevOps Engineer Professional DOP-C02 study guide
Full concept coverage aligned to exam objectives
- →
DOP-C02 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related DOP-C02 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Configuration Management and IaC practice questions
Practise DOP-C02 questions linked to Configuration Management and IaC.
Resilient Cloud Solutions practice questions
Practise DOP-C02 questions linked to Resilient Cloud Solutions.
Monitoring and Logging practice questions
Practise DOP-C02 questions linked to Monitoring and Logging.
Incident and Event Response practice questions
Practise DOP-C02 questions linked to Incident and Event Response.
Security and Compliance practice questions
Practise DOP-C02 questions linked to Security and Compliance.
SDLC Automation practice questions
Practise DOP-C02 questions linked to SDLC Automation.
DOP-C02 fundamentals practice questions
Practise DOP-C02 questions linked to DOP-C02 fundamentals.
DOP-C02 scenario practice questions
Practise DOP-C02 questions linked to DOP-C02 scenario.
DOP-C02 troubleshooting practice questions
Practise DOP-C02 questions linked to DOP-C02 troubleshooting.
Practice this exam
Start a free DOP-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 DOP-C02 question test?
Incident and Event Response — This question tests Incident and Event Response — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The service has reached the maximum number of tasks defined in the auto scaling configuration; increase the maximum tasks. — The auto scaling is not adding tasks because the ECS service has already reached the maximum number of tasks defined in the auto scaling configuration (10). With CPU utilization at 70% and the target tracking policy set to 50%, the policy would normally trigger scale-out actions, but since the maximum task count is already hit, no scaling activity occurs. The engineer must increase the maximum tasks in the auto scaling configuration to allow further scale-out.
What should I do if I get this DOP-C02 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 DOP-C02 practice questions
- A company uses AWS CodePipeline with a multi-branch strategy. A new feature branch triggers a pipeline that runs unit te…
- A development team uses AWS CodeBuild to compile a Java application and run unit tests. The build takes 30 minutes, but…
- A company uses AWS CodePipeline with multiple stages: Source (Amazon S3), Build (AWS CodeBuild), and Deploy (AWS CodeDep…
- A company uses AWS CodeCommit for source control. Developers frequently push large binary files (e.g., compiled JARs) to…
- An organization uses AWS CodePipeline to orchestrate deployments to multiple environments (dev, test, prod). Each enviro…
- A company uses AWS Key Management Service (KMS) to encrypt data at rest in Amazon S3. The security team wants to ensure…
Last reviewed: Jun 11, 2026
This DOP-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 DOP-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.