How to Use Mock Exams in the Final Six Weeks Before Your CFA or CPA

The Mistake Most Candidates Make

Every year, I see the same pattern. A candidate enters the final six weeks before their CFA or CPA exam with a stack of mock exams, a color-coded review schedule, and a quiet sense of dread. They grind through practice test after practice test, logging scores, watching the numbers inch upward — and then they sit for the real thing and underperform. Not because they didn't work hard. Because they worked wrong.

The core error is treating mock exams as a scoring exercise rather than a diagnostic tool. A mock exam is not a rehearsal for feeling good about yourself. It is a structured method for identifying exactly where your understanding breaks down under pressure, and then rebuilding those weak points before exam day. Every hour you spend retaking a mock without deeply reviewing the prior one is an hour largely wasted. I say this bluntly because the research bears it out: according to CFA Institute pass rate data, roughly 40 to 45 percent of Level I candidates fail in a given sitting. Most of them studied. The differentiator is almost never volume of practice — it's quality of review.

How Many Mocks to Take

For the CFA exam, I recommend completing between four and six full-length mock exams in the final six weeks. For CPA candidates, the structure differs by section — the Exam sections range from 4 to 5 hours — but the principle holds: aim for three to five full-section simulations per exam section you're sitting. Beyond that number, you hit diminishing returns fast, and the time cost becomes punishing.

Here is roughly how I'd distribute those mocks across the six weeks: take your first mock at the start of week one, before you've done any final-phase review. This is your baseline. It will be humbling. That's the point. Use weeks two and three to address the gaps that mock exposed. Take your second mock at the end of week three. Weeks four and five are your most intensive review period. Take mocks three and four during this window, with deep review between each. Save your final mock for the first half of week six, then stop taking new mocks entirely. The last few days before the exam should be light consolidation, not new stress-testing.

If you find yourself tempted to cram in a seventh or eighth mock in those final days, resist it. I've spoken with candidates who took eleven or twelve mocks and still failed. I've spoken with others who took four, reviewed ruthlessly, and passed comfortably. The number isn't the variable that matters most.

How to Review Mistakes So They Actually Stick

This is where most candidates fail to invest properly. After finishing a mock, many will glance at the answer explanations for questions they got wrong and move on. That is not review. That is the illusion of review.

Effective mistake review requires you to categorize every wrong answer before you read the explanation. I call this the three-bucket system. Before you look at why you were wrong, sort each missed question into one of three categories:

Careless error: You knew the concept but misread the question, rushed the calculation, or made an arithmetic slip.

Knowledge gap: You didn't know the concept well enough to answer reliably, even with more time.

Reasoning error: You understood the concept but applied it incorrectly — a misapplication of logic rather than a missing fact.

This sorting step forces you to be honest about your actual failure mode. Careless errors require a different intervention than knowledge gaps. For careless errors, the fix is often slowing down and building a personal checklist of common traps — units, sign conventions, formula variants. For knowledge gaps, you need to return to source material and re-derive the concept from first principles, not just re-read the explanation. For reasoning errors, you need to practice similar questions under low-pressure conditions until the correct logic feels automatic.

After categorizing, write a one-sentence summary of each knowledge gap in your own words — not copied from the answer key, but reconstructed in your own language. This act of retrieval and restatement is what cognitive science calls elaborative interrogation, and it dramatically improves long-term retention compared to passive re-reading. When I graded exams, I could almost always tell the difference between a candidate who understood a concept and one who had merely memorized a phrase. The exam is designed to test the former.

Finally, return to every flagged question two days later and attempt it again from memory, without looking at your notes. If you can't answer it cleanly, it goes back into active review. If you can, it's consolidated. This spaced repetition cycle is non-negotiable for high-yield topics like fixed income valuation, ethics application, or — for CPA candidates — revenue recognition under ASC 606.

Simulating Real Exam Conditions

Condition simulation is something candidates consistently underestimate. The CFA Level I exam is now computer-based and runs across two sessions of 135 minutes each, with 90 questions per session. The CPA exam sections are similarly structured with distinct question types including multiple-choice, task-based simulations, and written communication. Knowing this intellectually is not the same as having your nervous system adapted to it.

When you sit a mock, the conditions need to match the real exam as closely as possible. This means no phone, no music, no pausing to make coffee. It means sitting in a quiet room at a desk — not on your couch. It means using only the materials you'll have access to on exam day. For CFA candidates, that means the approved calculator and nothing else. For CPA candidates, that means the exam's built-in research tools if your provider supports simulation of them.

The timing discipline is particularly important. On the CFA exam, you have exactly 90 seconds per question. That sounds like plenty until you hit a complex derivatives problem or a multi-step fixed income calculation. Candidates who haven't trained their pacing often spend four minutes on question 12 and realize with horror that they've burned their buffer for the next twenty questions. Train your internal clock by setting hard time checkpoints during your mocks — for example, you should be at question 45 no later than the 67-minute mark in a 90-question session. If you're not, you flag the current question and move.

Sophos Academy's timed mock exams are built to replicate these conditions precisely, including per-question timing, randomized question order, and performance analytics that break down your results by topic area and difficulty tier. The free practice questions available at Sophos Academy let you drill individual concepts before you graduate to full mocks — which is exactly the sequencing I recommend.

The Week Before the Exam

I want to address week six specifically because it's where well-prepared candidates often sabotage themselves. After your final mock, you should be doing light review only — revisiting your mistake log, consolidating formulas you've identified as shaky, and doing short targeted practice on your three weakest topic areas. You should not be learning new material. If you encounter something you don't know in week six that you haven't studied yet, let it go. The expected value of cramming a new concept the week before the exam is close to zero, and the cost to your sleep and confidence is real.

Physical preparation matters more than most candidates acknowledge. Sleep in the week before the exam directly affects working memory performance. Staying up until 2 a.m. reviewing ethics cases the night before your exam will cost you more points than it could possibly save.

What to Do Next

If you're in the final six weeks and haven't taken a diagnostic mock yet, start there — use Sophos Academy's free practice questions at [sophosacademy.org/practice](https://sophosacademy.org/practice) to identify your weakest topics before committing to a full simulation. Then build your mock exam schedule using the full timed exams at [sophosacademy.org/mock-exams](https://sophosacademy.org/mock-exams), where the analytics will do a significant portion of the diagnostic work for you. The candidates who pass are not the ones who worked the most hours — they're the ones who worked on the right things, at the right time, in the right conditions.