How Do You Configure Cost Explorer to Show Costs per Project?

SOA-C03 By islever Editorial Last updated Oct 20, 2026

Short answer

A Activate user-defined cost allocation tags in the Billing console and apply a Project tag to resources so Cost Explorer can group costs by project.

Question

A company's financial department needs to view the cost details of each project in an AWS account. A CloudOps engineer must perform the initial configuration that is required to view cost for each project in Cost Explorer.
Which solution will meet this requirement?

Activate cost allocation tags. Add a project tag to the appropriate resources. Correct Answer
Configure consolidated billing. Create AWS Cost and Usage Reports.
Use AWS Budgets. Create AWS Budgets reports.
Use cost categories to define custom groups that are based on AWS cost and usage dimensions.

Key Takeaways

The exam tests the prerequisite for tag-based Cost Explorer reporting: activation plus resource tagging. The trap is selecting cost categories or budgets, which group or monitor costs but do not create the project tag dimension.

AWS Cost Explorer needs user-defined cost allocation tags to be activated and applied before project costs can be grouped by a Project tag. This page establishes that option A is the required initial configuration, not budgets, CUR, or cost categories alone.

Common mistake: Many candidates choose cost categories because they create custom groups, but cost categories rely on existing dimensions and do not activate user-defined tags or apply Project tags to resources.

Expert Analysis

Why the Answer Is Correct

AWS Cost Explorer can group and filter cost by user-defined cost allocation tags only after those tag keys are activated in the Billing and Cost Management console. The engineer must first activate the Project tag key, then ensure every resource that belongs to a project carries the correct Project key/value; otherwise Cost Explorer has no project dimension to display. Option A captures both required initial actions — activation and resource tagging — which is why it satisfies the "initial configuration" wording. Bad_Mat's comment supports this sequence, noting that activating user-defined cost allocation tags and applying Project tags is what makes per-project spend visible in Cost Explorer.

Why the Other Options Are Wrong

B is wrong because consolidated billing groups accounts under one payer and Cost and Usage Reports deliver detailed billing data, but neither activates a project tag dimension for Cost Explorer's initial view. C is wrong because AWS Budgets monitors thresholds and sends alerts; a budget report is not the configuration that makes per-project costs available in Cost Explorer. D is wrong because cost categories define custom groupings on top of existing dimensions such as tags or accounts; they do not activate user-defined tags or ensure resources carry a Project tag, so they cannot be the initial setup by themselves. Without activated, applied tags, all three approaches fail to produce the project-level breakdown the finance department requested.

Community Comment Notes

The single visible learner comment, from Bad_Mat, agrees with option A and stresses the two-step sequence: "Activate cost allocation tags" and then apply the Project tag to resources. That aligns with AWS's documented prerequisite for user-defined tag visibility in Cost Explorer. No contrary reasoning appears in the provided comments, so the community signal here is consistent with the technical analysis rather than merely a vote count.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

When a question asks for the "initial configuration" to view Cost Explorer by project, look for tag activation plus resource tagging, not downstream reporting tools. Budgets and cost categories are useful later, but they cannot create the tag dimension without the initial tagging setup.

Frequently Asked Questions

Why is a cost category not enough to show project costs in Cost Explorer?

Cost categories group costs using existing tags or accounts, but they do not activate user-defined tags or apply Project tags, so they cannot replace the initial tagging setup.

Do user-defined cost allocation tags appear in Cost Explorer immediately after tagging?

No. The tag key must be activated in the Billing console first, and activation can take up to 24 hours before tag data appears in Cost Explorer.

More SOA-C03 FAQ →

Discussion 1 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 1

Bad_Mat 👍 1 Answered A

The correct answer is A. Activate cost allocation tags. Add a project tag to the appropriate resources.To view expenses per project in AWS Cost Explorer, you must first enable user-defined cost allocation tags in the Billing console and then apply the corresponding Project tag keys and values to your AWS resources.Why This Option WorksActivation: Activating tags tells AWS to track tag data for billing metrics.Granularity: Applying the project tags lets you group and filter usage data directly inside Cost Explorer.

Reader comments & corrections

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

Practice All SOA-C03 Questions

Access 100 questions with complete answers and detailed explanations.

View Full SOA-C03 Practice Test →

← Back to SOA-C03 Study Guide