SAA-C03 Design High-Performing Architectures Practice Question
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?
⚠ Common exam trap
Many candidates think tuning health checks (Option A) or switching to Fargate (Option D) are simpler fixes, but the question specifically asks for the best first architectural step to scale EC2 capacity faster, which is directly addressed by the capacity provider integration.
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
✓
Use an ECS capacity provider (or Auto Scaling integration) to scale the EC2 instances based on ECS demand.
An ECS capacity provider (or Auto Scaling integration) directly links ECS task-level demand to EC2 instance scaling. When tasks are pending due to insufficient container instances, the capacity provider triggers a scale-out event on the Auto Scaling group, adding EC2 instances to accommodate the workload. This is the most direct and efficient architectural step to reduce the wait time for available container instances during peak traffic.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Tune the container health check settings so tasks stop failing and stay running.
Why it's wrong here
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.
- ✓
Use an ECS capacity provider (or Auto Scaling integration) to scale the EC2 instances based on ECS demand.
Why this is correct
When ECS tasks need compute, capacity must scale at the EC2 layer so there are enough container instances to place tasks. Integrating ECS with an Auto Scaling capacity provider allows the cluster to scale out in response to pending tasks. This reduces waiting time and improves responsiveness under load.
- ✗
Pin all tasks to a single Availability Zone to reduce placement overhead.
Why it's wrong here
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.
Why it's wrong here
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.
Go deeper
Related to this question
About these practice questions
This SAA-C03 question is part of Courseiva's 302-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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAA-C03 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 SAA-C03 exam.