Skip to content

SAP-C03 · Domain 3: Cost-Optimized Architecture Design · 15% of the exam

Task 3.3: Design cost allocation and visibility solutions.

Knowing who spends what: tagging strategies and their enforcement, Cost Explorer and the Cost and Usage Report, cost categories, split cost allocation and token usage for chargeback, and budgets and anomaly detection that warn early.

Study it

  • Cost allocation: tags and tag policies, cost categories, split cost allocation, budgets and anomaly detection

    Partly covered by: AWS Cost Levers

Sample questions

Try each one before opening the answer. Every option is explained, with the AWS documentation page that proves it.

Question 1 · choose 1

A company has 40 accounts. Each business unit owns several accounts, and some business units also run resources in two shared accounts, where every resource carries a cost-center tag. The costs of a shared networking account must be spread across the business units in proportion to their other costs. Finance wants monthly cost reports per business unit in Cost Explorer. Which solution meets these requirements?

  1. ACreate a separate organization for each business unit and move its accounts there so that each business unit receives its own monthly bill
  2. BActivate the tag for cost allocation, define a business-unit cost category from accounts and tags, and add a proportional split charge for networking
  3. CUse AWS Resource Groups and the Tag Editor to list each business unit's tagged resources and export the resource list for finance every month
  4. DTurn on consolidated billing and give finance the per-account totals from the monthly bill of the management account, grouped by business unit
Show the answer and why
  • ACreate a separate organization for each business unit and move its accounts there so that each business unit receives its own monthly bill

    Incorrect

    Separate organizations split billing by account but cannot assign tagged resources in shared accounts to business units or spread the networking costs.

  • BActivate the tag for cost allocation, define a business-unit cost category from accounts and tags, and add a proportional split charge for networking

    Correct

    Cost categories group costs by rules on accounts and tags, and split charge rules allocate a shared cost to other category values, for example in proportion to their costs.

  • CUse AWS Resource Groups and the Tag Editor to list each business unit's tagged resources and export the resource list for finance every month

    Incorrect

    Resource Groups and the Tag Editor find and tag resources. They do not report costs or allocate shared charges.

  • DTurn on consolidated billing and give finance the per-account totals from the monthly bill of the management account, grouped by business unit

    Incorrect

    Consolidated billing shows costs per account. It does not assign tagged resources in shared accounts to business units or split shared costs.

Accounts plus tags plus a shared cost to spread is exactly the combination that cost categories with split charge rules handle.

Question 2 · choose 1

A platform account runs shared Amazon ECS clusters on EC2 instances and Amazon EKS clusters on managed node groups. Ten teams run tasks and pods on the same instances; each team has its own Kubernetes namespace and tags its ECS tasks with its team name. Finance needs each team's share of the instance costs, in proportion to the CPU and memory its containers consumed, in the Cost and Usage Report that it already queries with Athena. Moving teams to separate accounts or dedicated nodes is ruled out, and the FinOps team will not build or run its own allocation code. Which solution meets these requirements?

  1. ACreate a cost category with a team value for each team and a split charge rule that divides the cluster costs by fixed percentages
  2. BTurn on hourly EC2 resource-level data in Cost Explorer and report the cost of each cluster instance to the teams that use it
  3. CTag every EC2 instance in the clusters with a team tag and activate that tag as a cost allocation tag for the billing reports
  4. DTurn on split cost allocation data for ECS and EKS, and activate the team task tags and the aws:eks:namespace tag
Show the answer and why
  • ACreate a cost category with a team value for each team and a split charge rule that divides the cluster costs by fixed percentages

    Incorrect

    Split charges spread a shared cost across cost category values evenly, by fixed percentages or in proportion to each value's other costs. None of these methods follows the CPU and memory that each team's containers actually consumed.

  • BTurn on hourly EC2 resource-level data in Cost Explorer and report the cost of each cluster instance to the teams that use it

    Incorrect

    Granular data shows the hourly cost of each EC2 instance, which is useful when an instance belongs to one owner. It cannot say how much of a shared instance each team's containers used.

  • CTag every EC2 instance in the clusters with a team tag and activate that tag as a cost allocation tag for the billing reports

    Incorrect

    Cost allocation tags on resources work when a team owns whole instances, such as a dedicated node group. A shared instance carries one tag value, so its cost cannot be divided by which team's containers used it.

  • DTurn on split cost allocation data for ECS and EKS, and activate the team task tags and the aws:eks:namespace tag

    Correct

    Split cost allocation data adds ECS task and Kubernetes pod line items to the CUR, priced from the amortized instance cost and the share of CPU and memory that each container consumed. ECS task tags and the generated EKS namespace tag then attribute those costs to teams.

