Examkin

Soru

Zorluk: Çok zorAWS Cost Monitoring, Budgeting, and Optimization Tool Analysis

A financial technology organization uses AWS Organizations to manage a multi-account structure. The organization has recently deployed a new transaction processing platform across several member accounts. The platform writes transaction logs to an Amazon S3 bucket, which are processed and then permanently deleted after 33 days. The platform's compute workloads are highly dynamic and exhibit natural cyclical scaling. The organization has the following requirements:

* Detect sudden, atypical spending spikes across all member accounts within 2424 hours without triggering false positives during regular cyclical scaling events.
* Provide a pro forma billing view to a subsidiary account that reflects a custom 15%15\% discount on all Amazon EC2 usage, without altering the actual consolidated invoice generated at the management account level.
* Send an immediate notification to the operations team if the actual monthly consolidated cost exceeds 110%110\% of the budgeted amount.
* Implement a cost-optimized storage strategy for the transaction logs.

Which combination of actions will meet these requirements in the most cost-effective and operationally efficient manner?

  1. A
    Configure AWS Cost Anomaly Detection with a cost monitor for all services. Create a billing group in AWS Billing Conductor for the subsidiary account, associate a custom pricing plan that applies a 15%15\% discount flat rate to EC2, and share the pro forma billing data. Create a cost budget in AWS Budgets at the management account level with an alert threshold set at 110%110\% of the budgeted amount based on actual costs. Create an S3 Lifecycle policy to transition the transaction logs to Amazon S3 Standard-Infrequent Access (S3 Standard-IA) immediately upon creation.
  2. B
    Configure AWS Cost Anomaly Detection with a cost monitor for all services. Purchase a Compute Savings Plan in the subsidiary member account to apply the custom 15%15\% discount on their EC2 instances and Amazon RDS databases, and configure AWS Billing Conductor to pass through these discounts. Create a cost budget in AWS Budgets at the management account level with an alert threshold set at 110%110\% of the budgeted amount based on actual costs. Create an S3 Lifecycle policy to delete the transaction logs directly from S3 Standard after 33 days.
  3. Configure AWS Cost Anomaly Detection with a cost monitor for all services. Create a billing group in AWS Billing Conductor for the subsidiary account, associate a custom pricing plan that applies a 15%15\% discount flat rate to EC2, and share the pro forma billing data. Create a cost budget in AWS Budgets at the management account level with an alert threshold set at 110%110\% of the budgeted amount based on actual costs. Create an S3 Lifecycle policy to delete the transaction logs directly from S3 Standard after 33 days.Cevap
  4. D
    Configure AWS Cost Explorer with daily scheduled reports to notify the operations team when consolidated actual costs exceed 110%110\% of the budget. Create a billing group in AWS Billing Conductor for the subsidiary account, associate a custom pricing plan that applies a 15%15\% discount flat rate to EC2, and share the pro forma billing data. Create a cost budget in AWS Budgets with a threshold set at 110%110\% using forecasted costs. Create an S3 Lifecycle policy to delete the transaction logs directly from S3 Standard after 33 days.

Cevap

Configure AWS Cost Anomaly Detection to monitor services using machine learning. Use AWS Billing Conductor to set up a billing group and custom pricing plan with a 15%15\% EC2 discount for the subsidiary account. Use AWS Budgets to alert on actual monthly costs exceeding 110%110\% of budgeted amounts. Maintain transaction logs in S3 Standard and delete them after 33 days using S3 Lifecycle policies.
The correct solution correctly separates the concerns of cost alerting, custom pro forma billing, and storage optimization. First, AWS Cost Anomaly Detection is configured because its machine learning model baselines cost patterns and dynamically adapts to cyclical compute scaling, minimizing false positives. Second, AWS Billing Conductor is ideal for generating custom billing data (e.g., a 15%15\% discount for the subsidiary) without modifying the consolidated payer account invoice. Third, AWS Budgets handles proactive threshold alerts based on actual monthly costs. Finally, S3 Standard is selected for logs with a 33-day lifespan because S3 Standard-IA imposes a 3030-day minimum storage duration billing penalty.

Adım Adım Çözüm

1
Evaluate S3 lifecycle and storage tiers for short-lived transaction logs.
Determine that S3 Standard is the most cost-effective tier and write an S3 Lifecycle policy to delete logs after 33 days.
Transitioning logs to S3 Standard-IA would trigger a 3030-day minimum storage billing charge penalty since the logs are deleted in only 33 days.
2
Select the appropriate service to monitor and alert on cost anomalies.
Configure AWS Cost Anomaly Detection with a cost monitor for all services.
Machine learning-based detection adapts to cyclical scaling to prevent false positives, while detecting spikes within 2424 hours.
3
Configure custom billing views for the subsidiary account.
Define a billing group and custom pricing plan in AWS Billing Conductor to apply a 15%15\% discount to EC2.
This allows the subsidiary to view pro forma costs with custom pricing without affecting the management account's consolidated invoicing.
4
Establish alerting for budget overruns.
Create a cost budget in AWS Budgets at the management account level.
AWS Budgets is required to monitor actual spend relative to a budget threshold (110%110\%) and send proactive alerts.

Anahtar Kavram

Selecting and configuring the correct AWS cost management tools based on proactive vs. reactive characteristics, ML anomaly detection limits, and pro forma billing requirements.
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

AWS Cost Monitoring, Budgeting, and Optimization Tool Analysis