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

Answer A. C cannot be correct because Cost Anomaly detection is for a surprise cost exceeds. A is a perfect use case for this scenario.

"A" describe perfectly the process to create this kind of control. Besides Cost Anomaly is very focused on "Cost", while the question ask to control the "usage" (ex:hours), not exactly $ cost. I suggest doing a demo. "A" for sure

A cannot be correct because AWS Budgets requires manual input of the threshold (e.g., 10% above the 30-day average). If the average changes daily, the budget amount would need constant manual updates, making it impractical.

Option B: Configure AWS Cost Anomaly Detection in the organization's management account. Configure a monitor type of AWS Service. Apply a filter of Amazon EC2. Configure an alert subscription to notify the architecture team if the usage is 10% more than the average usage for the last 30 days. 🛠 Explanation: The company needs a solution that: Tracks EC2 usage over time. Calculates the average usage for the past 30 days. Alerts the architecture team if usage exceeds 10% of the average. ✅ AWS Cost Anomaly Detection is designed for this exact purpose. It: Monitors usage and cost metrics at the AWS service level (e.g., EC2). Uses machine learning to detect anomalies based on historical usage. Sends alerts when usage exceeds a defined threshold (in this case, 10% more than the last 30-day average).

AWS Cost Anomaly Detection is designed to automatically track usage trends and detect anomalies in EC2 usage patterns. You can set up a monitoring rule to compare daily EC2 usage against a 30-day average. If usage exceeds 10% over the historical average, it will trigger an alert. This solution is automated, scalable, and requires minimal operational overhead.

AWS Budgets can be used to set custom budget based on your expected usage and notify you when a threshold is exceeded. AWS Cost Anomaly Detection uses advanced machine learning (ML) technologies to identify anomalous spend and root causes.

For those who think the correct answer is B: https://docs.aws.amazon.com/cost-management/latest/userguide/getting-started-ad.html "For Threshold, enter a number to configure the anomalies that you want to generate alerts for. There are two types of thresholds: absolute and percentage. Absolute thresholds trigger alerts when an anomaly's total COST impact exceeds your chosen threshold. Percentage thresholds trigger alerts when an anomaly's total impact percentage exceeds your chosen threshold. Total impact percentage is the percentage difference between the total expected SPEND and total actual SPEND."" AWS COST Anomaly Detection primarily focuses on COST anomalies rather than specific usage metrics.

Explanation: AWS Cost Anomaly Detection: This service can monitor your AWS usage and costs, identifying anomalies and deviations from normal usage patterns. By setting up a monitor for Amazon EC2 usage, you can detect if the usage is significantly higher than usual, such as exceeding 10% of the average usage over the past 30 days. Monitor Type: Choosing "AWS Service" as the monitor type allows you to focus specifically on EC2 usage. Alert Subscription: You can configure alerts to notify the architecture team when the detected usage anomaly exceeds the threshold, such as a 10% increase over the historical average.

It has to be A. I have tried to do it in AWS Budget Console. Here's a step by step breakdown of what I have done: Step 1: Click on the "Create budget" button and choose the "Usage budget" type Step 2: Set the Usage type groups as `EC2 Running hours`, Set budget amount's baseline timerange as `Last 30 days` with a `daily` period Step 3: Configure alerts with 110% of budgeted amount

A, for sure. Service Monitor tracks spend across all deployed services, but not for a specific service (like ec2)

It should be D as AWS Cost Anomaly Detection is a service that monitors your cost and usage data to detect anomalies based on machine learning models. It can identify unusual spending patterns and notify you when anomalies are detected based on historical usage patterns

Option A - Maybe I am the problem here, I don't why people are selecting option "B", when the the first line in AWS Cost Management documentation Under AWS Budget states - "You can use AWS Budgets to track and take action on your AWS costs and usage. You can use AWS Budgets to monitor your aggregate utilization and coverage metrics for your Reserved Instances (RIs) or Savings Plans." https://docs.aws.amazon.com/cost-management/latest/userguide/budgets-managing-costs.html AWS Blog - https://aws.amazon.com/blogs/mt/manage-cost-overruns-part-1/

It's B. Cost Anomaly detection _can_ do this kind of thing. AWS Budgets is for overall costs and is a less sharp tool here.

Option A - Cost Anomaly detection does not allow to filter based on EC2 type only.

A: Cost dedection is for cost, not for EC2 metrix

This questions is weird. The best soltuion should be AWS CloudWatch. No such answer to choose !

I recommend doing a demo. For sure it is A. It describe perfectly the process.