How hard is the AWS Cloud Practitioner exam? Honestly, it sits at the entry level of AWS certification, and it is still easy to fail if you treat it as a vocabulary quiz. The CLF-C02 is a Foundational-level exam: 65 questions in 90 minutes, scored on a scale of 100 to 1,000, with 700 to pass. Nothing on it asks you to write code, design an architecture or troubleshoot a broken system. Those job tasks are explicitly out of scope in AWS's exam guide.
The difficulty lives somewhere else. Almost every question is a matching problem: a short business scenario, four or five AWS services that all sound reasonable, and one that fits the scenario's exact wording. People who fail usually knew what each service was. They just could not tell two similar ones apart under a clock. The rest of this post covers the scoring and the specific traps worth drilling.
How hard is the AWS Cloud Practitioner exam for beginners?
The AWS certification page pitches it at people new to cloud, including those without an IT background. The exam guide describes a target candidate with "up to 6 months of exposure" to the AWS Cloud, and the FAQ on the certification page adds that this exposure is not required. There are no prerequisites.
So "beginner-friendly" is fair. What beginners underestimate is the breadth. The largest of the four domains, Cloud Technology and Services, is 34% of scored content across eight task statements. That domain alone covers compute, databases, networking, storage, AI and analytics and a long tail of other services. Nothing in it is deep. There is just a lot of it, and the questions punish fuzzy recall. If you come from a finance, sales or project role, expect the service names to be the hard part. If you already work in IT, expect the hard part to be AWS's own vocabulary, which is precise in ways your day job may not be. A full walk through each domain is in the CLF-C02 domains explained.
How is the AWS Cloud Practitioner exam scored?
This is the part most people get wrong, so it is worth going slowly.
A scaled score, with 700 to pass. Your result is reported on a scale of 100 to 1,000. The minimum passing score is 700. That 700 is not "70% correct." AWS converts your raw performance onto the scale so that different versions of the exam are comparable, and it does not publish how many correct answers it takes to reach 700. Anyone quoting you a precise number of questions you can miss is guessing.
Pass/fail on the whole exam. The scoring is compensatory. In the exam guide's words, "you do not need to achieve a passing score in each section." A weak showing in Billing, Pricing, and Support can be carried by a strong one in Security and Compliance. There is no per-domain cut.
15 of the 65 questions do not count. The exam has 50 scored questions and 15 unscored ones. The unscored items "are not identified on the exam," so you cannot spot them and skip them. Treat every question as live.
Blanks are wrong answers. Guesses are free. "Unanswered questions are scored as incorrect; there is no penalty for guessing." That single sentence should shape your whole time plan: never leave anything blank.
For context, the bar rises with level. AWS's after-testing policy sets 700 for Foundational exams, 720 for Associate and 750 for Professional and Specialty. The Cloud Practitioner sits at the bottom of that ladder on purpose.
Do not expect to see that score the moment you finish. When results arrive, and what exam day looks like, is covered in our CLF-C02 cost and exam-day guide.
Multiple choice vs multiple response: which is harder?
The exam uses two question types, and they are not equally forgiving.
Multiple choice has one correct answer out of four options. The three wrong ones are written to be plausible: they are the answers someone who half-knows the material would pick. Eliminating two and choosing between the remaining pair is the normal rhythm.
Multiple response has two or more correct answers out of five or more options. This is where time and points leak. AWS's guide says nothing about partial credit, so plan as though you need every selection right. The book's advice works well here: read how many answers the stem asks for before you read the options, then judge each option on its own as true or false against the scenario. Do not hunt for "the best one" and then scramble for a second.
Where do people actually lose points?
Not on obscure services. On pairs and trios of services that sound alike, and on a few concepts AWS words very precisely. These are the ones the book's chapters flag repeatedly, all still squarely inside the current exam guide.
Elasticity vs high availability
Both sound like "resilience," and the exam writes distractors that swap them. Elasticity is matching resources to demand: handling a traffic spike, scaling back down at night. High availability is staying up when a component fails. A system can be one without the other. When a scenario says "withstand the failure of a component," it wants high availability. When it says "handle unpredictable traffic," it wants elasticity. If it says "test a new idea quickly," that is agility, a third word with its own trigger.
The shared responsibility line moves, but some things never move
The shared responsibility model is the most tested idea in Domain 2, and the trap is assuming the line sits in the same place for every service. It does not. On Amazon EC2, the operating system and everything above it is yours. On Amazon RDS, AWS patches the OS and the database engine, and you own the data and who can reach it. On AWS Lambda, nearly everything below your code is AWS's.
The edge case that catches people: managed does not mean hands-off. Even on Lambda, the customer owns the data, the code and the permissions on the function's IAM role. When a question mentions customer data, IAM permissions or client-side encryption, the answer is the customer, whatever the service.
GuardDuty, Inspector and Macie
These three sound interchangeable and are not. Amazon GuardDuty watches behavior and flags suspicious activity. Amazon Inspector looks for known software vulnerabilities in workloads. Amazon Macie finds sensitive data, such as personal information, sitting in Amazon S3. Read the scenario for its angle: is something acting strangely, is something unpatched, or is something exposed?
Instance store vs Amazon EBS
Instance store is temporary block storage physically attached to the host, and its data is lost when the instance stops. EBS volumes persist. It is a one-line fact, and the book's exam-day chapter calls it one of the most frequently missed.
Pricing models: match the shape of the workload
Pricing questions give way to a simple test. Steady, predictable usage points to Reserved Instances or Savings Plans. Fault-tolerant work that can be interrupted points to Spot Instances. Short-lived or unpredictable usage points to On-Demand. A mention of software licenses tied to physical cores or sockets usually means a Dedicated Host. The trap is picking the cheapest-sounding option instead of the one the workload's shape calls for.
Budgets, Cost Explorer and Pricing Calculator
Read the tense of the question. Estimating a cost before anything is built is AWS Pricing Calculator. Being alerted when spend crosses a threshold is AWS Budgets. Analyzing what you have already spent is AWS Cost Explorer.
IAM roles vs access keys
When an application on EC2 or Lambda needs to call another AWS service, the right answer is an IAM role attached to the compute resource. The distractor is creating an IAM user and putting its access keys in the application. Pair that with least privilege and you have the default answer to most "most secure way to grant permissions" questions.
One caution on material: AWS revised the CLF-C02 exam guide during 2026 without changing the format or scoring, but some example services and Support plan names moved. Material written against the 2023 guide, including our own book's Support plans chapter, still uses some of the older names, so check names against the live guide and spend the saved time on the pairs above. The domains post lists what changed.
How much time do you get per question?
Ninety minutes across 65 questions works out to about 83 seconds each. For most CLF-C02 items that is plenty, because the scenarios are short and there is nothing to calculate. Time pressure shows up only when you stall.
A plan that works:
-
Answer what you know and move on.
-
On anything that stumps you, pick your best guess, flag it, and keep going. A flagged guess still scores if the clock runs out. A blank does not.
-
Aim to have seen all 65 questions with about 15 minutes left, then revisit the flags.
-
Change an answer only when you can point to a word you misread. "This one feels safer" is not a reason.
Non-native English speakers taking the exam in English can request a 30-minute extension. The details of requesting it, along with booking and fees, are in our CLF-C02 cost and logistics post.
So how should you calibrate your prep?
Spend time in proportion to the weights: Domain 3 first, then Domain 2, and resist the urge to over-polish Domain 4 because it feels manageable. Learn each service as a one-line trigger rather than a feature list, then test yourself on scenarios, because that is the format the exam uses.
Practice questions that explain why each wrong option is wrong are worth more than a higher volume of unexplained ones, because the wrong options are where the lookalike services live. Our AWS Certified Cloud Practitioner CLF-C02 Study Guide is built around that idea, with a block of explained questions for each task statement. If you want a sense of how those questions read, the CLF-C02 practice questions walkthrough works through five of them, and the CLF-C02 study plan turns the domain weights into a schedule.
If you are still deciding whether the certification is for you at all, start with what the AWS Cloud Practitioner certification is.
FAQ
What score do you need to pass the AWS Cloud Practitioner exam?
You need a scaled score of 700 on a scale of 100 to 1,000. It is not a percentage, and AWS does not publish how many correct answers that takes. The exam is pass/fail overall, so you do not need to pass each domain separately.
Is there a penalty for guessing on the CLF-C02?
No. AWS's exam guide says unanswered questions are scored as incorrect and there is no penalty for guessing. Answer every question, even if you have to guess and flag it for later.
Do all 65 questions count toward my score?
No. Fifty questions are scored and 15 are unscored. The unscored ones are not identified, so you have to treat every question as if it counts.
Which part of the Cloud Practitioner exam do people find hardest?
Usually the lookalike services: pairs such as GuardDuty and Inspector, or Budgets and Cost Explorer, where both options are real and only one fits the scenario's wording. Multiple-response questions are the other common leak, because you should plan on needing every selection right.
Can I fail one domain and still pass the Cloud Practitioner exam?
Yes. The scoring is compensatory, so strong performance in one domain can make up for weaker performance in another. What matters is the overall scaled score reaching 700.
Want a plain-English way to prepare? The AWS Certified Cloud Practitioner CLF-C02 Study Guide has plain-English chapters across the four domains and 210 practice questions with explained answers, mapped to all 19 CLF-C02 task statements.
Simply Certified is an independent publisher. AWS, Amazon Web Services and AWS Certified Cloud Practitioner are trademarks of Amazon.com, Inc. or its affiliates. Our books are independent study material and are not affiliated with, endorsed by, or sponsored by Amazon Web Services, Inc. or Amazon.com, Inc.