Billing, Pricing, Cost Management & Support
By Pritesh Yadav 22 min read —
This topic is mostly about picking the right tool for the right job and knowing what each Support plan includes. The exam loves to confuse the four cost tools: the Pricing Calculator estimates future costs before you build, Cost Explorer visualizes and analyzes past/current spend, AWS Budgets alerts you when spend crosses a threshold, and the Cost & Usage Report (CUR) gives the most granular line-item data. You also need the three pricing drivers (compute, storage, data transfer OUT), the three free-tier flavors, and exactly which Support tier first unlocks a Technical Account Manager (TAM) and full Trusted Advisor checks.
Most confused here: Calculator = estimate before building; Cost Explorer = analyze/visualize spend; Budgets = alert on a threshold; CUR = most granular line items. Business plan = full Trusted Advisor + 24/7 phone/chat; Enterprise plan = a dedicated TAM. Inbound data transfer is free; data transfer OUT to the internet costs money.
Q1 A company is still in the design phase and has not launched anything in AWS. They want a monthly cost estimate for a proposed architecture of EC2 instances, an RDS database, and an S3 bucket. Which tool fits this need?
- AWS Cost Explorer
- AWS Pricing Calculator
- AWS Budgets
- AWS Cost & Usage Report
Answer: B
Why B is correct: The AWS Pricing Calculator lets you model services you have not deployed yet and produces a forward-looking estimate. Because nothing is running, there is no usage data to analyze, so an estimation tool is exactly what you need.
Why the other options are wrong:
- A — Cost Explorer only visualizes spend that has already happened; with no running resources it has nothing to show.
- C — Budgets sets alerts against actual or forecasted spend on an existing account, not a pre-build estimate.
- D — The Cost & Usage Report details past billing line items, which do not exist before launch.
Common trap: Candidates pick Cost Explorer because it has the word "cost," but it analyzes existing usage. "Before you build" almost always means Pricing Calculator.
Q2 A finance manager wants to receive an email alert as soon as the month's actual spend reaches 80% of $5,000. Which service is purpose-built for this?
- AWS Budgets
- AWS Cost Explorer
- AWS Pricing Calculator
- Amazon CloudWatch billing metric only
Answer: A
Why A is correct: AWS Budgets is designed to set a cost or usage threshold and trigger a notification (email or SNS) when actual or forecasted spend crosses it. An 80%-of-$5,000 alert is a textbook Budgets use case.
Why the other options are wrong:
- B — Cost Explorer shows charts and trends but does not send threshold alerts on its own.
- C — The Pricing Calculator only produces pre-build estimates and has no alerting.
- D — A raw CloudWatch billing alarm can fire on a charge, but AWS Budgets is the dedicated, recommended budgeting/alerting tool and supports forecasted and usage budgets too.
Common trap: "Alert" plus "threshold" should map straight to Budgets. Cost Explorer is for analysis, not proactive alerts.
Q3 An analyst needs to understand why last quarter's bill rose by drilling into spend trends by service and region using interactive graphs. Which tool is the best fit?
- AWS Budgets
- AWS Pricing Calculator
- AWS Cost Explorer
- AWS Trusted Advisor
Answer: C
Why C is correct: Cost Explorer provides visual, filterable graphs of historical and current spend, letting you slice by service, region, tag, and time to explain cost changes. Analyzing "why the bill went up" is its core purpose.
Why the other options are wrong:
- A — Budgets alerts on thresholds; it is not an analysis/visualization tool.
- B — The Pricing Calculator estimates future costs, not past trends.
- D — Trusted Advisor gives best-practice recommendations (including some cost tips) but is not a spend-trend analysis dashboard.
Common trap: Trusted Advisor's "cost optimization" category tempts people, but trend analysis with graphs is Cost Explorer.
Q4 A company needs the most granular, line-item-level billing data exportable to Amazon S3 so a data team can load it into Amazon Athena for custom analysis. Which option provides this?
- The Billing Dashboard summary page
- AWS Budgets reports
- AWS Cost & Usage Report (CUR)
- Cost Explorer CSV export
Answer: C
Why C is correct: The Cost & Usage Report is the most detailed billing data AWS offers, breaking spend down to the hourly/resource line-item level and delivering it to an S3 bucket for analysis with tools like Athena, QuickSight, or Redshift.
Why the other options are wrong:
- A — The Billing Dashboard is a high-level summary, not granular exportable line items.
- B — Budgets produces alerts and simple reports, not detailed line-item exports to S3.
- D — Cost Explorer can export a summarized CSV but not the full resource-level granularity the CUR provides.
Common trap: "Most granular / line-item / export to S3 for Athena" is the signature of CUR, not Cost Explorer.
Q5 Which set correctly lists the three fundamental cost drivers that AWS says determine most of your bill?
- Number of users, number of Regions, number of IAM roles
- Compute, storage, and outbound data transfer
- Support plan tier, number of tags, and Availability Zones
- Reserved Instances, Savings Plans, and Spot Instances
Answer: B
Why B is correct: AWS frames pricing around three pillars: compute (what you run, e.g., EC2), storage (what you keep, e.g., S3/EBS), and data transfer OUT of AWS. Almost every service bill maps back to these.
Why the other options are wrong:
- A — IAM roles and users are free; these are not pricing drivers.
- C — Tags and AZs do not themselves carry charges; the support plan is a separate cost, not a fundamental driver.
- D — Those are pricing models for compute, not the three fundamental drivers.
Common trap: Pricing models (RIs, Savings Plans, Spot) are ways to pay for compute, not the underlying cost categories.
Q6 A team is surprised by charges on their bill. They transferred 500 GB into AWS from their data center and served 500 GB out to internet users. Which statement about these transfers is correct?
- Both the inbound and outbound transfers are charged equally
- Inbound is charged; outbound to the internet is free
- Both inbound and outbound transfers are always free
- Inbound (data in) is generally free; outbound to the internet (data out) is charged
Answer: D
Why D is correct: AWS generally does not charge for data transferred into its network, but it charges for data transferred out to the internet beyond the free allowance. This is why "data transfer OUT" is the third cost driver.
Why the other options are wrong:
- A — They are not charged equally; direction matters.
- B — This reverses reality; inbound is the free one.
- C — Outbound internet transfer is not free beyond the free-tier allowance.
Common trap: People assume transfer is symmetric. Remember: into AWS is usually free, out to the internet costs money.
Q7 The AWS Free Tier's "always free" category, unlike the "12-month free" category, means which of the following?
- The offer never expires as long as you stay within the stated limits
- The offer is free only for the first 12 months after account creation
- The offer is a short trial that expires after 30 or 60 days
- The offer is free only for customers on a paid Support plan
Answer: A
Why A is correct: "Always free" offers (for example, a monthly allotment of AWS Lambda requests or DynamoDB storage) never expire as long as your usage stays under the published limits, regardless of account age.
Why the other options are wrong:
- B — That describes the 12-month free tier (e.g., a small EC2/RDS allowance), not always free.
- C — That describes trial offers, which are short-term.
- D — Free-tier eligibility is not tied to a paid Support plan.
Common trap: Three flavors exist — Always Free, 12-Month Free, and Trials. Lambda/DynamoDB monthly limits are Always Free; the small EC2/RDS allowances are 12-month.
Q8 A growing company needs 24/7 access to AWS Support engineers by phone, chat, and email, plus the full set of Trusted Advisor checks, but does NOT need a dedicated Technical Account Manager. What is the lowest-cost plan that meets these needs?
- Developer
- Business
- Enterprise On-Ramp
- Enterprise
Answer: B
Why B is correct: The Business plan is the first tier offering 24/7 phone, chat, and email support to engineers and the full set of Trusted Advisor checks. It does not include a dedicated TAM, which matches the requirement exactly while keeping cost down.
Why the other options are wrong:
- A — Developer offers only business-hours email-style access to a Support associate and a limited subset of Trusted Advisor checks.
- C — Enterprise On-Ramp adds a pool of TAMs and costs more than needed.
- D — Enterprise includes a dedicated TAM and is the most expensive — more than required.
Common trap: Full Trusted Advisor + 24/7 engineer access starts at Business. A dedicated TAM only starts at Enterprise.
Q9 Which AWS Support plan is the first (lowest) tier to include a designated Technical Account Manager (TAM) who is assigned to your account?
- Business
- Enterprise On-Ramp
- Enterprise
- Developer
Answer: C
Why C is correct: A single designated Technical Account Manager — a named individual who knows your environment — is a defining benefit of the Enterprise plan. Enterprise On-Ramp gives access to a pool of TAMs, not a designated one.
Why the other options are wrong:
- A — Business has concierge-style support but no TAM.
- B — Enterprise On-Ramp provides a pool/team of TAMs, not a single designated TAM.
- D — Developer is the cheapest paid tier and includes no TAM.
Common trap: Enterprise On-Ramp = a pool of TAMs; only full Enterprise gives a designated TAM. The exam tests this exact wording difference.
Q10 Which capability is included even with the free Basic Support plan that every AWS account receives?
- 24/7 access to Cloud Support Engineers by phone
- A designated Technical Account Manager
- The full set of Trusted Advisor checks across all categories
- A limited set of Trusted Advisor checks (service limits and basic security)
Answer: D
Why D is correct: Even Basic Support includes a core subset of Trusted Advisor checks — the service-limit checks and a few basic security checks — plus 24/7 access to customer service, documentation, and forums.
Why the other options are wrong:
- A — Access to Cloud Support Engineers requires a paid plan (Developer and up); Basic gives only account/billing customer service.
- B — A TAM is an Enterprise feature.
- C — The full Trusted Advisor check set unlocks at Business and above, not Basic.
Common trap: Basic isn't "nothing" — it includes a limited Trusted Advisor set. But technical help from engineers requires a paid plan.
Q11 A company runs many AWS accounts under AWS Organizations. They want a single consolidated bill and to benefit from combined usage so they reach volume pricing tiers faster. Which feature delivers this?
- Cost allocation tags
- Consolidated billing
- AWS Budgets actions
- Reserved Instance Marketplace
Answer: B
Why B is correct: Consolidated billing (a feature of AWS Organizations) combines usage across all member accounts onto one bill, so tiered/volume discounts apply to the aggregated usage and Reserved Instance/Savings Plans benefits can be shared across accounts.
Why the other options are wrong:
- A — Cost allocation tags help categorize spend, not merge billing or aggregate volume discounts.
- C — Budgets actions automate responses to thresholds; they do not consolidate bills.
- D — The RI Marketplace lets you sell unused Standard RIs — unrelated to combined billing.
Common trap: Don't confuse aggregating usage for discounts (consolidated billing) with categorizing spend (cost allocation tags).
Q12 A company wants its bill broken down by department and project so each team sees its own share of spend in Cost Explorer. What must they set up to make this possible?
- Separate AWS accounts for every project, billed independently
- A Cost & Usage Report with hourly granularity
- Cost allocation tags activated in the Billing console
- An AWS Budget per department
Answer: C
Why C is correct: Cost allocation tags are key-value labels (e.g., Department=Marketing) applied to resources and activated in the Billing console so AWS groups costs by those tags in Cost Explorer and the CUR. This is the standard way to split spend by team or project.
Why the other options are wrong:
- A — Separate accounts work but are far heavier than needed and miss the point of tag-based reporting within shared accounts.
- B — A CUR provides granularity but still relies on tags to attribute cost to departments.
- D — Budgets alert on thresholds; they do not categorize existing spend by department.
Common trap: Tags must be activated as cost allocation tags in Billing before they appear in cost reports — simply tagging a resource isn't enough.
Q13 A company has a steady, predictable compute workload and wants the maximum discount while keeping flexibility to change instance family, size, OS, and Region. Which purchase option best fits?
- Standard Reserved Instances
- On-Demand Instances
- Spot Instances
- Compute Savings Plans
Answer: D
Why D is correct: Compute Savings Plans give deep discounts (similar to RIs) in exchange for a 1- or 3-year hourly spend commitment, while remaining flexible across instance family, size, OS, tenancy, Region, and even Fargate/Lambda. That flexibility is exactly what's asked for.
Why the other options are wrong:
- A — Standard RIs offer big savings but lock you to attributes (in particular instance family/Region for the largest savings), so they are less flexible.
- B — On-Demand has no commitment and no discount — the opposite of the goal.
- C — Spot is cheapest but can be interrupted, so it suits fault-tolerant, not steady predictable, workloads.
Common trap: "Maximum discount + flexibility across families/Regions" points to Compute Savings Plans. Standard RIs save the most only if you accept rigid attributes.
Q14 Which statement best describes the difference between a Savings Plan and a Reserved Instance in how you commit?
- Savings Plans commit to a specific instance configuration; Reserved Instances commit to a dollar-per-hour amount
- Both commit only to a Region and nothing else
- Both are billed purely per second with no commitment
- Savings Plans commit to a consistent amount of spend per hour; Reserved Instances commit to a specific instance configuration
Answer: D
Why D is correct: A Savings Plan is a commitment to spend a steady dollar amount per hour (e.g., $10/hour) for 1 or 3 years, and the discount applies to matching usage. A Reserved Instance instead reserves capacity/discount for a specific instance configuration (type, Region, etc.).
Why the other options are wrong:
- A — This reverses the two: it's RIs that commit to a configuration and Savings Plans to an hourly dollar amount.
- B — RIs commit to more than just Region (instance attributes), so this is incomplete and wrong.
- C — Both require a 1- or 3-year commitment; that's the whole point of the discount.
Common trap: Remember the one-liner: Savings Plan = commit to $/hour spend; Reserved Instance = commit to a specific instance setup.
Q15 A short-lived, interruption-tolerant batch job needs the absolute lowest EC2 price and can restart if AWS reclaims the capacity. Which purchase option is the best match?
- On-Demand Instances
- Standard Reserved Instances
- Spot Instances
- Dedicated Hosts
Answer: C
Why C is correct: Spot Instances use spare AWS capacity at discounts of up to ~90% off On-Demand, but AWS can reclaim them with short notice. A fault-tolerant batch job that can restart is the ideal Spot workload.
Why the other options are wrong:
- A — On-Demand has no interruption risk but is far more expensive.
- B — RIs require a 1- or 3-year commitment, which doesn't suit a short-lived job.
- D — Dedicated Hosts are the most expensive option, used for licensing/compliance, not cheap batch work.
Common trap: "Lowest price + can tolerate interruption" is the unmistakable signature of Spot. If it could NOT tolerate interruption, Spot would be wrong.
Q16 Where in the AWS console would a new user go to see a quick summary of the current month-to-date charges and a breakdown by service, without setting up any reports?
- The AWS Billing Dashboard (Billing and Cost Management home)
- AWS Pricing Calculator
- AWS Trusted Advisor
- AWS Systems Manager
Answer: A
Why A is correct: The Billing Dashboard (the home page of Billing and Cost Management) shows month-to-date spend, a top-services summary, and recent charges at a glance with no setup required — the default landing place for "what's my bill so far."
Why the other options are wrong:
- B — The Pricing Calculator estimates future costs, not current actual charges.
- C — Trusted Advisor gives optimization recommendations, not a bill summary.
- D — Systems Manager manages operations of resources, not billing summaries.
Common trap: The Billing Dashboard is for a quick glance; Cost Explorer is for deep interactive analysis. The phrase "summary, no setup" points to the dashboard.
Q17 Under consolidated billing with AWS Organizations, how are Reserved Instance and Savings Plans discounts typically handled across the linked accounts?
- Discounts apply only to the single account that purchased them and cannot be shared
- Unused Reserved Instance and Savings Plans benefits can be shared across the organization's accounts
- All accounts lose their free tier when joined to an organization
- Discounts are split evenly regardless of which account has matching usage
Answer: B
Why B is correct: With consolidated billing (and RI/Savings Plans sharing enabled, which is the default), unused reservation and Savings Plan benefits in one account can apply to matching usage in other accounts, maximizing the value of commitments across the organization.
Why the other options are wrong:
- A — Sharing across accounts is precisely a benefit of consolidated billing, so "cannot be shared" is wrong.
- C — Free-tier benefits are typically aggregated across the org, not lost.
- D — Benefits apply to accounts with matching usage, not split evenly arbitrarily.
Common trap: A big selling point of consolidated billing is exactly this RI/Savings Plan sharing — candidates wrongly assume commitments are stuck in the buying account.
Q18 A startup wants pay-as-you-go pricing and is reviewing AWS's core pricing philosophy. Which statement reflects how AWS pricing generally works?
- You sign a fixed annual contract for capacity whether you use it or not
- Every service charges a flat monthly subscription fee per user
- You pay only for what you use, and using more often lowers the per-unit price through volume tiers
- Pricing is identical in every Region worldwide
Answer: C
Why C is correct: AWS core pricing is pay-as-you-go with no required long-term contracts, and many services offer tiered "volume" pricing where the more you use, the lower the per-unit cost. Commitments (RIs/Savings Plans) are optional discounts on top.
Why the other options are wrong:
- A — Long-term contracts are optional, not required — the opposite of pay-as-you-go.
- B — Most AWS services bill by usage (compute hours, GB stored), not per-user subscriptions.
- D — Prices vary by Region due to differing operating costs.
Common trap: Region-independent pricing is a myth; the same service can cost different amounts in different Regions.
Q19 A company on the Developer Support plan complains they cannot reach a Support engineer outside business hours and only see a handful of Trusted Advisor checks. What is the most appropriate guidance?
- Upgrade to Business Support to get 24/7 engineer access and the full Trusted Advisor check set
- Stay on Developer; 24/7 engineer access is available there too
- Upgrade to Enterprise; it is the only plan with any Trusted Advisor checks
- Downgrade to Basic, which includes round-the-clock engineer support
Answer: A
Why A is correct: Developer gives business-hours technical guidance and a limited Trusted Advisor subset. Moving to Business unlocks 24/7 phone/chat/email access to Cloud Support Engineers and the complete set of Trusted Advisor checks — exactly what they're missing.
Why the other options are wrong:
- B — Developer is business-hours only, so this is factually wrong.
- C — Enterprise is not the only plan with checks; Business already provides the full set at lower cost.
- D — Basic provides no engineer technical support at all and only a limited check set.
Common trap: Developer ≠ 24/7. The first plan with both 24/7 engineer access and full Trusted Advisor is Business.
Q20 An EC2 instance and an S3 bucket are in the same Region. Data transferred between certain AWS services within the same Region is often free or low-cost, but a charge most reliably appears in which scenario?
- Data uploaded from the internet into the S3 bucket
- Data written from the EC2 instance to its attached EBS volume
- An IAM user signing in to the console
- Data served from the application out to internet users
Answer: D
Why D is correct: Data transfer OUT to the internet (serving users) is the classic recurring transfer charge once you exceed the free allowance. It's the third fundamental cost driver and the one to watch.
Why the other options are wrong:
- A — Data transferred into AWS from the internet is generally free.
- B — Writing to an attached EBS volume isn't a data-transfer-out charge (you pay for EBS storage, not the write as transfer-out).
- C — IAM sign-ins are free and unrelated to data transfer.
Common trap: The exam keeps reinforcing that the expensive, recurring transfer is OUT to the internet — not inbound and not intra-service writes.
Q21 A company wants AWS Budgets to not just alert but automatically take an action (such as applying a restrictive IAM policy) when a budget threshold is exceeded. What is this capability called?
- Cost Explorer forecasting
- Trusted Advisor service limits
- Cost & Usage Report automation
- AWS Budgets actions
Answer: D
Why D is correct: Budgets actions let you configure an automated response — such as applying an IAM/SCP policy or stopping instances — when a budget threshold is crossed, going beyond a simple notification.
Why the other options are wrong:
- A — Cost Explorer forecasting predicts spend trends but takes no automated action.
- B — Trusted Advisor checks service limits and best practices; it doesn't enforce budget actions.
- C — The CUR delivers detailed billing data; it has no automatic enforcement action.
Common trap: Plain Budgets = alerts; Budgets actions = automated enforcement. Don't confuse alerting with acting.
Q22 A manager asks for the difference between AWS Cost Explorer and the Cost & Usage Report. Which statement is the most accurate?
- Cost Explorer offers interactive visual analysis and forecasting in the console; the CUR provides the most detailed line-item data for export and deep analysis
- Both produce identical raw line-item files delivered to S3
- Cost Explorer estimates future architectures before launch; the CUR alerts on thresholds
- The CUR is a visual dashboard and Cost Explorer is a raw exportable file
Answer: A
Why A is correct: Cost Explorer is the interactive, visual analysis-and-forecasting tool inside the console; the CUR is the most granular, comprehensive billing dataset you export (to S3) for custom or large-scale analysis. They complement each other.
Why the other options are wrong:
- B — Only the CUR delivers raw line-item files to S3; Cost Explorer is a visual tool.
- C — Estimating future architectures is the Pricing Calculator, and threshold alerts are Budgets — neither describes these two.
- D — This reverses the two tools.
Common trap: Cost Explorer = visual/interactive analysis; CUR = the deepest raw data export. Keep their roles straight.
Q23 A new EC2 t-class instance under the 12-month free tier has been running continuously, and the customer now sees charges in month 13. Why?
- The 12-month free tier expired, so usage now bills at standard On-Demand rates
- AWS billed retroactively for all 12 prior months
- The instance was in an always-free category and should never be charged
- Charges appear only because they lack a paid Support plan
Answer: A
Why A is correct: The small EC2 allowance is part of the 12-month free tier, which starts at account creation and expires after one year. After that, the running instance bills at normal On-Demand rates — hence month-13 charges.
Why the other options are wrong:
- B — AWS does not retroactively bill the free months; only post-expiry usage is charged.
- C — EC2's free allowance is 12-month, not always-free, so it does eventually bill.
- D — Support plan status doesn't trigger EC2 usage charges.
Common trap: The EC2/RDS small allowances are 12-month, not always-free. Forgetting to stop them after a year is a classic surprise-bill cause.
Q24 A company needs to forecast next month's likely spend based on current usage trends so they can plan a budget. Which combination of tools best supports forecasting and then alerting on that forecast?
- Pricing Calculator to forecast and Trusted Advisor to alert
- Cost Explorer to forecast trends and AWS Budgets to alert when forecasted spend crosses a threshold
- The Billing Dashboard to forecast and the CUR to alert
- Trusted Advisor to forecast and the Pricing Calculator to alert
Answer: B
Why B is correct: Cost Explorer can forecast future spend based on historical usage trends, and AWS Budgets can alert on forecasted (not just actual) spend crossing a threshold. Together they cover trend-based forecasting plus proactive alerting.
Why the other options are wrong:
- A — The Pricing Calculator estimates pre-build costs, not usage-trend forecasts, and Trusted Advisor doesn't send budget alerts.
- C — The Billing Dashboard summarizes spend and the CUR exports data; neither forecasts or alerts.
- D — Trusted Advisor doesn't forecast and the Calculator doesn't alert.
Common trap: "Forecast from current usage" is Cost Explorer's forecasting — distinct from the Pricing Calculator's pre-build estimates. Budgets can alert on forecasts, not just actuals.