The deciding constraints are shared instances, allocation by consumed CPU and memory, and no custom code. Split charges divide shared costs by rules that ignore container usage, and instance-level data or tags can only assign whole instances. Split cost allocation data puts container-level costs straight into the CUR, where task tags and namespace tags map them to teams.

Question 3 · choose 1

A business unit spans 25 member accounts. Its finance lead needs to analyze the unit's costs in Cost Explorer across those accounts without being given access to the management account. Which approach fits?

  1. ATurn on Cost Explorer in each member account separately
  2. BShare a custom billing view for the business unit with the lead's account
  3. CGive the finance lead an IAM user in the management account with read-only access
  4. DAWS Budgets reports emailed to the finance lead every month
Show the answer and why
  • ATurn on Cost Explorer in each member account separately

    Incorrect

    Analysis would still be split across 25 accounts.

  • BShare a custom billing view for the business unit with the lead's account

    Correct

    A custom billing view shared with an account lets its users analyze that business unit's costs in Cost Explorer without access to the management account.

  • CGive the finance lead an IAM user in the management account with read-only access

    Incorrect

    This grants the management account access the company wants to avoid.

  • DAWS Budgets reports emailed to the finance lead every month

    Incorrect

    Budgets reports send the performance of existing budgets to email addresses on a schedule. They do not let the lead analyze the unit's costs in Cost Explorer.

Shared custom billing views give scoped cost visibility across accounts.

Question 4 · choose 1

Leadership wants one page that shows monthly costs, Savings Plans coverage and utilization, actual and forecasted spend against budgets, and recently detected cost anomalies. Finance partners who work in their own AWS accounts, some outside the organization, must be able to open the page, and the CFO wants it as a PDF by email every week. The FinOps team will not run a business intelligence service or build a data pipeline for this. Which solution meets these requirements?

  1. ACreate a Billing and Cost Management dashboard with widgets for each view, share it, and schedule weekly PDF delivery
  2. BConfigure an AWS Budgets report that emails the status of every budget to the CFO and the finance partners each week
  3. CBuild a CloudWatch dashboard from the estimated charges billing metrics and share it with the finance partners' accounts
  4. DExport CUR 2.0 to Amazon S3, query it with Athena, and build the views in Amazon Quick Sight dashboards for the partners
Show the answer and why
  • ACreate a Billing and Cost Management dashboard with widgets for each view, share it, and schedule weekly PDF delivery

    Correct

    Dashboards combine Cost Explorer, Savings Plans coverage and utilization, Budgets and detected anomalies as widgets on one page. They can be shared with accounts inside or outside the organization, and PDF reports can be emailed to stakeholders on a daily, weekly or monthly schedule.

  • BConfigure an AWS Budgets report that emails the status of every budget to the CFO and the finance partners each week

    Incorrect

    Budgets reports deliver the performance of existing budgets to up to 50 email addresses on a daily, weekly or monthly cadence, which covers the weekly email, but not Savings Plans coverage, anomalies or a shared interactive page.

  • CBuild a CloudWatch dashboard from the estimated charges billing metrics and share it with the finance partners' accounts

    Incorrect

    Billing metrics in CloudWatch carry estimated charges per service and in total, which suits billing alarms. They hold no Savings Plans coverage, budget status or anomaly data.

  • DExport CUR 2.0 to Amazon S3, query it with Athena, and build the views in Amazon Quick Sight dashboards for the partners

    Incorrect

    Quick Sight builds business intelligence dashboards and can show any view of exported cost data, but the export, the Athena tables and the dashboards are the pipeline and the BI service that the team will not run.

The constraints are four data sources on one page, sharing outside the organization, a scheduled PDF, and nothing to build or run. Budgets reports cover only budgets, CloudWatch billing metrics cover only estimated charges, and a CUR-based Quick Sight solution needs a pipeline and a BI service. Billing and Cost Management Dashboards provide every widget, cross-account sharing and scheduled PDF delivery as part of the billing console.

Question 5 · choose 1

A company is giving each development team its own sandbox account. Each sandbox has a monthly limit of 2,000 USD. When forecast spend reaches 80% of the limit, the team must be notified; when actual spend reaches the limit, the team's IAM role must lose permission to launch new resources until finance reviews it. Which solution meets these requirements with the LEAST custom code?

  1. ACreate a cost budget per account with an 80% forecast alert and a budget action that applies a restrictive IAM policy at 100%
  2. BTurn on AWS Cost Anomaly Detection for each sandbox account and send its anomaly alerts to the development team
  3. CCreate a CloudWatch billing alarm for each account that sends an Amazon SNS notification when charges reach 2,000 USD
  4. DReview the AWS Trusted Advisor cost optimization checks for each sandbox account at the end of every month
