Why most people review wrong
After finishing a practice session, most candidates check the score, scan through wrong answers, think "ah, I see," and move on. This is not review. This is score-checking with extra steps.
True review produces one of two outcomes: either you understand why you got it wrong and have updated your mental model accordingly, or you identify that you need to study a topic more deeply and do so. If review produces neither outcome, it was not useful.
The four reasons you get a question wrong
Understanding why you got a question wrong determines what to do next. There are four distinct causes:
1. You did not know the content. The topic was unfamiliar. You guessed or reasoned from adjacent knowledge and got it wrong. The fix: study the topic. Go to the relevant concept, read it properly, and come back to similar questions.
2. You knew the content but misread the question. The question asked about a specific condition (e.g., "which statement is NOT true?") or a specific context (e.g., "in a point-to-point OSPF network") that you missed. The fix: discipline yourself to read the full question before looking at answer choices. Underline or highlight negative qualifiers in your head.
3. You knew the content but fell for a trap. You understood the concept but chose an answer that sounded correct — a distractor that uses the right vocabulary in the wrong application. The fix: study the distractor. Why is that answer wrong? What would make it correct? Exam writers craft distractors around the most common misconceptions. Learning the distractor teaches you more than the correct answer alone.
4. You knew the content and got unlucky with wording. This happens with ambiguous questions in low-quality practice banks. If this is happening frequently, the practice bank may not be representative of the real exam. Switch sources.
What a proper review looks like
For every wrong answer:
- Read the question again, slowly. Did you misread anything?
- Read the correct answer and confirm you understand why it is correct — not just what it says, but why the concept applies in this context.
- Read every wrong answer. For each one, articulate specifically why it is wrong. "Because it said VLAN 10 instead of VLAN 1" is a specific reason. "Because it is not right" is not a reason.
- If you cannot explain why a wrong answer is wrong, add the concept to your study list. You do not fully understand the topic yet.
- For concept-gap questions (cause 1), find the relevant study resource and read it before your next session. Do not just drill more practice questions hoping the concept will become clearer — it will not.
Using weak-topic tracking effectively
If your practice platform tracks which topics you are getting wrong (Courseiva's practice mode does this), check the breakdown before each new session. Do not just do another random 20 questions. Spend the first half of your session on your three weakest topics and the second half on random mixed questions.
This approach means your weak areas get disproportionate attention. The goal is to move every topic from "consistently wrong" to "consistently right" — not to maintain a high average by scoring well on topics you already know.
The timing question
Some candidates review immediately after each question. Others review at the end of the session. Both have merit.
Immediate review: You review the answer while the question and your reasoning are still fresh. You can more accurately identify why you chose the wrong answer. Better for diagnosis.
End-of-session review: You work through all questions under timed conditions, simulating the real exam experience. Better for building exam stamina and time management.
A combined approach works well: take the first half of your study period with immediate review (learning mode), then switch to timed full sessions with end-of-session review (exam simulation mode) in the final weeks.
The week before the exam
Stop studying new content in the last seven days. Your brain cannot reliably absorb new topics under deadline pressure. Instead, run a full practice exam every day. Review wrong answers immediately. Revisit weak topics from your tracker.
If you are consistently scoring above 75% on realistic practice exams, you are ready. If you are below 70%, identify the two or three topics dragging you down and spend focused time on those — not more full practice exams.
Practise with tracking
Courseiva tracks your performance by topic and surfaces weak areas automatically. Use the CCNA practice test, Security+ practice questions, or AZ-104 practice test with detailed explanations to build your review habit before exam day.
See also: exam dumps vs practice tests for how to make sure the practice questions you are using are worth reviewing.
Frequently asked questions
How many wrong answers should I be reviewing per session? All of them, every time. There are no wrong answers you can safely ignore. A question you got wrong for the wrong reason (trap) is as important as one you got wrong for the right reason (knowledge gap).
What if I keep getting the same topic wrong despite reviewing it? The review is not deep enough. Stop trying to learn it through practice questions and go back to the source material — a textbook chapter, a topic guide, a video walkthrough. Practice questions test your understanding; they do not build it from scratch.
Should I redo questions I got wrong? After studying the underlying topic, yes. Redoing questions too soon (the same session or the next day) tends to produce false confidence from recognising the question rather than actually learning the concept. Space it out — redo similar questions a few days later after studying.
How do I know when I am ready for the real exam? When you consistently score 75% or above on full-length, timed, realistic practice exams — and when your weak topics in the tracker are no longer weak. Both conditions, not just one.
The Difference Between 'Almost Got It' and 'Fundamentally Wrong'
Not all wrong answers deserve the same response. Treating them identically is inefficient. Categorise each wrong answer before deciding how much time to spend on it:
Reading error — You misread the question or an answer choice. You knew the correct answer but selected the wrong one due to haste. Response: re-read questions more carefully next time, especially ones with "NOT," "EXCEPT," "MOST appropriate." No additional study needed on the concept.
Trap — You knew the material but the question exploited a specific misconception or distractor. Example: selecting "GRS" instead of "RA-GRS" when the question specified read access during a regional outage. You need to memorise the specific trick, not study the whole topic again. Add this exact distinction to your trap sheet.
Conceptual gap — You genuinely don't understand the underlying concept. You would get any question on this topic wrong. Response: stop, go back to the source material, build the concept from scratch. This deserves the most time.
Lucky guess — You selected the correct answer but for the wrong reason, or you had no idea and guessed. This is dangerous: your score looks fine but the knowledge isn't there. Response: treat these exactly like wrong answers. Review the concept as if you got it wrong.
The meta-skill is being honest with yourself about which category applies. Calling a conceptual gap a "reading error" to avoid revisiting the material is self-deception that shows up on exam day.
The Feynman Technique Applied to Wrong Answers
Richard Feynman's learning technique: if you truly understand something, you can explain it in plain language to someone who knows nothing about the subject. If you use the technical term itself in your explanation, you haven't explained it — you've restated it.
Apply this to wrong answers. After reviewing why the correct answer is right, close your notes and explain it out loud (or in writing) without using the technical term.
Example — managed identity question: "Why is managed identity the correct answer for 'accessing Azure resources without credentials'?"
Bad explanation (using the term): "Because managed identity doesn't require credential management."
Good explanation (without the term): "Because Azure manages the authentication entirely — the application asks a local endpoint for a temporary token, that endpoint knows who the application is because Azure assigned it an identity at the platform level, and Azure issues a signed token that proves the identity to whatever service the app wants to access. There's no password or key anywhere in this process."
If you can do this, you understand it. If you can't explain it without the jargon, the concept isn't solid yet and you'll lose marks on differently worded questions.
When to Do Wrong Answer Review — The Timing That Works Best
The timing of review matters as much as the review itself.
Immediately after a session (within 5 minutes): review every wrong answer while the question is still fresh. This is when you're most emotionally engaged (you just got it wrong, you want to know why) and when working memory still holds context about why you made the choice you did. Don't let wrong answers sit overnight before first review.
24 hours later: review the same wrong answers again from scratch — don't just re-read your notes from the previous review. Re-attempt to recall the correct answer and explanation. This is the first spaced interval and produces strong memory consolidation.
72 hours later: final review of answers that are still uncertain after 24 hours. Answers you got right on the 24-hour review can be retired from the active review pile. Answers you're still uncertain on stay in rotation until they're solid.
This three-touch approach — immediate, 24 hours, 72 hours — is more effective than reviewing all wrong answers once thoroughly. The retrieval practice of re-encountering the question without your notes builds durable memory.
Building Your Personal Exam Trap Sheet
A trap sheet is a one-page (maximum two-page) document of the specific wrong answers you personally keep falling for. Not a study guide — a list of your specific failure points.
Format example:
| Topic | What I keep getting wrong | The correct distinction |
|---|---|---|
| Storage replication | Choosing GRS when question says "read during outage" | GRS = failover first; RA-GRS = always readable |
| DHCP starvation | Saying "rogue DHCP server" for starvation | Starvation = pool exhaustion by fake MACs; rogue = unwanted DHCP responses |
| OSPF 2-Way state | Treating 2-Way between DROthers as a problem | 2-Way/DROther is the correct final state between non-DR/BDR routers |
The trap sheet is personal — your traps are different from other candidates' traps. Someone who has worked with Azure storage for two years won't confuse GRS and RA-GRS. Someone who has never configured OSPF will get the 2-Way state wrong repeatedly.
Review your trap sheet the morning of the exam. Not to learn new material — to prime the specific misconceptions you've already identified and corrected. This is the most targeted exam-day preparation you can do.
When Practice Test Scores Are Misleading
A 75% practice test average doesn't tell you whether you're ready. What matters more:
Domain distribution of wrong answers: 75% overall with 95% on "easy" conceptual domains and 45% on the specific technical domains the exam weights most heavily means you're not ready. Calculate your score per domain and compare to the exam's domain weightings.
Difficulty calibration: are your practice questions representative of actual exam difficulty? Free practice tests are often easier than the real exam. A 75% on an easy test bank might be 55% on the real exam. Use practice tests from sources with accurate difficulty calibration (Boson, official vendor practice exams, Pearson VUE practice tests).
Plateau recognition: if your score has been at 72–76% for the last 5 practice tests, you've plateaued. More practice tests without changing your approach won't break the plateau. Identify the domains where you're consistently losing marks and do targeted review of those domains specifically — not full practice tests.
Consistency vs average: a candidate who scores 70%, 68%, 74%, 71%, 72% is more consistently ready than a candidate who scores 85%, 55%, 80%, 60%, 75%. High variance means the knowledge is inconsistent and exam-day conditions (nerves, time pressure, unfamiliar question phrasing) will push you to the lower end of your range.
The readiness target isn't just "what's my average" — it's "what's my floor?" If your worst recent session was still above 70% on a well-calibrated test bank, you're more likely ready than a candidate whose average is 75% but whose floor is 58%.
Practice Question Sets
| Session | Questions | Estimated time | Link |
|---|---|---|---|
| Quick check | 10 | 10–12 min | Start → |
| Standard session | 20 | 20–25 min | Start → |
| Browse all certifications | — | — | View certifications → |
| Full practice test bank | — | — | View all practice tests → |