AWS DevOps Engineer Professional DOP-C01 – Question546

A company has multiple environments that run applications on Amazon EC2 instances. The company wants to track costs and has defined a new rule that states that all production EC2 instances must be tagged with a CostCenter tag.
A DevOps engineer has created a tag policy to validate the use of the CostCenter tag, has activated the option to prevent noncompliant tagging operations for this tag, and has attached the policy to the production OU in AWS Organizations. The DevOps engineer generates a compliance report for the entire organization and ensures that all the deployed instances have the correct tags configured. The DevOps engineer also verifies that the CostCenter tag cannot be removed from an EC2 instance that runs in one of the production accounts.
After some time, the DevOps engineer notices that several EC2 instances have been launched in the production accounts without the configuration of the CostCenter tag.
What should the DevOps engineer do to ensure that all production EC2 instances are launched with the CostCenter tag configured?

A.
Attach the tag policy to the organization root to ensure that the policy applies to all EC2 instances.
B. Create an SCP that requires the CostCenter tag during the launch of EC2 instances.
C. In the AWS Billing and Cost Management console of the management account, activate the CostCenter tag as a cost allocation tag.
D. Activate the AWS Config required-tags managed rule in all production accounts. Ensure that the rule evaluates the CostCenter tag.

Correct Answer: C

Explanation:

Explanation:
After you activate cost allocation tags, AWS uses the cost allocation tags to organize your resource costs on your cost allocation report, to make it easier for you to categorize and track your AWS costs.
Reference: https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-a…