AWS Cloud Practitioner practice questions: what a good one looks like
On this page
Short answer
A good CLF-C02 question makes you choose between services that sound alike — S3 or EBS, SQS or SNS, GuardDuty or Inspector — and then tells you why each wrong option was wrong in that scenario.
A bad one asks you to recall a definition or a number. The real exam rarely does, and a bank full of them will leave you confident and unprepared.
What the exam is actually testing
Cloud Practitioner has a reputation for being a vocabulary test. It is not, quite. Most questions describe a small situation and ask which service fits — which means the skill being measured is drawing boundaries between things that overlap.
You can know what Amazon EFS does and still miss a question about it, because the question was really asking how it differs from EBS. That gap is where most of the points are, and it is invisible if you study by reading definitions.
| A weak question asks | A strong question asks |
|---|---|
| What does Amazon S3 stand for? | Several instances across two Availability Zones need to read and write the same files at once. Which storage service fits? |
| Which service is a NoSQL database? | An application needs single-digit millisecond lookups, has no fixed schema, and unpredictable traffic. Which database service fits? |
| What is the default EBS volume size? | An instance is stopped. What happens to data on its instance store volume, and why? |
The left column is quicker to write, which is why cheap question banks are full of it.
Four things to check before you trust a question bank
- Does every wrong option have an explanation? Being told the answer is B teaches you almost nothing. Being told why C fails in this particular scenario is the part that transfers to the next question. This is the single most reliable quality signal.
- Does each question cite AWS documentation? A link to the official docs means somebody had the page open while writing. It is also your evidence that the question was written from public material rather than copied from an exam.
- Is it mapped to the exam objectives? CLF-C02 publishes numbered task statements. A bank that tracks them can tell you which objective you are weak on; one that does not can only give you a percentage.
- Does the spread match the published weights? See the next section — this one is quietly important and almost never checked.
Skip anything advertising “real exam questions”
Sites selling dumps or “actual CLF-C02 questions” are distributing material obtained in breach of the agreement every candidate signs. AWS pursues them, and the risk of using them lands on you. Every legitimate bank is written from the published exam guide.
Practice by domain, and check the weights
CLF-C02 publishes how much of the exam each domain is worth:
| Domain | Share of the exam |
|---|---|
| 1 — Cloud Concepts | 24% |
| 2 — Security and Compliance | 30% |
| 3 — Cloud Technology and Services | 34% |
| 4 — Billing, Pricing, and Support | 12% |
Two consequences most people miss. First, security and technology together are nearly two thirds of the exam — if your study time is split evenly across four domains, a third of it is going into the smallest two.
Second, a question bank whose spread does not match these weights will give you a misleading score. A bank that is 60% services questions tells you how good you are at services, not how close you are to passing.
How to use a domain breakdown properly
Work in topic-sized sets while your gaps are still wide — one domain at a time, twenty or thirty questions, then go and fix what came up. That is far more efficient than full-length tests early on, which mostly produce a long undifferentiated list of mistakes and a discouraging number.
Save the full timed runs for the last stretch. We wrote separately about when a full CLF-C02 practice exam is worth taking and how to read the result.
The service pairs worth drilling deliberately
If you only have limited time, spend it on the boundaries rather than on breadth. These pairs account for a large share of the questions people get wrong:
- S3 vs EBS vs EFS — object, block, and shared file storage; and which of them one instance versus many can use
- SQS vs SNS — one consumer per message versus fan-out to every subscriber
- CloudWatch vs CloudTrail — what is happening now versus who did what
- GuardDuty vs Inspector vs Macie — suspicious behavior, software vulnerabilities, sensitive data
- Security groups vs network ACLs — stateful at the resource, stateless at the subnet
- Reserved Instances vs Savings Plans vs Spot — commit to a configuration, commit to an amount, or accept interruption
Notice that every one of those is a distinction, not a definition. That is not a coincidence — it is what the exam is made of.
Knowing when you are ready
The signal is not a percentage. It is whether unseen questions still surprise you. If new questions regularly reveal something you did not know existed, keep covering ground. If your mistakes cluster in two or three specific areas, fix those. If unseen questions are consistently fine across all four domains, book the exam.
Keep a reserve of questions you have never touched for the final week. Once you have worked through everything twice you are partly remembering answers rather than working them out — which feels exactly like progress and is not.
What we are building
We are writing a Cloud Practitioner bank to the standard described above: every wrong option carries its own explanation, every question cites the AWS documentation it came from, and every question is mapped to a numbered exam objective so a weak area has a name rather than a number.
Straight with you: it is written, and the review has not started yet. You can practice with it today, free — and you should know what that means: every question in it is a draft written against the published objectives, and none of them has been reviewed yet — read by a person and checked against the AWS documentation it cites. Today that reviewer is our founder, and that review is still ahead. The form below is how to hear about it, and that is the entire extent of what we will send you.
The one-line version
Judge a question bank on the explanations for the answers you did not pick, check its spread against the published domain weights, and drill the pairs of services that sound alike — that is where the exam actually lives.
Practice AWS Cloud Practitioner free
A short placement test puts an estimated score on the real exam scale, then practice goes after the topics you miss. No account needed to start.
Start practicing freeNot ready to start yet?
Leave an email and we will send the occasional AWS Cloud Practitioner study guide. Nothing else.
Keep reading
- Is AWS Cloud Practitioner worth it? An honest answer, by situationWorth it for some people and a waste of $100 for others — and the difference is not how badly you want a cloud job. Four situations, answered separately.
- Cloud Practitioner vs Solutions Architect Associate: which one to sitCloud Practitioner is not a prerequisite for Solutions Architect Associate, and for people already in IT it is often a detour. How the two exams differ, and the self-test that answers it.
- How long to study for AWS Cloud Practitioner? Plan in hours, not weeksTwo to six weeks for most people, but the range hides everything useful. What your starting point actually changes, how to split the hours, and the signal that says you are ready to book.