Topic 1 Question 524
A company migrated to AWS and uses AWS Business Support. The company wants to monitor the cost-effectiveness of Amazon EC2 instances across AWS accounts. The EC2 instances have tags for department, business unit, and environment. Development EC2 instances have high cost but low utilization.
The company needs to detect and stop any underutilized development EC2 instances. Instances are underutilized if they had 10% or less average daily CPU utilization and 5 MB or less network I/O for at least 4 of the past 14 days.
Which solution will meet these requirements with the LEAST operational overhead?
Configure Amazon CloudWatch dashboards to monitor EC2 instance utilization based on tags for department, business unit, and environment. Create an Amazon EventBridge rule that invokes an AWS Lambda function to stop underutilized development EC2 instances.
Configure AWS Systems Manager to track EC2 instance utilization and report underutilized instances to Amazon CloudWatch. Filter the CloudWatch data by tags for department, business unit, and environment. Create an Amazon EventBridge rule that invokes an AWS Lambda function to stop underutilized development EC2 instances.
Create an Amazon EventBridge rule to detect low utilization of EC2 instances reported by AWS Trusted Advisor. Configure the rule to invoke an AWS Lambda function that filters the data by tags for department, business unit, and environment and stops underutilized development EC2 instances.
Create an AWS Lambda function to run daily to retrieve utilization data for all EC2 instances. Save the data to an Amazon DynamoDB table. Create an Amazon QuickSight dashboard that uses the DynamoDB table as a data source to identify and stop underutilized development EC2 instances.
ユーザの投票
コメント(10)
- 正解だと思う選択肢: A
It would be A as correct answer Tagging with EC2 instances for department, business unit, and environment .
CloudWatch to collect and monitor CPU utilization and network I/O metrics.
Create CloudWatch Alarms to detect underutilized instances with composite alarmwith boh CPU utilization and network I/O are low.
AWS Lambda Function to be triggered by the CloudWatch Alarms and check the conditions (10% or less average daily CPU utilization and 5 MB or less network I/O) hold true for at least 4 of the past 14 days. Stop the instances that meet these criteria.
👍 3vip22024/07/05 - 正解だと思う選択肢: C
This is exactly the same criteria provided by the Trusted Advisor: https://docs.aws.amazon.com/awssupport/latest/user/cost-optimization-checks.html#low-utilization-amazon-ec2-instances
👍 3sam2ng2024/08/07 - 正解だと思う選択肢: C
C, for sure. TA for 10% or less average daily CPU utilization and 5 MB or less network I/O for at least 4 of the past 14 days. And least operational overhead
👍 2gfhbox00832024/07/14
シャッフルモード