Billing, Pricing and Support is the smallest of the four CLF-C02 domains at 12% of the exam — roughly six to eight of your 65 questions. It is also the domain candidates most often decide to skim, on the reasoning that 12% is not worth the evening. That is a bad trade, and here is why.
Every other domain asks you to reason. Security asks you to work out where the boundary between AWS’s job and yours falls in an unfamiliar scenario. Technology asks you to choose between services that all technically work. Billing mostly asks you to know things: which support plan answers the phone at 3am, which tool estimates a cost you have not incurred yet, what the Free Tier actually covers. The material is finite, it does not require architectural judgement, and it does not change much. Marks here are about as close to free as this exam gets — but only if you have done the reading.
The one distinction the exam keeps testing
Almost every cost-tool question in this domain is the same question wearing different clothes: which moment in the cost lifecycle are we in?
AWS gives you a different tool for each moment, and the tools do not overlap as much as their names suggest. Before you build anything, the Pricing Calculator estimates what a configuration will cost. Once money is actually being spent, Cost Explorer shows you where it went and forecasts where it is heading, while the Cost and Usage Report gives you the same story in exhaustive, line-item detail. When you want to be warned rather than informed, AWS Budgets watches a threshold you define and tells you when actual or forecast spend crosses it. And when you want the bill to be smaller for the same workload, you are in optimisation: Savings Plans and Reserved Instances for committed usage, Trusted Advisor for the idle and oversized resources you have forgotten about.
Read a question and find the moment. “Before we migrate” is planning. “Last month’s spend, broken down by team” is tracking. “Alert us at 80% of budget” is control. “Reduce what we pay for the same instances” is optimisation. Once the moment is identified, usually only one option survives.
Pricing models: what you are actually paying for
The EC2 purchasing options are the other reliable source of questions, and they sit on a single spectrum: how much certainty are you giving AWS, and what does AWS pay you for it?
On-Demand buys you complete freedom — start and stop whenever, no commitment — and you pay full list price for that freedom. Reserved Instances and Savings Plans are the opposite trade: you commit to a level of usage for one or three years and AWS discounts it substantially. Spot Instances are the cheapest of all, because you are buying capacity AWS has spare and agreeing that it can be taken back with two minutes’ notice. Dedicated Hosts are the outlier that trips people up: they are more expensive, not less, and you choose them for physical isolation or for licensing that is tied to a physical socket.
The exam rarely asks you to price these. It gives you a workload description — “steady and predictable”, “can be interrupted”, “must not share hardware for compliance reasons” — and expects you to map the description to the model. Learn the descriptions, not the discounts.
Support plans: learn the boundaries, not the brochure
There are five support plans — Basic, Developer, Business, Enterprise On-Ramp and Enterprise — and the exam tests the boundaries between them rather than their full feature lists. Three boundaries carry almost all the questions:
- Basic to Developer: Basic includes no technical support. Developer adds it, but by email, during business hours, for one contact.
- Developer to Business: Business is where 24/7 phone and chat appear, with unlimited contacts and a one-hour target for a production system down. If a question mentions round-the-clock human help, the answer is Business or above.
- Business to Enterprise: Enterprise adds a designated Technical Account Manager and a 15-minute target for business-critical systems down. Enterprise On-Ramp sits between them with a pool of TAMs and a 30-minute target.
A recurring trap: a question asks for the cheapest plan that meets a requirement, and lists two plans that both meet it. Enterprise satisfies almost every requirement in the exam — and is almost always the wrong answer, because Business got there for less money.
Three smaller topics round out the domain, and each has one fact the exam actually wants.
Consolidated billing through AWS Organizations does two things: one bill for many accounts, and — the part that gets tested — combined usage across those accounts, so the group reaches volume pricing tiers sooner than any single account would.
Cost allocation tags are how you answer “which department spent this?” inside a single account. The detail people miss: a tag does nothing for billing until you activate it as a cost allocation tag in the billing console.
The Free Tier is not one offer. It is three: always-free allowances within a limit, twelve-month offers for new accounts, and short-term trials of individual services. Any answer option that describes it as a single blanket trial is wrong for that reason alone.
What the On-Demand price does and does not include
A quieter source of questions, and one that quietly bridges into the security domain: what are you actually buying per hour?
The rate covers the compute capacity and everything AWS runs underneath it — the physical server, the power, the cooling, the building, the maintenance. That is the whole promise of not owning a data centre, expressed as a line on a bill.
What it does not cover catches people out. Outbound data transfer to the internet is billed separately beyond the free allowance — and note the asymmetry the exam likes: data in is generally free, data out is not. EBS volumes are billed separately from the instance, which is why a stopped instance can still cost money: the compute stops, the disk does not disappear. And patching the guest operating system is not a cost at all — it is your work, under the shared responsibility model. Any option offering it as something included in the EC2 price is testing whether you know which side of that line it falls on.
Trusted Advisor: four categories, one that pays
Trusted Advisor checks your account against AWS best practice in several categories — cost optimisation, security, fault tolerance, performance and service limits. All of them are real, which is exactly why questions here work: you are given a scenario and asked which category catches it.
The mapping is more literal than people expect. An idle or oversized instance is money burning, so it is cost optimisation. An open port or an exposed access key is security. Missing snapshots or no Multi-AZ is fault tolerance. Approaching a quota is service limits. If the scenario describes waste, the answer is cost optimisation — regardless of how technical the waste sounds.
One detail that shows up as a distractor: the checks available to you depend on your support plan. Basic and Developer get a limited core set; the full range arrives with Business and above. That is a neat example of how this domain interlocks — a Trusted Advisor question can quietly be a support-plan question.
How to use the questions below
Answer each one before you open the explanation, and when you are wrong, read past the correct letter to the paragraph underneath it. The distractors are where the learning is — each wrong option in these questions is wrong for a specific, nameable reason, and that is exactly the muscle the real exam tests. Getting a question right for the wrong reason feels identical to knowing it, right up until exam day.
Updated for CLF-C02 (July 2026). The sample questions above are our own work
in the style of the exam — not real exam items. The exam itself is set and marked
by the certification body.