Exampractice
Exam Preparation

Why Your Practice Score May Not Match Your Exam Score

Scored 85% on mocks but failed the real exam? The gap has identifiable causes — scaled scoring, unscored items, memorised pools and nerves — explained here.

Amara Okafor · 8 min read
Diagram of two score gauges showing a mock score higher than a real exam score, with arrows labelling five causes of the gap

Short answer: a practice score and a real exam score are two different measurements taken with two different instruments under two different conditions — so some gap is normal, and a large gap usually has one of five identifiable causes: your mock's percentage isn't comparable to a scaled score, some real questions don't count, you partly memorised your practice pool, the question styles differ, or exam-day conditions degraded your performance. None of these means your preparation was worthless; each one points to a specific correction.

This article diagnoses the gap. What score you should be aiming for on mocks is a separate question, answered in what is a good practice test score before the real exam, and the fixes for a stalled score live in the sibling improvement-plan article — here we stay on why the numbers diverge.

Cause 1: You compared a percentage to a scaled score

The most common confusion is arithmetic, not ability. Practice platforms typically report a raw percentage: 78% means you answered 78% of questions correctly. Real certification exams overwhelmingly report scaled scores: AWS scores from 100 to 1,000 with Cloud Practitioner passing at 700 and Solutions Architect – Associate at 720; CompTIA scores from 100 to 900 with Security+ (SY0-701) passing at 750 and the A+ Core exams (220-1201/220-1202) at 675 and 700.

A scaled score is not a percentage of questions correct. AWS's exam guides state the purpose explicitly: scaling equates different exam forms of slightly different difficulty, so a candidate who draws a harder form isn't disadvantaged. "750 out of 900" is not 83%, and "700 out of 1,000" is not 70%. So when your 82% mock became a 705 real score, no simple subtraction connects those numbers — they live on different scales, and the conversion between raw correctness and scaled score is not published.

What this means for you: treat mock percentages as a trend line and a domain-coverage signal, not as a predicted exam score. Consistency across several fresh mocks predicts better than any single number — the readiness side of that argument is in how to know when your practice scores are good enough.

Cause 2: Some of your real exam didn't count

Several major programmes seed their exams with unscored pilot questions — new items being trialled before they count. AWS is explicit: on Cloud Practitioner and Solutions Architect – Associate, only 50 of the 65 questions are scored; 15 are unscored, and you are not told which. Other programmes handle pilots differently, so check your provider's exam guide.

Unscored items are a documented reason your felt performance and your actual score diverge. Perhaps you struggled with four bizarre questions that turned out to be unscored pilots — your score was better than the sitting felt. Or the reverse: questions you breezed through didn't count, and the scored set concentrated on your weaker domains. Your practice platform, by contrast, scores everything, so mock arithmetic and real arithmetic simply aren't the same calculation.

A related mechanic worth knowing: AWS scores unanswered questions as incorrect and applies no guessing penalty, and passes candidates on the overall (compensatory) score rather than per domain. If you left blanks on the real exam but never on relaxed mocks, that alone opens a gap.

Cause 3: You partly memorised your practice pool

This is the quietest and most damaging cause. Run the same question bank three or four times and your score rises — but increasingly it measures recognition of those specific items, not command of the objectives they sample. The real exam draws different items from the same objectives, and the recognition advantage evaporates.

Learning science explains why practice testing works and where this trap hides. Roediger and Karpicke's 2006 research on test-enhanced learning showed retrieval practice beats restudying for long-term retention — but the benefit comes from retrieving knowledge, not from re-seeing familiar stems and remembering "the answer was C". Telltale signs you've crossed the line:

  • You answer familiar questions in seconds without reading all the options.
  • Your score on a repeated bank is 15+ points higher than on any fresh set.
  • You can pick the right answer but couldn't explain why the others are wrong.

The escape techniques — explaining every distractor, rotating fresh material, testing from objectives — get full treatment in how to avoid memorising practice test answers. For gap-diagnosis purposes, run one honest experiment: take a full-length set of questions you have never seen. That score, not your fourth pass at a familiar bank, is your real baseline. ExamPractice's free sample questions are one quick way to get eyes on unfamiliar items for your exam before committing to a fuller set.

Cause 4: The question styles weren't the same

