CLF-C02 domain - 12% of the exam

Billing, Pricing, and Support

Billing, Pricing, and Support is 12% of the CLF-C02 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

38
Practice questions
4
Objectives
27
Easy
11
Medium

Where people go wrong

  • Placing a support feature at the wrong tier

    The wrong answers hand a feature to the wrong plan. Enterprise Support is offered for the full set of Trusted Advisor checks and for Support API access, although both start at Business Support, the lowest tier to include them. The reverse slip gives Business Support a designated Technical Account Manager or the Concierge Support Team, which begin at Enterprise. Basic and Developer Support offer only a limited subset of checks and no Support API.

    See it in a sample question
  • Using a cost tool in the wrong time direction

    The wrong answers swap tools that look at different moments. Cost Explorer and the Cost and Usage Report describe spend already incurred, so neither can estimate a workload when nothing is provisioned. AWS Pricing Calculator models planned services before launch but has no view of real charges. AWS Budgets sets a limit and alerts on actual or forecast spend, which Cost Explorer charts do not do.

    See it in a sample question
  • Crediting the wrong feature with combining or splitting a bill

    The wrong answers give one billing job to a neighbouring feature. Cost allocation tags, Cost Explorer and AWS Budgets are offered for a single combined invoice or pooled volume pricing, yet only consolidated billing in AWS Organizations merges member accounts and aggregates their usage. In the other direction, consolidated billing is offered for splitting one shared account by department or project, which needs cost allocation tags. Service control policies govern permissions, not pricing.

    See it in a sample question
  • Tying a committed discount to one instance type

    The wrong answers offer Standard Reserved Instances for a commitment that has to follow a changing workload. A Reserved Instance attaches its discount to a specific instance type, so changing families leaves part of the commitment unused, and it does not reach AWS Fargate or AWS Lambda. Compute Savings Plans commit to an hourly spend instead, so the discount applies automatically across instance families, sizes, Fargate and Lambda.

    See it in a sample question
  • Matching Spot to steady or watched workloads

    The wrong answers pick Spot Instances for work that cannot be interrupted: an always-on production site, an always-on production database, or a trial the team must watch closely. Spot uses spare capacity that AWS can reclaim at short notice, so it fits only fault-tolerant jobs that checkpoint, retry or resume, such as batch rendering and stateless test runners. A steady baseline fits Reserved Instances or Savings Plans, and a short uncertain trial fits On-Demand.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleBilling, Pricing, and Supporteasy

A growing company is subscribing to AWS Business Support for its first production workload and wants to confirm what that plan includes. Which two capabilities are part of AWS Business Support? (Select TWO.)

  • ARound-the-clock access to AWS Support engineers by phone, web and chat for production issues Correct
  • BA designated Technical Account Manager assigned to proactively guide the account's architecture
  • CAccess to the full set of AWS Trusted Advisor checks across cost, security and fault tolerance Correct
  • DA dedicated AWS Concierge Support Team to handle billing and account enquiries for the customer
  • EAWS Incident Detection and Response monitoring included for the customer's workloads at no extra cost
Recognise that AWS Business Support adds 24/7 phone, web and chat access plus the full set of AWS Trusted Advisor checks above the lower tiers. AWS Support plans add capabilities as the tier rises; Business Support is the level that first grants 24/7 engineer access by phone, web and chat together with all AWS Trusted Advisor checks, while a designated Technical Account Manager and the Concierge Support Team stay reserved for Enterprise Support.

Why A is correct: Business Support adds 24/7 access to cloud support engineers by phone, web and chat, which is the core upgrade over Developer.

Why B is wrong: A designated Technical Account Manager is tempting but belongs to Enterprise Support, not to the Business Support plan.

Why C is correct: Business Support unlocks every AWS Trusted Advisor check, whereas Basic and Developer expose only a limited subset of them.

Why D is wrong: The Concierge Support Team sounds plausible but is an Enterprise Support benefit and is not included with Business Support.

Why E is wrong: Incident Detection and Response is a separate paid offering tied to higher tiers, so it is not bundled into Business Support.

Free sampleBilling, Pricing, and Supporteasy

A team is planning a new workload before launching anything and wants a written estimate of the monthly AWS bill so it can be shared with finance for budget approval. No resources have been created yet. Which AWS tool is designed to produce this kind of upfront cost estimate?

  • AAWS Pricing Calculator, modelling the planned services and configuration to produce a shareable monthly cost estimate Correct
  • BAWS Cost Explorer, reviewing graphs of past usage and spend so the team can read the expected monthly figure
  • CAWS Budgets, setting a monthly spend limit that becomes the agreed estimate finance signs off before launch
  • DAWS Trusted Advisor, scanning the live account for savings so the resulting figure forms the monthly estimate
The AWS Pricing Calculator estimates the cost of a planned workload before any resources are deployed. The AWS Pricing Calculator models the price of services and configurations you intend to use and produces a shareable estimate, so a team can forecast a future bill before creating any resources.

