Ultimate access to all questions.
A large company has faced an unexpected surge in costs for Amazon RDS and Amazon DynamoDB services. To enhance cost management and billing transparency across multiple AWS accounts within AWS Organizations, including both development and production environments, the company seeks a strategic approach. Despite the absence of a unified tagging policy, the company mandates the use of AWS CloudFormation for infrastructure deployment with consistent tagging practices. The management team insists on the inclusion of cost center numbers and project ID numbers for all current and future DynamoDB tables and RDS instances. What strategy should the solutions architect propose to fulfill these management requirements effectively?
A
Utilize Tag Editor to apply tags to existing resources. Establish cost allocation tags to specify the cost center and project ID, allowing 24 hours for these tags to be reflected in the billing data.
B
Implement an AWS Config rule to notify the finance department of resources without tags. Develop a centralized AWS Lambda solution that uses a cross-account role to periodically tag untagged RDS databases and DynamoDB resources every hour.
C
Employ Tag Editor to tag existing resources. Set up cost allocation tags to identify the cost center and project ID. Enforce Service Control Policies (SCPs) to prevent the creation of resources that lack the required cost center and project ID tags.
D
Define cost allocation tags for the cost center and project ID, allowing 24 hours for these tags to update in the billing data. Modify existing federated roles to limit the ability to provision resources that do not adhere to the tagging requirements for cost center and project ID.