You can pass a certification exam while working full time with roughly one focused hour on weekdays plus one longer weekend session, held for 10 to 12 weeks. The method below converts published vendor preparation estimates into an evening-and-weekend plan that survives a normal work week, then protects that plan with rules for the weeks that usually break it.
This guide was assembled on October 14, 2026, from the official vendor pages listed in the Sources section; every exam figure quoted here was read on those pages during this review. The schedule itself is an illustrative example — resize the blocks to your own deadline and energy rather than treating them as a fixed requirement.
Vendor estimates make the workload explicit: CompTIA’s product pages for Security+ estimate 25–40 hours of foundational learning, 30–60 hours when labs are included, and 10–20 hours for a practice-only path. That spread is the difference between a semester-style effort and a focused five-week sprint, and it is the first number to pin down before booking an exam date.
The Math of a Working Candidate
Start by dividing the vendor’s estimate by your real weekly capacity, not your best week. A working candidate with 45-minute weekday blocks and one 2–3 hour weekend session has roughly six to seven study hours per week, which means a 30–60 hour vendor estimate translates to about five to ten weeks of consistent effort before final review. Candidates who skip this division either burn out in week three or book the exam before they are ready.
Next, anchor your pacing to the exam’s actual shape. According to CompTIA’s official exam page, the current Security+ exam (SY0-701) has a maximum of 90 questions, lasts 90 minutes, and requires a passing score of 750 on a scale of 100-900 — which means practice must include timed sessions, because an untimed practice run proves recall, not pacing.
A 12-Week Schedule That Holds
The table below is an illustrative 12-week frame for a mid-length exam such as Security+; a shorter associate exam compresses it and a CISSP-level exam stretches it. For a domain-by-domain version of this approach with weights and checkpoints, see the 12-week CCSP study plan already published on this site.
| Weeks | Weekday blocks (45 min) | Weekend session (2–3 h) | Milestone |
|---|---|---|---|
| 1–3 | Objectives reading, one domain at a time | Rebuild notes from memory; flashcards for weak terms | All domains read once |
| 4–6 | Labs and hands-on exercises for the heaviest domains | First untimed practice set; log every error | First practice score recorded |
| 7–9 | Error review: only items missed in practice | Timed practice sets under exam conditions | Timed score stable |
| 10–12 | Targeted review of the two weakest domains | Full-length simulation; light review in the final week | Exam-ready decision |
The rule that keeps this alive is separation of concerns: weekdays are for input (reading, labs) and weekends are for output (recall, timed practice). Working candidates who mix the two tend to spend scarce weekend energy re-reading material they already know.
Study Tasks by Exam Format
Match the practice format to the exam format. For exams that mix multiple-choice with performance-based questions, at least part of every weekend session should be hands-on, not just question answering. AWS describes a full-length Official Practice Exam as a highly recommended step prior to attempting the certification exam — treat that as the trigger for booking: when a full-length, timed attempt is consistently above your target, you are ready to schedule.
Practice questions also do double duty as diagnosis. Reviewing a missed item should produce one of three actions: fix a knowledge gap, fix a misread of the question stem, or flag the item as trivial and move on. For a worked example of turning practice errors into a concrete plan, see the guide on how to pass the CEH exam — the error-review loop there applies to any vendor’s exam.
Week One Survival Rules
- Book the exam date first, using the weekly-hours math above — a fixed date creates the deadline the schedule needs.
- Attach the weekday block to a specific time tied to an existing habit (after coffee, before dinner), not to intention alone.
- Keep one weekday completely free each week as a pressure valve; a plan with zero slack breaks in week two.
- Prepare a 10-minute fallback task — flashcards or one short lab — for days when the full block is impossible.
- Log every session in one place (date, minutes, topic) so progress stays visible when motivation dips.
Limits and Honest Caveats
Vendor hour estimates are averages for the vendor’s own product paths, not promises: candidates with relevant job experience finish faster, career changers need longer, and no figure guarantees a pass. No schedule substitutes for hands-on time with the technologies the exam tests. Plan also for what happens after the exam — for example, ISC2 certifications must be renewed on a regular three-year cycle, maintained through continuing professional education credits and an annual maintenance fee, so passing starts a maintenance habit rather than ending the effort.
If your target exam is months away, a slower 20-week variant of the same table works — keep the milestone column and halve the intensity. If the exam is under four weeks out, invert the plan: start from timed practice and let the errors decide what you read.