AWS Cloud Practitioner Passing Score Explained

The short answer: 700 out of 1000

The passing score for the AWS Certified Cloud Practitioner (CLF-C02) exam is 700 out of a possible 1000. AWS reports your result on a scaled range of 100 to 1000, and 700 is the line between pass and fail — regardless of which version of the exam you take or how difficult that particular set of questions happens to be.

That single number raises more questions than it answers, though. Is 700 a high bar? Is it 70% of the questions correct? Why does AWS use a scale of 100–1000 instead of just reporting a percentage? This article walks through what's actually happening behind that number.

How scaled scoring actually works

AWS does not simply count your correct answers and convert them to a percentage. Instead, CLF-C02 uses what AWS calls a scaled scoring model. The exact internal weighting AWS applies to each question is not publicly published, but the structure AWS does disclose is consistent: your raw performance is converted onto a 100–1000 scale, with 700 representing the minimum passing performance.

This approach is standard across professional certification testing, not unique to AWS. It exists to keep results comparable across different exam forms. Because AWS draws questions from a large pool and rotates them between candidates, no two people necessarily see an identical set of 65 questions. Scaled scoring adjusts for small differences in difficulty between forms, so a 750 earned on one exam attempt represents roughly the same level of mastery as a 750 earned on a different form.

Why it isn't just a percentage

If scaled scoring purely tracked percentage correct, 700/1000 would imply "get 70% of questions right." That's a reasonable rule of thumb, but it isn't precisely how the math works, because not every question is guaranteed to carry identical statistical weight in AWS's model, and the exact published methodology stops short of a simple linear formula. Treat 700 as the pass/fail threshold on AWS's own scale — not as a literal stand-in for "70% of questions correct" — and you'll have a more accurate mental model.

Why only 50 of the 65 questions count

Here's a detail that surprises a lot of first-time candidates: the CLF-C02 exam has 65 total questions, but only 50 of them are scored. The remaining 15 are unscored — AWS calls these "pretest" questions. They're being trialed for potential use on future versions of the exam, and your answers to them don't count toward your result at all.

The catch: there's no way to tell scored questions apart from unscored ones during the exam. They look and feel identical, and they're mixed in throughout your 90-minute session. AWS does this deliberately, because if candidates could identify and skip the unscored items, those questions would stop providing useful difficulty data for future exams.

The practical takeaway is simple — treat every one of the 65 questions as if it counts, because functionally, you have no way to know which 15 don't.

How domain weighting affects your score

CLF-C02 questions aren't spread evenly across topics. The official exam guide defines four domains, each with a fixed percentage of the exam:

Security and Compliance and Cloud Technology and Services together make up 64% of the exam — nearly two-thirds. A candidate who is strong in Billing but weak in Security is going to feel that imbalance much more than one who has the reverse problem, simply because Security carries two and a half times the weight of Billing. When you're studying, allocate your time roughly in proportion to these percentages rather than spreading effort evenly across all four domains.

What counts as a "good" score

Technically, 700 is a passing score and 699 is not — AWS doesn't grade on a curve at the individual level. But in practice, candidates who walk in scoring right at 700 on their final practice attempts are cutting it closer than is comfortable, because:

• Real exam-day nerves typically cost a few percentage points compared to relaxed practice conditions.
• The specific question set you draw on exam day may skew slightly harder than your practice average.
• A single careless misread on a multiple-response question (where partial credit doesn't exist) can swing your result more than expected.

A more realistic target is to consistently score 750–800 or higher on full-length, timed practice exams before you book the real thing. That buffer absorbs day-of variability without requiring you to be flawless.

Using practice tests to gauge readiness

Practice test scores from any third-party provider — including this site — are informal estimates, not predictions of your actual AWS result. No outside question bank has access to AWS's real scaled-scoring algorithm or its live item-difficulty statistics, so any practice score is, at best, a directional signal.

That said, directional signal is still useful. Two things to watch for in your own practice data:

1. Consistency above 750 across multiple full 65-question timed attempts — one good run can be luck; five good runs in a row is a real signal.
2. No domain dragging significantly below your overall average — a single weak domain, especially Security and Compliance at 30% of the exam, can pull your real result down even if your overall practice average looks fine.

Review every question you get wrong, including the explanation — understanding why an answer is correct (and why the others are wrong) does more for retention than re-taking the same test repeatedly.

Key takeaways

• 700/1000 is the passing score, on a scaled range of 100–1000 — not a literal raw percentage.
• 65 questions appear on the exam; only 50 are scored, and you can't tell which 15 aren't.
• Domains are weighted unevenly — Security and Compliance (30%) and Cloud Technology and Services (34%) deserve the most study time.
• Aim for 750–800+ on practice tests, not exactly 700, to build in a margin for exam-day variability.
• Treat practice scores as directional estimates, not guarantees — consistency across multiple full attempts matters more than any single score.