SAA-C03 Question 151
Select 2A company is running a containerized application using Amazon Elastic Container Service (Amazon ECS) with the Fargate launch type. The application requires seamless scaling based on CPU utilization and must ensure high availability across multiple Availability Zones (AZs). What should the Solutions Architect do to meet these requirements?
- A
Configure an Application Load Balancer (ALB) to distribute traffic across ECS tasks deployed in multiple AZs.
- B
Use Service Auto Scaling to adjust the desired count of tasks based on CPU utilization.
- C
Deploy the ECS service in a single Availability Zone to reduce complexity and cost.
- D
Switch from Fargate to the EC2 launch type to gain more control over scaling policies.
- E
Enable ECS task placement constraints to restrict tasks to a single AZ.
Show answer and explanation
Correct answers: A, B
Explanation
To meet the requirements of seamless scaling and high availability across multiple Availability Zones, the ECS service must use Service Auto Scaling to dynamically adjust the number of tasks based on CPU utilization. Additionally, an Application Load Balancer should be used to distribute traffic across tasks running in multiple AZs. Using Fargate simplifies the setup and eliminates the need to manage EC2 instances, while task placement constraints or restricting to a single AZ would violate the high availability requirement.
- A. Correct.
Correct: An Application Load Balancer (ALB) ensures traffic is distributed across ECS tasks running in multiple AZs, which is essential for high availability.
- B. Correct.
Correct: Service Auto Scaling can adjust the number of running tasks based on CPU utilization, enabling seamless scaling based on workload.
- C. Incorrect.
Incorrect: Deploying in a single AZ compromises high availability. Running across multiple AZs is necessary to meet the high availability requirement.
- D. Incorrect.
Incorrect: While the EC2 launch type provides more control over scaling, Fargate is fully managed and supports auto-scaling, making it a better choice for the given scenario.
- E. Incorrect.
Incorrect: Restricting tasks to a single AZ goes against the requirement for high availability across multiple AZs.