SAP-C02 · Question #549
A large company recently experienced an unexpected increase in Amazon RDS and Amazon DynamoDB costs. The company needs to increase visibility into details of AWS Billing and Cost Management. There…
The correct answer is C. Use Tag Editor to tag existing resources. Create cost allocation tags to define the cost center and. To gain visibility into RDS and DynamoDB costs and enforce consistent tagging for chargeback, existing resources need to be tagged with Tag Editor, and cost allocation tags must be activated for future resources while enforcing tagging for CloudFormation deployments.
Question
A large company recently experienced an unexpected increase in Amazon RDS and Amazon DynamoDB costs. The company needs to increase visibility into details of AWS Billing and Cost Management. There are various accounts associated with AWS Organizations, including many development and production accounts. There is no consistent tagging strategy across the organization, but there are guidelines in place that require all infrastructure to be deployed using AWS CloudFormation with consistent tagging. Management requires cost center numbers and project ID numbers for all existing and future DynamoDB tables and RDS instances. Which strategy should the solutions architect provide to meet these requirements?
Options
- AUse Tag Editor to tag existing resources. Create cost allocation tags to define the cost center and
- BUse an AWS Config rule to alert the finance team of untagged resources. Create a centralized
- CUse Tag Editor to tag existing resources. Create cost allocation tags to define the cost center and
- DCreate cost allocation tags to define the cost center and project ID and allow 24 hours for tags to
How the community answered
(23 responses)- A13% (3)
- B4% (1)
- C78% (18)
- D4% (1)
Why each option
To gain visibility into RDS and DynamoDB costs and enforce consistent tagging for chargeback, existing resources need to be tagged with Tag Editor, and cost allocation tags must be activated for future resources while enforcing tagging for CloudFormation deployments.
This option is missing the crucial step of activating cost allocation tags, which is necessary for tags to appear in billing reports and enable chargeback.
An AWS Config rule is reactive (alerts about untagged resources) and does not proactively tag existing resources or directly enforce the consistent application of specific tags with defined values.
The solution correctly addresses both existing and future resources. Using Tag Editor allows for efficiently tagging existing RDS and DynamoDB instances across multiple accounts to apply the required cost center and project ID tags for immediate cost visibility. Activating these tags as cost allocation tags ensures they appear in the AWS Cost and Usage Report for chargeback. Furthermore, enforcing tagging for new resources deployed via CloudFormation (which has existing guidelines for consistent tagging) ensures compliance for all future deployments, providing comprehensive cost management.
This option only focuses on future tags and activating cost allocation tags, ignoring the immediate need to tag existing RDS and DynamoDB resources that contributed to the cost increase.
Concept tested: Cost management, resource tagging, and chargeback
Source: https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html
Community Discussion
No community discussion yet for this question.