How to Enforce Cost Allocation Tags Across AWS Accounts
A company has a complex AWS environment with hundreds of accounts. They want to implement a tagging strategy that allows them to track costs by department and project. The tags must be propagated from resources to cost reports automatically. Which approach meets these requirements with minimal ongoing maintenance?
Quick Answer
The answer is to use AWS Organizations tag policies to enforce required tags on accounts, then activate cost allocation tags in the management account. This approach is correct because tag policies centrally define and enforce tagging rules across hundreds of accounts, ensuring consistent tag application at the resource level, while activating cost allocation tags in the management account automatically propagates those tags into AWS Cost Explorer and cost reports without any manual intervention or ongoing maintenance. On the AWS Certified Solutions Architect Professional SAP-C02 exam, this scenario tests your understanding of governance at scale versus per-account manual tagging—a common trap is choosing AWS Config rules or Lambda-based remediation, which require ongoing maintenance and do not natively propagate tags to cost reports. The key distinction is that tag policies enforce compliance before resource creation, while cost allocation tag activation handles the reporting pipeline. Memory tip: think “Policy for enforcement, Activation for reporting”—two steps, zero ongoing effort.
⚠ Common exam trap
Many exam-takers confuse reactive remediation (like Config rules with Lambda) with proactive enforcement (like tag policies), and overlook that cost allocation tags must be explicitly activated in the management account to appear in cost reports.
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
✓
Use AWS Organizations tag policies to enforce required tags on resources, and activate cost allocation tags in the management account.
AWS Organizations tag policies allow you to define and enforce required tags across all accounts in the organization, ensuring consistent tagging. When you activate cost allocation tags in the management account, these tags are automatically propagated to AWS Cost Explorer and cost reports without any manual intervention or ongoing maintenance, meeting the requirement for minimal ongoing effort.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create a CloudFormation template that applies tags to all resources and deploy it via StackSets.
Why it's wrong here
This requires updating the template for new resources and does not enforce tagging on existing resources.
- ✓
Use AWS Organizations tag policies to enforce required tags on resources, and activate cost allocation tags in the management account.
Why this is correct
Tag policies enforce tags across accounts, and cost allocation tags are automatically activated.
- ✗
Use AWS Config rules to detect untagged resources and trigger a Lambda function to add tags.
Why it's wrong here
This is reactive and adds operational overhead.
- ✗
Use AWS Cost Explorer to filter by resource tags after they are manually applied.
Why it's wrong here
Manual tagging is not scalable.
Go deeper
Related to this question
About these practice questions
This SAP-C02 question is part of Courseiva's 1,660-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
3 more ways this is tested on SAP-C02
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company has multiple AWS accounts and wants to ensure that all resources are tagged with a cost center tag. Which THREE steps should they take to enforce this?
hard- ✓ A.Use AWS Organizations to define a tag policy that mandates the cost center tag.
- B.Use AWS Config rules to detect untagged resources and trigger a Lambda function to add the tag.
- ✓ C.Use AWS CloudFormation templates that enforce tagging and use StackSets to deploy across accounts.
- ✓ D.Create a service control policy (SCP) that denies resource creation if the required tag is not present, for supported services.
- E.Enable AWS Cost Explorer to report on untagged resources.
Why A: AWS Organizations tag policies allow you to define rules for tagging resources across accounts in your organization. By specifying the cost center tag as mandatory in a tag policy, you can enforce that all resources must have this tag, and any non-compliant resources can be reported or prevented from being created, depending on the policy's enforcement mode.
Variation 2. A global company uses AWS Organizations with many OUs and accounts. The finance team needs to track costs by cost center, which is tagged on each resource. However, some resources are not tagged. Which solution will provide the MOST accurate cost allocation?
hard- A.Enable cost allocation tags and use AWS Cost Explorer to filter by tag.
- B.Create AWS Budgets reports for each cost center using tag filters.
- C.Export AWS Cost and Usage Reports to Amazon QuickSight and use tag-based filtering.
- ✓ D.Use AWS Cost Categories to group costs by tag value and set a default rule for untagged resources.
Why D: AWS Cost Categories allow you to group costs by tag values and, crucially, set a default rule for untagged resources. This ensures that all resources—tagged or not—are assigned to a cost center, providing the most accurate cost allocation across the entire organization. Other options only filter or report on tagged resources, leaving untagged costs unallocated.
Variation 3. A company uses AWS Organizations with multiple accounts. The finance team needs to track costs by department, where each department uses resources across several accounts. What is the BEST way to allocate costs accurately?
medium- A.Use AWS Cost Explorer to view costs by linked account.
- ✓ B.Define cost allocation tags for each department and enable them in the Billing and Cost Management console.
- C.Set up AWS Budgets for each department with alerts.
- D.Create AWS Resource Groups for each department and use AWS Config to track costs.
Why B: Cost allocation tags allow you to tag AWS resources with department-specific metadata (e.g., 'Department: Finance') and then activate those tags in the Billing and Cost Management console. Once enabled, AWS Cost Explorer and cost reports can filter and group costs by these tags, providing accurate per-department cost tracking across multiple accounts in AWS Organizations. This is the most precise method because it directly associates resource usage with the department responsible, regardless of which account hosts the resource.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAP-C02 exam.