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…

Question

Options

• AIt takes at least 30 days to be able to use tags to filter views in Cost Explorer.
• BThe company has not activated the user-defined tags for cost allocation.
• CThe company has not created an AWS Cost and Usage Report.
• DThe company has not created a usage budget in AWS Budgets.

• A
  5% (2)
• B
  89% (39)
• C
  5% (2)
• D
  2% (1)

Explanation

Explanation

To filter views in AWS Cost Explorer using tags, those tags must first be activated as cost allocation tags in the AWS Billing console - simply applying tags to resources is not enough. Without this activation step, AWS does not track or associate the tags with cost and usage data, making them invisible to Cost Explorer filters.

Why the distractors are wrong:

• A is incorrect because there is no 30-day waiting period rule; tags become usable in Cost Explorer relatively quickly (within 24 hours) after they are activated for cost allocation.
• C is incorrect because an AWS Cost and Usage Report is not required to use tag filtering in Cost Explorer; these are separate, independent features.
• D is incorrect because AWS Budgets is a separate service for setting spending alerts and has no bearing on whether tags appear in Cost Explorer.

Memory Tip: Think of it as a two-step process - "Tag it, then Activate it." Applying a tag is like putting a label on a box, but activating it for cost allocation is like registering that label in the billing system so it can actually be searched and reported on. If you skip activation, billing services simply won't "see" the tag.

No community discussion yet for this question.