Why A is correct: The AWS Pricing Calculator lets you model services and settings before deploying and exports a shareable estimate, which is exactly what finance needs for budget approval.

Why B is wrong: Cost Explorer analyses costs that have already been incurred, so it has no data to show for a workload that has not been launched and cannot produce a pre-launch estimate.

Why C is wrong: AWS Budgets tracks and alerts on actual or forecast spend against a limit you set, but it does not model the price of a planned design, so it cannot generate the estimate itself.

Why D is wrong: Trusted Advisor inspects resources already running for cost and other recommendations, so with nothing deployed yet it cannot calculate the bill for a future workload.

Free sampleBilling, Pricing, and Supporteasy

A business wants its AWS bill broken down by department and project so each team can see what it spent, even though many teams share the same account. It needs to attach its own labels to resources to drive this breakdown. Which AWS feature makes this possible?

  • ACost allocation tags, which apply custom labels such as department or project so costs are grouped by those labels in billing reports Correct
  • BAWS Budgets, which sends an alert per team so each department can infer its own share of the monthly spending
  • CConsolidated billing, which produces a separate invoice for each department and project sharing the single account
  • DAWS Pricing Calculator, which labels the planned resources by department so the estimate is divided across each project
Cost allocation tags label resources so AWS billing reports can break down actual spend by category such as department or project. Cost allocation tags attach key-value labels to resources, and once activated AWS groups costs by those tags in billing reports, letting a shared account be split by department or project.

Why A is correct: Cost allocation tags let you attach key-value labels like department or project to resources, and billing reports then group costs by those tags for a clear per-team breakdown.

Why B is wrong: AWS Budgets alerts on spend against thresholds but does not categorise charges by custom labels, so it cannot itself split a shared bill by department or project.

Why C is wrong: Consolidated billing combines separate accounts into one invoice rather than splitting a single shared account's costs by team, so it does not give the per-project breakdown.

Why D is wrong: The Pricing Calculator only estimates the cost of a planned design before launch and cannot tag or report on the actual charges a shared account has already incurred.

Free sampleBilling, Pricing, and Supportmedium

A company commits to a steady amount of compute spend per hour but expects to keep changing its Amazon EC2 instance families and sizes as its applications evolve. It wants a discount that still applies automatically when those instance choices change. Which pricing model best meets this requirement?

  • AStandard Reserved Instances tied to a single instance type, giving a discount only while that exact type runs
  • BSpot Instances, relying on spare capacity so the discount continues to apply as the instance families change
  • CCompute Savings Plans, committing to an hourly spend so the discount follows changing instance families and sizes Correct
  • DOn-Demand Instances, paying the standard rate so the company can freely switch instance families and sizes
Compute Savings Plans give a flexible discount on committed hourly spend that follows changing instance families, sizes and regions. A Compute Savings Plan commits to a fixed hourly compute spend instead of a specific instance type, so the reduced rate keeps applying automatically even as the company shifts between instance families, sizes and regions.

Why A is wrong: Standard Reserved Instances attach the discount to a specific instance type, so changing families would leave the commitment partly unused as applications evolve.

Why B is wrong: Spot gives a discount on spare capacity but offers no committed-spend coverage and can be reclaimed, so it does not provide the flexible commitment described.

Why C is correct: Compute Savings Plans commit to a steady hourly spend rather than one instance type, so the discount keeps applying automatically as families, sizes and regions change.

Why D is wrong: On-Demand allows free switching but gives no discount at all, so it fails the goal of keeping a committed-spend saving as the instance mix changes.

Free sampleBilling, Pricing, and Supportmedium

A startup is testing a brand new feature on Amazon EC2 for a few weeks. The traffic is hard to predict and the team is not ready to commit to any long-term term or upfront payment. Which pricing model best suits this short, uncertain trial?

  • AReserved Instances with a three-year commitment, locking in a low rate before the feature trial begins
  • BOn-Demand Instances, paying the standard per-second rate with no commitment for the short trial period Correct
  • CSpot Instances, accepting that AWS may reclaim the capacity while the feature trial is still running
  • DA Compute Savings Plan with a one-year commitment to a fixed hourly spend during the feature trial
On-Demand Instances suit short, unpredictable workloads because they need no upfront payment or long-term commitment. On-Demand pricing bills per second at the standard rate with no commitment, so a team running a brief trial with uncertain traffic can start and stop freely without paying for capacity in advance.

Why A is wrong: A three-year commitment is wrong for a few weeks of uncertain testing, since the startup would pay for years of capacity it may not keep using.

Why B is correct: On-Demand charges the standard rate with no upfront payment or term, so it suits short, unpredictable trials where flexibility matters more than a discount.

Why C is wrong: Spot is cheap but can be reclaimed at short notice, which adds avoidable risk to an interactive trial that the small team needs to watch closely.

Why D is wrong: A Savings Plan still requires committing to a fixed hourly spend for a year, so it does not fit a team that wants no long-term commitment for a brief test.

Other domains in this exam

See also the CLF-C02 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Amazon Web Services. Original, blueprint-aligned practice material only.