DOP-C02 Question 182
Select 2You are managing a containerized application running on Amazon ECS with the Fargate launch type. The application needs to scale based on CPU utilization. Additionally, you need to ensure that any new container deployments do not disrupt the running application. Which of the following configurations should you implement to meet these requirements?
- A
Configure an Application Auto Scaling policy to scale the ECS service based on the average CPU utilization metric.
- B
Set the ECS service deployment type to 'Blue/Green' using AWS CodeDeploy.
- C
Configure a Target Tracking Scaling policy to scale the ECS service based on memory utilization instead of CPU utilization.
- D
Set the ECS service deployment type to 'Rolling Update' and use a minimum healthy percentage of 100.
- E
Enable Service Auto Scaling and configure it to scale based on the average CPU utilization of the ECS service.
Show answer and explanation
Correct answers: A, B
Explanation
To meet the requirements, you need to configure scaling based on CPU utilization and ensure zero-downtime deployments. Application Auto Scaling policies allow you to scale ECS services dynamically based on metrics like CPU utilization. Blue/Green deployments, configured through AWS CodeDeploy, ensure that new deployments do not disrupt existing traffic by routing traffic to new versions only after they pass health checks. Other options either do not fully meet the requirements or are less appropriate given the scenario.
- A. Correct.
Correct: Configuring an Application Auto Scaling policy to scale the ECS service based on average CPU utilization ensures the service can scale dynamically based on workload demands.
- B. Correct.
Correct: Using the 'Blue/Green' deployment type ensures zero-downtime deployments by routing traffic to new task sets only after they pass health checks.
- C. Incorrect.
Incorrect: While memory utilization can be a useful metric, the scenario specifically requires scaling based on CPU utilization, so this option does not meet the requirements.
- D. Incorrect.
Incorrect: Using a 'Rolling Update' deployment with a minimum healthy percentage of 100 prevents any disruption during updates but does not ensure zero downtime like Blue/Green deployments. It also does not address the scaling requirement.
- E. Incorrect.
Incorrect: While enabling Service Auto Scaling is generally correct, this option is less specific than configuring an Application Auto Scaling policy, which directly addresses the requirement to scale based on CPU utilization.