Question
A company applies user-defined tags to resources that are associated with the company's AWS workloads. Twenty days after applying the tags, the company notices that it cannot use the tags to filter views in the AWS Cost Explorer console.
What is the reason for this issue?
- A. It takes at least 30 days to be able to use tags to filter views in Cost Explorer.
- B. The company has not activated the user-defined tags for cost allocation. Correct
- C. The company has not created an AWS Cost and Usage Report.
- D. The company has not created a usage budget in AWS Budgets.
Explanation
According to AWS documentation, user-defined tags must be activated for cost allocation before they can be used to filter views in the AWS Cost Explorer console. This activation is necessary for Cost Explorer to recognize and utilize these tags for filtering purposes.
