AWS Certified SysOps Administrator – Associate (legacy) — Question 749

A company wants to track Amazon EC2 usage charges that are based on the value of a tag that is named Business-Unit. Company leaders instruct developers to update all EC2 resources with the tag. The developers notify the leaders that they have completed this task.
Later that week, a finance team member checks Cost Explorer. The finance team member sees EC2 costs in the different accounts but cannot find the Business-
Unit tag to filter by or group by.
What is the MOST likely reason that the Business-Unit tag is absent?

Answer options

• A. The Business-Unit tag is not activated as a cost allocation tag in the AWS Billing and Cost Management console.
• B. The Business-Unit tag is not valid because tag key names do not support dashes (-).
• C. The instances have been rebooted, and the developers neglected to re-add the Business-Unit tag after the reboot.
• D. The IAM user does not have permission to view the tags in Cost Explorer.

Correct answer: A

Explanation

To use user-defined tags like Business-Unit for filtering and grouping in Cost Explorer, they must be explicitly activated as cost allocation tags in the AWS Billing and Cost Management console. Once activated, AWS begins tracking the costs associated with those tags, which can take up to 24 hours to appear. Tags persist through instance reboots and support hyphens, meaning the other options are technically incorrect.