The correct choice is to implement cost allocation tags for resources and use AWS Cost Explorer to filter by tags. This works because cost allocation tags allow you to attach department-specific metadata—such as 'Department: Engineering'—directly to AWS resources across multiple accounts. Once these tags are activated in the Billing and Cost Management console, AWS Cost Explorer can group and filter costs by those tags, delivering granular cost visibility per department that goes far beyond the account-level view provided by consolidated billing. On the AWS Certified Solutions Architect Professional SAP-C02 exam, this concept tests your understanding of how to bridge the gap between high-level organizational billing and detailed departmental accountability. A common trap is assuming that enabling consolidated billing alone provides per-department insights, but without tags and Cost Explorer, you only see aggregate account costs. Memory tip: think of tags as the "department labels" and Cost Explorer as the "magnifying glass"—you need both to see the granular picture.
SAP-C02 Practice Question: Design Solutions for Organizational Complexity
This SAP-C02 practice question tests your understanding of design solutions for organizational complexity. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company manages multiple AWS accounts and wants to centralize billing and cost tracking. They have enabled AWS Organizations and consolidated billing. Which additional step should they take to gain granular visibility into costs per department?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Implement cost allocation tags for resources and use AWS Cost Explorer to filter by tags
Option C is correct because cost allocation tags allow you to tag AWS resources with department-specific metadata (e.g., 'Department: Engineering'). Once enabled and activated in the Billing and Cost Management console, AWS Cost Explorer can filter and group costs by these tags, providing granular visibility into per-department spending across multiple accounts in an AWS Organization. This approach directly addresses the need for department-level cost tracking beyond the account-level view provided by consolidated billing.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Enable AWS Cost Explorer and use default groupings
Why it's wrong here
Default groupings may not reflect departments without tags.
✗
Create AWS Budgets for each department
Why it's wrong here
Budgets only provide alerts, not granular cost visibility.
✓
Implement cost allocation tags for resources and use AWS Cost Explorer to filter by tags
Why this is correct
Tags enable granular cost tracking by department.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use the consolidated billing feature to view costs per account
Why it's wrong here
Per-account view is available but not per-department if multiple departments share an account.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse the account-level aggregation of consolidated billing (Option D) with the resource-level granularity needed for department tracking, or they assume AWS Budgets (Option B) provide visibility rather than just alerts.
Detailed technical explanation
How to think about this question
Cost allocation tags must be activated in the Billing and Cost Management console before they appear in Cost Explorer; tags applied to resources are not automatically visible for cost tracking until activated. AWS also supports AWS-generated tags (e.g., aws:createdBy) and user-defined tags, but only user-defined tags that are activated can be used for cost filtering. In a multi-account organization, tags propagate to the management account's Cost Explorer, enabling centralized, cross-account cost analysis by department.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Design Solutions for Organizational Complexity — This question tests Design Solutions for Organizational Complexity — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Implement cost allocation tags for resources and use AWS Cost Explorer to filter by tags — Option C is correct because cost allocation tags allow you to tag AWS resources with department-specific metadata (e.g., 'Department: Engineering'). Once enabled and activated in the Billing and Cost Management console, AWS Cost Explorer can filter and group costs by these tags, providing granular visibility into per-department spending across multiple accounts in an AWS Organization. This approach directly addresses the need for department-level cost tracking beyond the account-level view provided by consolidated billing.
What should I do if I get this SAP-C02 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.