Even honest, fresh practice material can differ in kind from the live exam:

  • Performance-based and interactive items. CompTIA's A+ and Security+ exams include performance-based questions alongside multiple choice; Microsoft notes that AZ-900 "may have interactive components." If your practice diet was pure multiple choice, a chunk of the real exam exercised skills you never rehearsed in that format.
  • Depth of scenario. Live exams at associate level and above tend to wrap objectives in situational judgement — "a company needs X under constraint Y" — where weaker practice material asks for bare definitions. Both can cover the same objective; only one predicts the exam.
  • Blueprint weighting. Real exams follow a published domain weighting. A practice bank that over-represents your strong domains inflates your mock average. Compare any mock's domain mix against the official exam objectives before trusting its number.
  • Deliberate difficulty tuning. Some prep materials run easier than the exam (to keep customers cheerful), some deliberately harder. Either way the percentage shifts for reasons unrelated to your knowledge. If your material sits at the too-gentle end, how to prepare when practice tests feel too easy covers the fix.

Cause 5: Exam day itself taxed you

The last cluster of causes has nothing to do with the questions.

Test anxiety and stakes. A mock costs nothing; the real sitting costs money, time and pride. Under genuine stakes, working memory narrows — candidates reread stems, second-guess sound answers, and burn time. If your mocks were relaxed, untimed or pausable, you never rehearsed performing under that load.

Unfamiliar procedure. Room scans, ID checks, a proctor watching via webcam, a cleared desk, no notes, a clock you can't stop — each novelty costs a little attention. Online proctoring adds its own texture: Pearson VUE's OnVUE requires a system test, a private distraction-free space and consent to continuous monitoring by human proctors and AI tools.

Fatigue and pacing. Ninety continuous minutes (the allotment for Security+ and Cloud Practitioner alike) is a physical event. Fragmented practice sessions never trained it.

The remedy for this whole cluster is a strict full dress rehearsal, which is its own discipline — room setup, break rules, unbroken timing — detailed in how to simulate real exam conditions at home.

A worked example of a "mystery" fail

Consider a support technician who averaged 88% across five runs of one Security+ question bank, then scored below the 750 passing mark on SY0-701. Reconstructing it: two of his five runs were repeats (memorisation inflated the 88%), his bank was light on performance-based questions (style gap), he'd always practised with pauses (no fatigue training), and he assumed 750 meant "I need 83%" (scale confusion) so believed he had margin he never had. Four causes, one gap — and not one of them means he learned nothing. Each is separately fixable before a retake.

How to tell which cause applies to you

A quick decision framework:

  1. Did you repeat question pools? If yes, memorisation is suspect number one. Test with a fully fresh set.
  2. Was your mock score a raw percentage compared against a scaled pass mark? If yes, discard the comparison; watch trend and consistency instead.
  3. Did the real exam contain formats your practice lacked (performance-based, interactive, long scenarios)? If yes, it's a style gap — change material, not effort.
  4. Did the real sitting feel physically different — nerves, time pressure, fatigue, procedure? If yes, conditions were the gap; rehearse them.
  5. None of the above, and the gap is small? Then it may simply be normal measurement noise between two different instruments — including unscored pilot items you'll never see identified.

Frequently asked questions

Is the real exam actually harder than practice tests?

Sometimes, but "harder" often decomposes into the causes above: unfamiliar items versus a memorised pool, richer scenarios, formats you hadn't rehearsed, and pressure. Providers also equate forms via scaled scoring precisely because difficulty varies slightly between forms — so "hard" is partly adjusted for.

Can my practice score ever understate my real score?

Yes. Deliberately difficult practice material, a mock taken while fatigued, or a bank over-weighted toward your weak domains can all produce a mock score below what you achieve on the day. The gap runs both ways; the causes are the same list in mirror image.

Do providers publish how raw answers convert to scaled scores?

The conversion is not published for the exams covered here. AWS documents the scale (100–1,000), the passing marks and the purpose of scaling, but not the mapping — which is exactly why translating a mock percentage into a predicted scaled score is guesswork.

How big a gap is normal?

There's no published benchmark, and any specific number would be invented. The practical test is consistency: if several fresh, timed, full-length mocks cluster comfortably above passing-equivalent performance and the real result still falls far short, look hard at causes 3 through 5.

Closing the gap starts with naming it

A mismatch between mock and exam scores is information, not verdict. Separate the arithmetic illusions (scaling, pilot items) from the preparation gaps (memorised pools, style mismatch) and the performance gaps (nerves, fatigue, procedure), and each has a targeted fix — fresh material, better-matched formats, strict simulation. Diagnose first; only then change how you study.

Exam facts in this guide were checked against official certification-provider pages on . Fees, exam codes and policies change — confirm on the provider’s own site before you book.

Put it into practice

Test what you have just read

Reading about an exam only takes you so far. Work through practice questions for your certification and find the gaps before exam day does.

You may also like