Examkin

Soru

Zorluk: Çok zorAWS Cost Explorer and Cost Anomaly Detection

A SysOps administrator needs to implement a cost-monitoring solution for an AWS account where developers frequently deploy untagged experimental workloads. The solution must use machine learning to automatically detect unexpected spend spikes on resources that lack the Environment tag and send immediate alerts to an existing Amazon SNS topic. Furthermore, the administrator must be able to perform root-cause analysis in AWS Cost Explorer to identify the specific EC2 instance IDs responsible for any detected anomalies.

Which combination of steps should the administrator perform to meet these requirements?

  1. Activate the Environment tag as a cost allocation tag in the Billing console. Enable hourly and resource-level granularity in AWS Cost Explorer. In AWS Cost Anomaly Detection, create a Cost Allocation Tag monitor for the Environment tag, create an alert subscription linked to the SNS topic, and ensure the SNS topic's access policy permits the anomaly-detection.amazonaws.com service principal to publish to it.Cevap
  2. B
    Enable hourly and resource-level granularity in AWS Cost Explorer. In AWS Cost Anomaly Detection, create a Cost Allocation Tag monitor for the Environment tag, create an alert subscription linked to the SNS topic, and ensure the SNS topic's access policy permits the anomaly-detection.amazonaws.com service principal to publish to it.
  3. C
    Activate the Environment tag as a cost allocation tag in the Billing console. Enable hourly and resource-level granularity in AWS Cost Explorer. Create a Cost Category that filters for resources where the Environment tag is empty. Configure an AWS Budget with a daily recurring cost filter matching the untagged Cost Category, and configure an email and SNS alert with a static cost threshold above the forecasted budget.
  4. D
    Activate the Environment tag as a cost allocation tag in the Billing console. Enable hourly and resource-level granularity in AWS Cost Explorer. In AWS Cost Anomaly Detection, create a Cost Allocation Tag monitor for the Environment tag, create an Amazon EventBridge rule that triggers when Cost Anomaly Detection publishes to CloudWatch Metrics, and configure the target as the SNS topic.

Cevap

Activate the Environment tag as a cost allocation tag in the Billing console, enable hourly and resource-level granularity in AWS Cost Explorer, create a Cost Allocation Tag monitor for the Environment tag in AWS Cost Anomaly Detection, link it to an SNS subscription, and allow the anomaly-detection.amazonaws.com service principal to publish to the SNS topic.
The correct option outlines the comprehensive set of actions required to monitor untagged resources and analyze them. Activating the Environment tag as a cost allocation tag ensures AWS tracks cost data associated with this key. Enabling hourly and resource-level granularity in AWS Cost Explorer is necessary to identify individual EC2 instance IDs. Creating a Cost Allocation Tag monitor in AWS Cost Anomaly Detection allows the machine learning model to evaluate cost anomalies associated with tag values (including resources with no tag value). Modifying the SNS topic access policy to allow the anomaly-detection.amazonaws.com service principal to publish ensures alerts are successfully delivered.

Adım Adım Çözüm

1
Activate the tag key in the Billing console.
The Environment tag is registered as a Cost Allocation Tag, allowing AWS to start tracking and aggregating cost data by this tag value.
Cost Anomaly Detection and Cost Explorer cannot filter or monitor based on tags unless they are explicitly activated as cost allocation tags.
2
Enable hourly and resource-level granularity in Cost Explorer.
AWS Cost Explorer is configured to store detailed resource-level and hourly data.
By default, Cost Explorer aggregates cost data daily at the service/member account level. Viewing individual EC2 instance IDs requires enabling resource-level granularity.
3
Create a Cost Allocation Tag monitor and associate it with an alert subscription targeting the SNS topic.
AWS Cost Anomaly Detection will evaluate costs grouped by the Environment tag (including untagged resources marked as 'No Tag Value') and send notifications to the SNS topic.
This establishes the machine-learning-driven monitoring for anomalous spend on the target tag key.
4
Update the SNS topic access policy to grant publish permissions to the Cost Anomaly Detection service principal.
The anomaly-detection.amazonaws.com service principal is authorized to call the Publish API on the SNS topic.
Without this policy modification, the SNS topic will reject the publish requests from AWS Cost Anomaly Detection, preventing alerts from being delivered.

Anahtar Kavram

AWS Cost Anomaly Detection utilizes machine learning to identify unexpected cost spikes, but depends on Cost Allocation Tags to monitor tagged/untagged resources, and requires SNS policy permissions to deliver alerts, while Cost Explorer requires explicit enablement of resource-level granularity for instance-level root-cause analysis.
Bu soruyu puanla

Konular

AWS Cost Explorer and Cost Anomaly Detection

Bu konudan daha fazla soru