CV0-004 Deployment Practice Question
A company is deploying a containerized application on Amazon ECS using the Fargate launch type. The application must be highly available and able to handle sudden increases in traffic. The operations team wants to ensure that the service automatically adjusts the number of running tasks based on CPU utilization. Which ECS service configuration should the team implement?
⚠ Common exam trap
The trap here is assuming that cluster auto scaling or custom Lambda solutions are needed for Fargate task scaling, when Application Auto Scaling directly supports it.
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
✓
Configure an Application Auto Scaling target tracking scaling policy for the ECS service using the ECSServiceAverageCPUUtilization metric.
Application Auto Scaling with a target tracking policy using the ECSServiceAverageCPUUtilization metric is the native AWS solution for automatically scaling ECS services based on CPU usage. It dynamically adjusts the desired task count to maintain the target utilization, ensuring high availability and responsiveness to traffic changes without manual intervention or custom code.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set up a CloudWatch alarm that triggers an AWS Lambda function to call the UpdateService API to change the desired count.
Why it's wrong here
While this approach can work, it requires custom scripting and maintenance. It is not the native, integrated way to scale ECS services. Application Auto Scaling provides a managed solution that eliminates the need for custom Lambda functions. This option is less efficient and more error-prone than using built-in scaling policies.
- ✗
Enable ECS cluster auto scaling by associating the cluster with a capacity provider that manages EC2 Auto Scaling groups.
Why it's wrong here
Cluster auto scaling with capacity providers is designed for EC2 launch types to manage the underlying EC2 instances, not for Fargate tasks. For Fargate, there are no EC2 instances to manage. This option does not address scaling the number of tasks based on CPU utilization.
- ✓
Configure an Application Auto Scaling target tracking scaling policy for the ECS service using the ECSServiceAverageCPUUtilization metric.
Why this is correct
Application Auto Scaling for ECS supports target tracking scaling policies that can automatically adjust the desired count of tasks based on a specified metric. The ECSServiceAverageCPUUtilization metric is a predefined metric that represents the average CPU utilization across all tasks in the service. This directly meets the requirement to scale based on CPU utilization.
- ✗
Use the ECS deployment circuit breaker to automatically roll back and scale the service when CPU utilization exceeds a threshold.
Why it's wrong here
The deployment circuit breaker is used to detect and roll back failed deployments, not to scale services based on metrics. It does not adjust task count for performance. This option confuses deployment health monitoring with runtime scaling.
Go deeper
Related to this question
About these practice questions
This CV0-004 question is part of Courseiva's 834-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This CV0-004 practice question is part of Courseiva's free CompTIA 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 CV0-004 exam.