An ECS service runs on EC2 capacity. During peak traffic, tasks frequently wait for available container instances. The team wants faster scale-out for the underlying EC2 capacity when tasks increase. What is the best first architectural step?

Tune the container health check settings so tasks stop failing and stay running.

Health checks affect task readiness and replacement behavior, but they don’t create more EC2 capacity. If no container instances are available, tasks still cannot be placed. Scaling container health checks alone won’t address placement delays.

Pin all tasks to a single Availability Zone to reduce placement overhead.

Restricting tasks to one Availability Zone can reduce placement options and increase the likelihood of insufficient capacity. It may also reduce availability. It does not automatically trigger EC2 scale-out when tasks increase.

Switch the tasks to run only on Fargate so EC2 scaling is no longer relevant.

Migrating to Fargate changes the compute model but is not the best first step for optimizing current ECS-on-EC2 placement latency. The question asks about faster EC2 scale-out when tasks increase. Using ECS capacity provider integration is the targeted fix.

What does this SAA-C03 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Use an ECS capacity provider (or Auto Scaling integration) to scale the EC2 instances based on ECS demand. — If ECS tasks are waiting for available container instances, the bottleneck is EC2 capacity rather than application readiness. The most direct fix is to connect ECS demand to EC2 scaling using an ECS capacity provider with Auto Scaling integration. With this approach, when tasks become pending due to lack of resources, the Auto Scaling group can launch additional instances for the cluster, improving placement and reducing response time during traffic spikes. Health check tuning does not add capacity. Why others are wrong: Option A focuses on task health checks; it may reduce restarts, but it doesn’t address the absence of container capacity for scheduling. Option C limits placement and can worsen capacity shortages. Option D is a compute migration decision (ECS to Fargate) and may be unnecessary, costly, and not the minimal change to resolve pending tasks.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.