Practice review and closing gaps

Earlier this month Noor took her first full practice test, and lesson 9 described the reading errors it revealed. Her plan has two more full tests before March 2027, one in December and one in mid-February. Lorna wants her to know exactly what to do with each result, because a practice test is only as useful as the review that follows it. Many candidates take test after test, glance at the score and start another. They are measuring, not improving. This lesson describes a review method that turns each practice test into a short list of specific gaps, a plan to close them, and a better estimate of readiness. The numbers in the examples are invented for teaching, but they are typical of what Lorna has seen in cert club members.

What a practice test can and cannot tell you

A good practice test shows which topics and question types cause trouble and whether pacing holds up for a full hour. It cannot predict the exact scaled score on the real exam. Practice providers write their own questions, which differ in style and difficulty from CompTIA's, and they report results in their own way, often as a number correct out of the total. The real exam converts results onto a scale where 650 of 900 passes, using a method CompTIA does not publish. So treat practice results as signals: improvement from test to test, consistency across domains and the kinds of mistakes being made matter more than any single number.

Choose practice material carefully. Questions should be written for the FC0-U71 objectives, not the older FC0-U61 exam, and should come from reputable sources: CompTIA's own CertMaster products, established training publishers, or questions written by an instructor from the objectives. Avoid sites that claim to offer the real exam questions. Using leaked exam content breaks CompTIA's candidate agreement and can lead to a ban and loss of certifications, and those collections are often wrong anyway.

The error log

The core of the method is an error log. For every question answered wrongly, and for every question answered correctly by a guess, record four things: the domain and objective, what the correct answer was, why you chose wrongly, and what you will do about it. The "why" column uses a small set of categories. A knowledge gap means you did not know the fact or concept. A misread means you knew the material but misread the question, missing a keyword such as NOT or FIRST. A careless error means you knew the answer and read correctly but clicked the wrong option or rushed. A time error means you guessed because time was short. Each category has a different fix, which is why separating them matters.

Closing a knowledge gap properly

Closing a gap means more than rereading the right answer. Go back to the objective in the official document, reread the relevant lesson, and write a short explanation in your own words, as if teaching a colleague. Then test yourself on new questions about the same objective, ideally a day or two later. Explaining and then retrieving from memory are two of the most reliable learning techniques known: actively recalling information strengthens memory far more than reading it again, and spacing the practice over days works better than cramming it into one session.

Noor applies this to her weakest objective, database keys. She rereads COMP-111's lesson on databases, writes three sentences explaining primary and foreign keys with a library example, draws the patrons, items and loans tables from memory, and two days later answers ten new questions on keys. She gets nine right, and the one she missed was a misread. The gap is closed; the objective moves from "shaky" to "known" on her checklist.

Flash cards and spaced repetition

Many Tech+ facts are short and specific: port numbers she may meet in context, file system limits, Wi-Fi security modes, license types, malware names. These suit flash cards, either on paper or in a spaced-repetition app that shows each card again just before you are likely to forget it. Cards you answer easily appear less often; cards you miss appear again soon. Ten or fifteen minutes a day with cards is more effective than an hour once a week. Write cards in your own words, one fact per card, and include a short example where possible.

Confidence calibration

A useful extra column in the error log is confidence: before checking the answer, rate each response as sure, fairly sure or guess. After a few practice tests, compare confidence with results. Ideally, "sure" answers are almost always right and "guess" answers are right only sometimes. If many "sure" answers are wrong, overconfidence is a problem, and those topics need checking even though they feel comfortable. If many "guess" answers are right, you know more than you think, and the fix is trust and pace rather than more study. Calibration also helps on exam day, when knowing which answers deserve a second look makes the review time more productive.

Judging readiness

No practice score guarantees a pass, but a few signals together suggest readiness. Scores on reputable practice tests have improved and are consistently comfortable rather than borderline. No domain is far weaker than the others. Most misses are misreads or occasional careless errors rather than knowledge gaps. Pacing checkpoints are met with time to spare. The objectives checklist is marked known for nearly every line. If several of these are missing a week or two before the exam, it may be wiser to reschedule than to sit an exam that the evidence says is not ready. Pearson VUE allows rescheduling under its own policy and deadlines, which should be checked well in advance; a lost attempt costs the full price.

One more caution applies to practice material: memorizing the answers to a particular practice set is not the same as learning the objectives. If a practice test is retaken and the score jumps because the questions are familiar, the result says nothing new about readiness. Fresh questions on the same objectives are the real measure, which is why Noor's plan uses a different source for each full test.

A week of gap closing

Turning an error log into action works best as a short weekly plan. Lorna helps Noor draft the week after her first test, built around the categories in her log. Each weekday has a focused block of about forty minutes on one weak objective, a short card review and a small set of mixed questions using the reading routine. The weekend has one longer session. The plan is deliberately modest, because a plan that fits around real shifts is one that actually happens.

Reviewing correct answers too

It is tempting to look only at wrong answers, but correct answers hold information as well. A correct answer reached by luck is a gap waiting to appear on the exam, which is why guesses go in the log. A correct answer that took three minutes is a pacing problem in disguise. And a correct answer reached by eliminating three options, without being able to say why the key is right, shows partial understanding that may fail on a differently worded question. Lorna suggests a quick pass through every question after a practice test, right or wrong, asking one thing: could I explain to someone else why the right answer is right and why each wrong option is wrong? Where the answer is no, the objective goes back on the study list.

If the real exam does not go to plan

The same method applies to a real score report. If a first attempt does not pass, the report lists the domains where performance was weakest. Those domains become the top of a new priority list, using the weight-and-gap method from lesson 2 with the report as evidence. Candidates often find that the report confirms what their practice logs already suggested; the difference is that now the evidence is official. CompTIA's retake policy allows a second attempt without a waiting period, but a few weeks of focused work on the weak domains, followed by at least one fresh practice test, is the sensible path before rebooking.