Q30 — AWS SAP-C02 Ch.3

Question 30 of 75 | ← Chapter 3

Q255. 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?

• A. Use Tag Editor to tag existing resources. Create cost allocation tags to define the cost center and project ID and allow 24 hours for tags to propagate to existing resources.
• B. Use an AWS Config rule to alert the finance team of untagged resources. Create a centralized AWS Lambda based solution to tag untagged RDS databases and DynamoDB resources every hour using a cross-account role.
• C. Use Tag Editor to tag existing resources. Create cost allocation tags to define the cost center and project ID. Use SCPs to restrict resource creation that do not have the cost center and project ID on the resource. ✓
• D. Create cost allocation tags to define the cost center and project ID and allow 24 hours for tags to propagate to existing resources. Update existing federated roles to restrict privileges to provision resources that do not include the cost center and project ID on the resource.

Correct Answer: C. Use Tag Editor to tag existing resources. Create cost allocation tags to define the cost center and project ID. Use SCPs to restrict resource creation that do not have the cost center and project ID on the resource.

Explanation

To increase visibility into details of AWS Billing and Cost Management in an organization, it is essential to have a consistent tagging strategy that includes cost center numbers and project ID numbers for all infrastructure resources. In this scenario, there are various accounts associated with AWS Organizations, including many development and production accounts, without consistent tagging strategies. The solution architect must provide a strategy to meet these requirements. Option C is the best approach because it uses Tag Editor to tag existing resources, creates cost allocation tags to define the cost center and project ID, and uses Service Control Policies (SCPs) to restrict resource creation that does not have the cost center and project ID on the resource. This approach ensures that all resources are tagged consistently, and it provides better visibility into resource usage and costs. Option A suggests using Tag Editor to tag existing resources and create cost allocation tags to define the cost center and project ID. However, it may take up to 24 hours for tags to propagate to all existing resources, and this might not meet the requirement of immediate visibility. Option B suggests using an AWS Config rule to alert the finance team of untagged resources and creating a centralized AWS Lambda- based solution to tag untagged RDS databases and DynamoDB resources every hour using a cross- account role. While it could work, it may impact the application's normal workflow during the implementation time. Option D suggests creating cost allocation tags to define the cost center and project ID and updating existing federated roles to restrict privileges to provision resources that do not include the cost center and project ID on the resource. It may also affect the application's normal workflow during the implementation time.