CLF-C02 Billing, Pricing, and Support Practice Question

A company is using several AWS services and has noticed their bill has been increasing. They want to identify which team or project is responsible for each cost. Which AWS feature enables tracking costs by team, project, or environment?

⚠ Common exam trap

Candidates often confuse AWS Config tags (used for compliance and resource tracking) with Cost Allocation Tags, or assume that consolidated billing alone provides per-team cost visibility without the need for tagging.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

AWS Cost Allocation Tags

AWS Cost Allocation Tags allow you to tag AWS resources with metadata (e.g., team, project, environment) and then activate those tags in the Billing and Cost Management console. Once activated, AWS generates cost reports that break down charges by those tag values, enabling you to attribute costs to specific teams or projects. This is the native AWS feature designed specifically for cost allocation and tracking.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
AWS Organizations consolidated billing
Why it's wrong here
AWS Organizations consolidated billing is a feature that aggregates the usage and costs of all member accounts into a single bill, enabling you to take advantage of volume discounts and to see a combined view of spending. It groups costs by account, not by arbitrary business tags like team or project, and it cannot split a single account's costs by those dimensions. Consolidation is about combining spend across accounts, whereas the requirement is to attribute charges within an account to specific business units, which is a different function.
✓
AWS Cost Allocation Tags
Why this is correct
AWS Cost Allocation Tags let you attach user-defined metadata (e.g., team, project, environment) to resources, and once activated, AWS incorporates these tags into your billing reports and Cost Explorer. This enables accurate cost breakdown and chargeback by any business dimension, such as team or project, which directly addresses the requirement. Because the tags themselves are the mechanism that carries attribution data into your billing data, this is the service that fulfills the need to identify which team or project incurred costs.
✗
AWS Budgets
Why it's wrong here
AWS Budgets is a service that monitors your actual and forecasted AWS spending against custom thresholds and sends alerts when you exceed or are forecasted to exceed them. Budgets can be filtered by tags, including cost allocation tags, but it does not create or manage the tags themselves, nor does it produce a billing report grouped by those tags. It is a reactive monitoring tool that depends on tags already existing and being used elsewhere, so it cannot establish the required cost attribution mechanism.
✗
AWS Config tags
Why it's wrong here
AWS Config is a service that records resource configurations and evaluates them against compliance rules; it can check whether resources have specific tags, but it is not a billing tool. Tag compliance checks in Config help you maintain tagging standards, but they do not roll up spending by team or project in your billing reports. Since the question is about how to get a cost breakdown by business dimension, Config's governance-focused tag tracking does not provide the financial attribution that Cost Allocation Tags provide.

Go deeper

CLF-C02 Billing, Pricing, and Support Practice Question

Why each option matters

Option-by-option breakdown

Related to this question