SAP-C02 · Question #781
A company is running a large containerized workload in the AWS Cloud. The workload consists of approximately 100 different services. The company uses Amazon Elastic Container Service (Amazon ECS) to…
The correct answer is B. Use Amazon CloudWatch to monitor service quotas that are published under the AWS/Usage. The company needs to monitor its AWS Fargate task usage and be notified when it reaches 80% of the maximum allowed service quota for ECS tasks.
Question
A company is running a large containerized workload in the AWS Cloud. The workload consists of approximately 100 different services. The company uses Amazon Elastic Container Service (Amazon ECS) to orchestrate the workload. Recently the company's development team started using AWS Fargate instead of Amazon EC2 instances in the ECS cluster. In the past, the workload has come close to running the maximum number of EC2 instances that are available in the account. The company is worried that the workload could reach the maximum number of ECS tasks that are allowed. A solutions architect must implement a solution that will notify the development team when Fargate reaches 80% of the maximum number of tasks. What should the solutions architect do to meet this requirement?
Options
- AUse Amazon CloudWatch to monitor the Sample Count statistic for each service in the ECS
- BUse Amazon CloudWatch to monitor service quotas that are published under the AWS/Usage
- CCreate an AWS Lambda function to poll detailed metrics from the ECS cluster. When the number
- DCreate an AWS Config rule to evaluate whether the Fargate SERVICE_QUOTA is greater than
How the community answered
(39 responses)- A3% (1)
- B87% (34)
- C3% (1)
- D8% (3)
Why each option
The company needs to monitor its AWS Fargate task usage and be notified when it reaches 80% of the maximum allowed service quota for ECS tasks.
The `Sample Count` statistic in CloudWatch monitors the number of data points, not the actual number of running tasks or their utilization against a service quota.
Option B is the most appropriate solution because Amazon CloudWatch publishes service quota utilization metrics under the `AWS/Usage` namespace, allowing direct monitoring of the current number of running Fargate tasks against the account's Fargate task quota. An alarm can then be easily configured to trigger when this usage metric crosses the 80% threshold.
Creating a custom AWS Lambda function to poll metrics is an unnecessary and more complex solution when CloudWatch natively provides service quota metrics.
AWS Config is designed for evaluating resource compliance against predefined rules, not for real-time, percentage-based monitoring and alarming on service quota utilization.
Concept tested: AWS Fargate service quota monitoring with CloudWatch
Source: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/UsageMetrics-Fargate.html
Community Discussion
No community discussion yet for this question.