SAP-C02 Question #710: Real Exam Question with Answer & Explanation

Question

A company used AWS CloudFormation to create all new infrastructure in its AWS member accounts. The resources rarely change and are properly sized for the expected load. The monthly AWS bill is consistent. Occasionally, a developer creates a new resource for testing and forgets to remove the resource when the test is complete. Most of these tests last a few days before the resources are no longer needed. The company wants to automate the process of finding unused resources. A solutions architect needs to design a solution that determines whether the cost in the AWS bill is increasing. The solution must help identify resources that cause an increase in cost and must automatically notify the company's operations team. Which solution will meet these requirements?

Options

• ATurn on billing alerts. Use AWS Cost Explorer to determine the costs for the past month. Create
• BTurn on billing alerts. Use AWS Cost Explorer to determine the average monthly costs for the
• CUse AWS Cost Anomaly Detection to create a cost monitor that has a monitor type of Linked
• DUse AWS Cost Anomaly Detection to create a cost monitor that has a monitor type of AWS

Explanation

Automate detection of increasing costs due to forgotten test resources, identify the cause, and notify operations.

Common mistakes.

• A. Turning on billing alerts with CloudWatch alarms monitors aggregate billing but does not automatically identify the specific resources causing the cost increase or provide the anomaly detection intelligence needed; Cost Explorer is for analysis, not automated detection and notification of anomalies.
• B. Similar to option A, using billing alerts and Cost Explorer requires manual investigation to identify the specific forgotten resources; it lacks the automated anomaly detection and root cause analysis capabilities of Cost Anomaly Detection.
• D. While AWS Cost Anomaly Detection is the correct service, a monitor type of 'AWS services' would monitor all services, making it less specific for identifying cost increases from linked accounts and potentially less precise for the specific use case of forgotten test resources within member accounts; 'Linked accounts' monitor type directly focuses on the cost sources from individual member accounts.

Concept tested. AWS Cost Anomaly Detection for cost governance and resource identification

Reference. https://aws.amazon.com/aws-cost-management/aws-cost-anomaly-detection/

No community discussion yet for this question.