Ultimate access to all questions.
A company utilizes AWS CloudFormation for deploying new infrastructure across its AWS member accounts. These resources are seldom altered and are appropriately scaled for anticipated loads, resulting in a consistent monthly AWS billing. However, developers occasionally create resources for testing purposes and neglect to delete them post-testing, with these resources typically remaining active for a few days. The company seeks to automate the identification of such unused resources and monitor for any increases in AWS billing costs. The solution must pinpoint the specific resources contributing to cost increases and automatically alert the operations team. Which solution meets these requirements?
A
Enable billing alerts. Utilize AWS Cost Explorer to assess the costs from the previous month. Establish an Amazon CloudWatch alarm for total estimated charges, setting a cost threshold above the determined costs from Cost Explorer. Configure the alarm to notify the operations team if the threshold is exceeded.
B
Activate billing alerts. Employ AWS Cost Explorer to calculate the average monthly costs over the last three months. Set up an Amazon CloudWatch alarm for total estimated charges, with a cost threshold higher than the average costs determined by Cost Explorer. Implement the alarm to send a notification to the operations team if the threshold is surpassed.
C
Implement AWS Cost Anomaly Detection to establish a cost monitor with a Linked account monitor type. Set up a subscription to deliver daily AWS cost summaries to the operations team, including a specified threshold for cost variance.
D
Apply AWS Cost Anomaly Detection to create a cost monitor with an AWS services monitor type. Configure a subscription to forward daily AWS cost summaries to the operations team, with a defined threshold for cost variance.