DOP-C02 Question 170
Select 3Your team is running a microservices-based architecture on Amazon ECS with an Application Load Balancer (ALB). You need to ensure that the services scale efficiently based on application load while minimizing costs. Which metrics should you configure for scaling the ECS services?
- A
Average CPU utilization of ECS tasks
- B
Request count per target on the ALB
- C
Memory utilization of ECS tasks
- D
Average latency of requests handled by the ALB
- E
Number of healthy targets registered with the ALB
Show answer and explanation
Correct answers: A, B, C
Explanation
To efficiently scale ECS services, appropriate metrics like CPU and memory utilization of ECS tasks, as well as request count per target on the ALB, should be used. These metrics directly correlate with application load and resource usage. While metrics like latency and the number of healthy targets provide useful insights for monitoring and diagnostics, they are not suitable for scaling decisions.
- A. Correct.
Correct. Monitoring and scaling based on CPU utilization is a common and effective metric for ECS tasks, as it reflects the processing load of the application.
- B. Correct.
Correct. Request count per target on the ALB is a valid metric, as it directly correlates with the traffic hitting the application and can help you scale services in response to varying demand.
- C. Correct.
Correct. Memory utilization of ECS tasks is another critical metric for scaling, as memory-intensive applications may require more resources even if CPU usage is low.
- D. Incorrect.
Incorrect. While average latency can indicate application performance issues, it's not ideal for scaling ECS services because latency can be affected by factors other than load, such as application code or database responsiveness.
- E. Incorrect.
Incorrect. The number of healthy targets registered with the ALB is used for health checks and ensuring availability but does not correlate directly with scaling demands.