Show the answer and why
  • ACreate a cost budget per account with an 80% forecast alert and a budget action that applies a restrictive IAM policy at 100%

    Correct

    AWS Budgets can alert on forecast and actual spend, and budget actions can apply an IAM policy or SCP automatically, or after approval, when a threshold is reached.

  • BTurn on AWS Cost Anomaly Detection for each sandbox account and send its anomaly alerts to the development team

    Incorrect

    Cost Anomaly Detection alerts on unusual spend patterns. It does not track a fixed limit or apply any policy.

  • CCreate a CloudWatch billing alarm for each account that sends an Amazon SNS notification when charges reach 2,000 USD

    Incorrect

    A billing alarm notifies, but removing permissions would need custom code subscribed to the notification, and there is no forecast alert.

  • DReview the AWS Trusted Advisor cost optimization checks for each sandbox account at the end of every month

    Incorrect

    Trusted Advisor recommends savings. It does not enforce a limit, and a monthly review comes too late.

Budgets cover both halves: forecast alerts for awareness and budget actions for control.

Question 6 · choose 1

Finance asks for the cost of every individual EC2 instance, EBS volume and S3 bucket over the past year, grouped by cost allocation tag, so it can find waste. The data must be queryable with SQL and refreshed automatically. Which approach meets these requirements?

  1. ATurn on resource-level data in Cost Explorer and export the grouped cost and usage view every month
  2. BExport CUR 2.0 with resource IDs through AWS Data Exports to Amazon S3 and query it with Amazon Athena
  3. CDownload the monthly invoice PDFs from the Billing console and load them into a shared spreadsheet
  4. DCreate an AWS Budgets cost budget for each tag value and compare the budgets with each other every month
Show the answer and why
  • ATurn on resource-level data in Cost Explorer and export the grouped cost and usage view every month

    Incorrect

    Resource-level data in Cost Explorer covers only the past 14 days at daily granularity, so it cannot show a full year per resource.

  • BExport CUR 2.0 with resource IDs through AWS Data Exports to Amazon S3 and query it with Amazon Athena

    Correct

    Data Exports creates recurring exports of CUR 2.0 in Amazon S3, a standard export can include the ID of each resource, and the exports can be analyzed with tools such as Amazon Athena.

  • CDownload the monthly invoice PDFs from the Billing console and load them into a shared spreadsheet

    Incorrect

    Invoices summarize charges. They do not list each resource or its tags.

  • DCreate an AWS Budgets cost budget for each tag value and compare the budgets with each other every month

    Incorrect

    Budgets track spend against thresholds. They do not give per-resource costs that can be queried with SQL.

Per-resource, per-tag cost data over long periods comes from the Cost and Usage Report, delivered by Data Exports and queried with Athena.

Question 7 · choose 1

A company's FinOps team allocates cloud costs from AWS and two other cloud providers in one third-party analytics tool. The tool ingests billing data in the FinOps Open Cost and Usage Specification (FOCUS) format. The team wants AWS billing data for all accounts of the organization delivered in that format to S3 automatically, without writing transformation code. Which approach meets these requirements?

  1. ATurn on the legacy Cost and Usage Report and convert its line items to the FOCUS schema each month with an AWS Glue ETL job
  2. BSchedule Cost Explorer reports that the team downloads and maps to FOCUS columns each month
  3. CCreate an AWS Data Exports export of the FOCUS 1.2 with AWS columns table from the management account, delivered to S3
  4. DSet up AWS Budgets reports for each account and send them to the analytics tool by email
Show the answer and why
  • ATurn on the legacy Cost and Usage Report and convert its line items to the FOCUS schema each month with an AWS Glue ETL job

    Incorrect

    This needs a transformation job to build and maintain, while AWS Data Exports can produce FOCUS data directly.

  • BSchedule Cost Explorer reports that the team downloads and maps to FOCUS columns each month

    Incorrect

    Manual downloads and mapping are neither automatic nor free of transformation work.

  • CCreate an AWS Data Exports export of the FOCUS 1.2 with AWS columns table from the management account, delivered to S3

    Correct

    Data Exports offers FOCUS tables with AWS columns as a standard export type and delivers them to S3 on a schedule, so no conversion code is needed.

  • DSet up AWS Budgets reports for each account and send them to the analytics tool by email

    Incorrect

    Budgets reports summarize spend against budgets. They are not detailed billing data in the FOCUS schema.

AWS Data Exports can deliver billing data in the open FOCUS schema, with AWS-specific columns, for multi-cloud FinOps tools, alongside CUR 2.0 and other export types.

Practice domain 3 →Practice all domains →