Examkin

Question

Difficulty: MediumAWS Cost Explorer and Cost Anomaly Detection

A company has recently added a new business unit to their AWS Organization as a member account. A SysOps Administrator is tasked with configuring cost monitoring for this specific account. The administrator needs to identify unexpected cost spikes that deviate from historical trends using machine learning and send immediate email alerts to the operations team. Additionally, the administrator must view a projection of the member account's total costs for the next three months. Which two actions should the SysOps Administrator take to meet these requirements? (Select two.)

  1. Create a Linked Account monitor in AWS Cost Anomaly Detection for the member account, and associate it with an alert subscription targeting the operations email address.Answer
  2. Open AWS Cost Explorer, apply a filter for the new member account, and run a forecast with a three-month prediction interval.Answer
  3. C
    Configure a monthly cost budget in AWS Budgets for the member account, and define an alert threshold based on forecasted costs to notify the operations email.
  4. D
    Apply a custom 'BusinessUnit' tag to the resources in the member account, create a Cost Allocation Tag monitor in AWS Cost Anomaly Detection, and configure email alerting.
  5. E
    Configure an Amazon EventBridge rule that detects AWS Config evaluation changes for cost compliance, and trigger an AWS Systems Manager Automation runbook to send emails.

Answer

Create a Linked Account monitor in AWS Cost Anomaly Detection for the member account, associate it with an alert subscription targeting the operations email address, and run a forecast in AWS Cost Explorer filtered by the new member account.
To detect machine learning-driven anomalies for a specific member account, a Linked Account monitor must be configured in AWS Cost Anomaly Detection along with an alert subscription. To project future costs for the next three months, AWS Cost Explorer's forecasting feature must be used with a filter applied to the specific member account. These two actions address both monitoring and forecasting requirements accurately.

Step-by-Step Solution

1
Navigate to the AWS Cost Anomaly Detection console and create a new monitor.
A Linked Account monitor is configured specifically for the target member account.
This establishes machine learning-driven anomaly detection on the account level to identify unexpected spend spikes.
2
Configure an alert subscription for the newly created Cost Anomaly monitor.
An alert subscription is linked to the monitor with the operations email address as the recipient.
This ensures the operations team receives immediate notifications when an anomaly exceeding the threshold is detected.
3
Navigate to AWS Cost Explorer, filter by the new member account, and select the Forecast option.
A projection graph showing the estimated total costs for the next three months is rendered.
This fulfills the requirement to view a three-month cost projection for the member account.

Key Concept

Using AWS Cost Anomaly Detection for machine learning-driven spend alerting alongside AWS Cost Explorer for future spend forecasting.
Rate this question

Topics

AWS Cost Explorer and Cost Anomaly Detection

More questions from this topic