Examkin

Soru

Zorluk: Çok zorAWS Cost Explorer and Cost Anomaly Detection

A company has an AWS Organization with multiple member accounts. A SysOps administrator is tasked with implementing a cost management strategy to address unexpected cost spikes. The strategy must achieve the following:

1. Identify unexpected spend anomalies specifically for resources tagged with the key ProjectID and notify the project team via Slack.
2. Enable member accounts to access AWS Cost Explorer to view their own historical costs and three-month cost forecasts, while restricting them from viewing any billing data of other member accounts.

Which two actions should the SysOps administrator take to meet these requirements? (Select two.)

  1. Activate the ProjectID tag key as a user-defined cost allocation tag in the Billing console of the management account. In AWS Cost Anomaly Detection, create a Cost Allocation Tag monitor for the ProjectID tag key, and configure an alert subscription to send notifications to the project's Slack channel via AWS Chatbot.Cevap
  2. Enable Linked Account Access to AWS Cost Explorer under the Cost Management Preferences of the management account. This allows member accounts to log in and natively view their own cost forecasts and historical data without access to other accounts' billing information.Cevap
  3. C
    Create a multi-account budget in AWS Budgets in the management account, set the scope to the ProjectID tag, and configure an Amazon SNS topic to publish alerts to the Slack channel when forecasted usage exceeds the threshold.
  4. D
    Apply the ProjectID tag to resources in all member accounts. In AWS Cost Anomaly Detection, create a Cost Category monitor that groups costs by the ProjectID tag, and configure a daily subscription report to be emailed directly to the Slack channel's email integration address.
  5. E
    Configure an Amazon EventBridge rule that monitors AWS Cost Anomaly Detection events and triggers an AWS Systems Manager Automation document to execute a script that exports Cost Explorer forecasts to an S3 bucket in each member account.

Cevap

The correct configurations are to activate the ProjectID cost allocation tag in the Billing console and create a Cost Allocation Tag monitor in AWS Cost Anomaly Detection with an AWS Chatbot Slack subscription, and to enable Linked Account Access to AWS Cost Explorer in the Cost Management Preferences of the management account.
To satisfy the first requirement, the ProjectID tag must be activated as a cost allocation tag in the management account, which then allows the creation of a Cost Allocation Tag monitor in AWS Cost Anomaly Detection to detect unexpected spikes. The alert subscription is configured to target an AWS Chatbot Slack channel for real-time notifications. To satisfy the second requirement, enabling Linked Account Access in the Cost Management Preferences of the management account permits member accounts to natively use Cost Explorer to view their own cost history and forecasts without seeing billing data from other accounts.

Adım Adım Çözüm

1
Activate the tag key in the billing system.
The ProjectID tag key is registered as a user-defined cost allocation tag in the management account, allowing AWS billing services to track and group costs using this dimension.
Before any resource tags can be used in AWS Cost Explorer or Cost Anomaly Detection, they must be activated as cost allocation tags.
2
Set up cost anomaly detection and alerting.
An AWS Cost Anomaly Detection Cost Allocation Tag monitor is created for the ProjectID tag, and an alert subscription is configured to send alerts to the project team's Slack channel via AWS Chatbot.
This detects machine-learning-based anomalies for the specific tag and routes alerts to Slack in real-time.
3
Configure Cost Explorer permissions for member accounts.
Linked Account Access is enabled in the Cost Management Preferences of the management account, allowing member accounts to access Cost Explorer directly.
This native feature allows member accounts to view their own billing history and three-month forecasts while preventing them from viewing the costs of other member accounts.

Anahtar Kavram

AWS Cost Anomaly Detection uses machine learning to identify unexpected cost spikes based on dimensions like Cost Allocation Tags, and alert subscription destinations like AWS Chatbot can route these notifications to Slack. AWS Cost Explorer access can be granted to member accounts via Linked Account Access, restricting their view to only their own account's data.
Bu soruyu puanla

Konular

AWS Cost Explorer and Cost Anomaly Detection

Bu konudan daha fazla soru