AWS Organizations for Cost Separation and Tracking

Understand concepts of cloud economics. Understand AWS Cloud security, governance, and compliance concepts.

Answer Correct answer: A — Use AWS Organizations and create one account for each business unit to isolate and track costs natively.

A company wants to launch multiple workloads on AWS. Each workload is related to a different business unit. The company wants to separate and track costs for each business unit. Which solution will meet these requirements with the LEAST operational overhead?

Use AWS Organizations and create one account for each business unit. Correct Answer
Use a spreadsheet to control the owners and cost of each resource.
Use an Amazon DynamoDB table to record costs for each business unit.
Use the AWS Billing console to assign owners to resources and track costs.

Community Votes

82%

18%

82% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

The exam tests the understanding that account isolation via AWS Organizations is the standard best practice for cost management, whereas tagging or manual assignment in a single account introduces significant ongoing maintenance overhead.

This question addresses the optimal strategy for separating and tracking costs across multiple business units on AWS. The correct solution leverages AWS Organizations to create isolated accounts, providing native cost separation with minimal operational overhead.

Many learners choose Option D, believing that using tags and the billing console requires less effort than managing separate accounts. However, this ignores the operational burden of maintaining consistent tagging policies and manually assigning ownership as resources scale.

Community Discussion (8 comments)

teegee 👍 1 Selected: A

A is correct

ShaiTay 👍 1 Selected: A

A. Use AWS Organizations and create one account for each business unit. - AWS Organizations allows you to organize all accounts under one master/management account. Then you can easily track costs.

chalaka 👍 1 Selected: A

A. Use AWS Organizations and create one account for each business unit. AWS Organizations allows you to centrally manage and govern multiple AWS accounts. By creating separate AWS accounts for each business unit, the company can easily separate and track costs for each unit. AWS provides consolidated billing, which aggregates the charges for all linked accounts in a single bill while still allowing detailed cost reporting at the account level. This approach provides a clean separation of costs for each business unit with minimal operational overhead.

517d694 👍 1 Selected: A

A. The least overhead is just having an account per BU. Otherwise you need to assing owners, work with tags, and have a billing structure you need to maintain.

Felicia_T 👍 2 Selected: A

A. Use AWS Organizations and create one account for each business unit.

Dutch_delight 👍 1

I really think it should be D. Because google bard says: Therefore, considering the trade-off between functionality and operational overhead, D. Using the AWS Billing console with owners is the solution with the LEAST operational overhead. It offers a balance between ease of use and cost separation while avoiding the significant management overhead of separate accounts or custom solutions like spreadsheets or DynamoDB tables.

komorebi 👍 3 Selected: A

ChatGPT Answer The most suitable solution that meets the requirements with the least operational overhead is: A. Use AWS Organizations and create one account for each business unit. Using AWS Organizations allows you to centrally manage and govern multiple AWS accounts. By creating separate accounts for each business unit, you can easily isolate and track costs for each unit without mixing them up. This approach provides a clear separation of resources and costs, simplifying cost management and tracking. Additionally, AWS provides consolidated billing and cost allocation features within Organizations, making it easier to manage billing and costs across multiple accounts.

JackHerer 👍 2 Selected: D

This is the answer from AI. D. Use the AWS Billing console to assign owners to resources and track costs. Here's why the other options might not be optimal: A. Use AWS Organizations and create one account for each business unit: This approach provides strong isolation but significantly increases management complexity and overhead due to managing multiple separate accounts. B. Use a spreadsheet to control the owners and cost of each resource: This is a manual and error-prone method, not scalable for multiple workloads and business units, and prone to human error. C. Use an Amazon DynamoDB table to record costs for each business unit: While offering flexibility, setting up and maintaining a DynamoDB table adds unnecessary complexity and overhead compared to built-in tools.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

Option A is the correct answer because AWS Organizations allows you to create separate AWS accounts for each business unit. Each account has its own set of resources, IAM identities, and billing. When you enable consolidated billing, AWS automatically separates the costs by account, allowing you to track spend per business unit natively without complex configuration. This provides strong isolation and meets the requirement with the least operational overhead in the long run, as there is no need to maintain tagging policies or custom tracking logic.

Why the Other Options Are Wrong

Option B is incorrect because using a spreadsheet is a manual process that does not integrate with AWS services, leading to high error rates and significant operational overhead. Option C is incorrect because DynamoDB is a database service; while you could theoretically store cost data there, it requires building custom integration (e.g., Lambda functions parsing CloudBill exports) which is highly complex and not a native cost management solution. Option D is incorrect because while tagging can separate costs, it requires rigorous enforcement of tagging standards across all teams. Assigning 'owners' in the billing console is not a persistent, automated mechanism for resource-level cost allocation and does not provide the same level of structural isolation as separate accounts.

Community Comment Notes

The majority of the community correctly identified Option A, noting that "AWS Organizations allows you to centrally manage and govern multiple AWS accounts" and that separate accounts prevent mixing costs. Some users argued for Option D, suggesting it offers "a balance between ease of use and cost separation," but this view overlooks the scalability issues of manual tagging and ownership assignments compared to the structural clarity of separate accounts. One commenter noted that separate accounts avoid the need to "assign owners, work with tags, and have a billing structure you need to maintain."

Exam Strategy

When asked about cost separation, always consider whether separate AWS Accounts are an option. If the requirement involves distinct business units, projects, or environments, separate accounts via AWS Organizations are typically the most robust and lowest-overhead solution for cost isolation.

Frequently Asked Questions

Why is tagging not the best solution for cost separation?

Tagging requires strict governance and continuous monitoring to ensure all resources are tagged correctly. It adds operational overhead compared to the automatic separation provided by separate accounts.

Does consolidated billing mix up costs from different accounts?

No. Consolidated billing aggregates payments into one bill, but each linked account retains its own separate detailed invoice and cost breakdown, preserving visibility per business unit.

Related Analysis

Practice All CLF-C02 Questions

Access 120 questions with complete answers and detailed explanations.

View Full CLF-C02 Practice Test →

← Back to CLF-C02 Study Guide