Examkin

Question

Difficulty: HardAWS Cost Explorer and Cost Anomaly Detection

A company wants to implement automated cost monitoring for a new multi-tenant application deployed across multiple member accounts in AWS Organizations. The application uses a variety of services, and the SysOps team needs to detect unexpected cost spikes using machine learning. They also need to ensure that anomalies associated with the specific cost allocation tag 'TenantID' are detected and that a centralized record of all anomalies is logged to an Amazon SQS queue in the management account for auditing. Which combination of steps should the SysOps administrator perform to meet these requirements? (Select TWO.)

  1. Create a cost monitor in AWS Cost Anomaly Detection using the Cost Allocation Tag monitor type, specifying the 'TenantID' tag key. Create an anomaly subscription associated with this monitor that targets an Amazon SNS topic.Answer
  2. Create an Amazon EventBridge rule that filters for AWS Cost Anomaly Detection events and configure the rule to send these events to the centralized Amazon SQS queue.Answer
  3. C
    Create an AWS Budget with a daily cost filter for the 'TenantID' tag, configure a 10% daily budget variance limit, and set the target directly to the Amazon SQS queue.
  4. D
    Define the 'TenantID' tag on all resource types using an AWS Organizations tag policy, and rely on AWS Cost Anomaly Detection to automatically evaluate the tag without further configuration in the Billing console.
  5. E
    Configure an AWS Config rule to evaluate resource compliance and trigger an AWS Systems Manager Automation document that polls the Cost Explorer API hourly to write cost spikes to the SQS queue.

Answer

To meet the requirements, the SysOps administrator should create a cost monitor in AWS Cost Anomaly Detection using the Cost Allocation Tag monitor type, specifying the 'TenantID' tag key, and target an Amazon SNS topic. Additionally, they should create an Amazon EventBridge rule that filters for AWS Cost Anomaly Detection events and routes them to the centralized Amazon SQS queue.
The correct steps involve creating a Cost Allocation Tag monitor in AWS Cost Anomaly Detection for the 'TenantID' tag and linking it to an anomaly subscription targeting Amazon SNS. Additionally, Amazon EventBridge natively captures AWS Cost Anomaly Detection events, allowing an EventBridge rule to route them directly to the centralized Amazon SQS queue for audit logging.

Step-by-Step Solution

1
Ensure the 'TenantID' tag is activated as a Cost Allocation Tag in the AWS Billing console.
The tag becomes available for AWS Cost Anomaly Detection and AWS Cost Explorer to track and group costs.
Tags must be activated before they can be evaluated by AWS Cost Anomaly Detection.
2
Create a Cost Allocation Tag monitor in AWS Cost Anomaly Detection targeting the 'TenantID' tag.
AWS Cost Anomaly Detection begins using machine learning to monitor costs matching the 'TenantID' tag and detect unusual spikes.
This establishes the detection mechanism tailored to the multi-tenant application.
3
Create an anomaly subscription for the monitor and point it to an Amazon SNS topic.
Anomaly alerts will be published to the SNS topic immediately upon detection.
An anomaly subscription is required to forward detection events to notification services.
4
Create an Amazon EventBridge rule filtering for Cost Anomaly Detection events, with the Amazon SQS queue in the management account as the target.
All cost anomaly events are automatically captured and sent to the centralized SQS queue.
EventBridge integrates natively with Cost Anomaly Detection, providing a clean, serverless way to log anomalies to SQS for auditing.

Key Concept

Using AWS Cost Anomaly Detection to monitor tag-based spending and routing alerts using Amazon EventBridge.
Estimated Time:3m 0s
Rate this question

Topics

AWS Cost Explorer and Cost Anomaly Detection

More questions from this topic