Cost reporting, budgets and anomaly detection: SAP-C03 study notes and practice questions
What to know about Cost reporting, budgets and anomaly detection for the SAP-C03 exam, from the Cost-Optimized Architecture Design domain (15% of the exam guide), then 1 free question to test it. Part of the SAP-C03 study guide.
SAP-C03 cost monitoring questions ask how finance and engineering get detailed, trusted cost data across an organization, and how they hear about overspend before the monthly invoice.
Reporting
Tool
Gives you
Use when
Cost Explorer
Interactive charts by service, account, tag, cost category and usage type; forecasts; Savings Plans and RI utilization and coverage; rightsizing and commitment recommendations
Quick analysis without building anything
CUR 2.0 via AWS Data Exports
Line-item billing data (hourly, daily or monthly) with resource IDs, tags, cost categories, discounts and split cost allocation data, delivered to S3 in Parquet or CSV
Detailed, custom or chargeback reporting
FOCUS export (Data Exports)
Billing data in the open FinOps FOCUS format
Combining AWS with other clouds’ data
Athena and QuickSight
SQL queries and dashboards over the exports, such as the Cloud Intelligence Dashboards
Organization-wide FinOps dashboards
Billing views
Share a filtered cost view with a member account owner
Let business units see their own costs
Create exports in the management account to cover every member account, and partition them in S3 for Athena. The legacy CUR still exists, but new designs use CUR 2.0, which has a fixed schema.
Alerts
AWS Budgets tracks cost, usage, Savings Plans and RI utilization and coverage, against actual or forecasted amounts, and notifies by email, SNS or chat. Budgets can be filtered by account, tag, cost category or service.
Budget actions respond automatically when a threshold is crossed: apply an IAM policy or SCP (for example, deny launching new instances), or stop EC2 or RDS instances, with or without approval.
AWS Cost Anomaly Detection uses machine learning to learn normal spend and flags unusual increases. Monitors watch AWS services, linked accounts, cost categories or cost allocation tags. Alert subscriptions send individual alerts immediately through SNS, or daily or weekly summaries by email, with a threshold in dollars or percent. Each anomaly shows its likely root cause (service, account, Region, usage type).
Route SNS alerts to EventBridge, Lambda or chat for automated response.
Design patterns
One budget per account or cost category, owned by the team that can act on it, plus organization-wide budgets in the management account.
Anomaly monitors per cost category or business-unit tag, so alerts go to the owners, not only to finance.
Commitment coverage and utilization budgets warn when Savings Plans are underused or when new usage runs uncovered.
How to choose
Scenario wording
Pick
“Alert when forecast spend will exceed the monthly budget”
AWS Budgets with a forecasted threshold
“Stop new spend in a sandbox once it reaches its limit”
Budget action applying an SCP or IAM policy
“Detect a sudden spike nobody predicted, without setting thresholds”
Cost Anomaly Detection
“Line-item cost by resource and tag for chargeback”
CUR 2.0 in S3, queried with Athena
“Savings Plans utilization dropping”
Utilization budget
Common traps
Static CloudWatch billing alarms as the main tool across many accounts (they work on estimated charges only and live in us-east-1).
Budgets to find unknown spikes; budgets compare to a fixed number, anomaly detection learns patterns.
Cost Explorer for line-item, per-resource chargeback at scale.
Creating exports in each member account instead of once from the management account.
A retailer's finance team wants to know before the month ends when account spend is likely to pass its approved budget, and it wants to hear about sudden unexplained spikes the same day, not at the end of the billing period.
The spend comes from several accounts, and the team wants the alerts delivered to an email list through a managed notification service, with no servers to run.
Which solution meets these requirements?
Choose one answer.
AA. Open Cost Explorer once a week, filter by account, and compare the month-to-date total with the approved budget in a shared spreadsheet.
BB. Create an AWS Budgets forecasted-spend alert for the approved amount and a Cost Anomaly Detection monitor with individual alerts, both sent to an SNS topic that emails the finance list.
CC. Export the Cost and Usage Report to Amazon S3 each day, and run an Amazon Athena query by hand whenever someone wants to compare the month-to-date spend against the approved budget for the month.
DD. Write a Lambda function that runs every hour, reads the account's spend from the Cost Explorer API, and posts the total to a chat channel.
Show the answer and explanation
Answer: B
A. Wrong: Weekly manual checks do not warn before the month ends or flag a spike on the day it happens. The spreadsheet is also a manual process.
B. Right: Correct. The budget alert fires on the forecast before the limit is reached, and the anomaly monitor flags unusual spend on the day it happens. SNS delivers both to the email list without any servers to run.
C. Wrong: The report and the query give the data, but nothing alerts the finance team before the limit or on a spike. The team would still check it by hand.
D. Wrong: The function can work, but the team would build and maintain the polling and the alert logic itself. Budgets and anomaly detection provide these alerts as managed features.
Explanation
Budgets forecast alerts warn before the limit, and Cost Anomaly Detection flags unusual spikes, with SNS delivering both to email. Manual checks, a hand-run query and a custom polling function each miss the early warning or add work.
Want more on Cost reporting, budgets and anomaly detection? The 5 full-length practice sets have 5 more Cost reporting, budgets and anomaly detection questions, 375 in all, none of them in the free exam. One payment of $14.99, no subscription. See the practice sets →
Study Cost reporting, budgets and anomaly detection