Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 524 discussion

CloudWatch dashboards are for visual monitoring, not detection.

Due to the link posted by Kinnam and sam2ng, together with this https://docs.aws.amazon.com/awssupport/latest/user/cloudwatch-events-ta.html

Option C, This solution meets the requirements with the least operational overhead because it uses Amazon EventBridge (formerly CloudWatch Events) to trigger a response based on low utilization reports from AWS Trusted Advisor. AWS Trusted Advisor provides pre-configured dashboards that can be used to monitor various aspects of your AWS resources, including EC2 instance utilization. By leveraging these pre-configured dashboards, you don't need to set up additional monitoring infrastructure or write custom code. The EventBridge rule will automatically invoke the Lambda function when a low utilization report is received from Trusted Advisor, which eliminates the need for daily polling or manual intervention. The other options are more resource-intensive and require additional setup and maintenance:

AWS Trusted Advisor provides insights into underutilized EC2 instances automatically, including recommendations for cost-saving based on utilization metrics like CPU and network usage. Since the company is using AWS Business Support, they already have access to Trusted Advisor, making this a low-overhead solution. Amazon EventBridge can be used to create a rule that detects when Trusted Advisor reports low-utilization instances. This avoids the need for custom-built CloudWatch dashboards or manual tracking. AWS Lambda can be triggered to handle the logic of stopping instances that meet the specific criteria of low CPU utilization and network I/O, filtering by tags for department, business unit, and environment. Lambda is serverless and scales automatically, so it minimizes operational overhead.

https://docs.aws.amazon.com/awssupport/latest/user/cost-optimization-checks.html#low-utilization-amazon-ec2-instances

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

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

A - involves continuous monitoring and potential updates to dashboards and metrics. C - minimizes ongoing maintenance by relying on Trusted Advisor's automated reports.

A is not correct as it's missing setting up alarms for the "detect" part. I go with C.

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.

Not c because AWS Trusted Advisor does not provide real-time utilization metrics suitable for detecting underutilized instances over a specific timeframe. It focuses more on best practices and recommendations rather than real-time operational metrics. Should be B