CompTIA A+ Exam Prep: The 8-Week Plan

Updated August 2026

This is a default 8-week structure — one that works Core 1 domains first, sits Core 1, then works Core 2 domains and sits Core 2. It assumes a few focused hours most days. If that's not your pace, the last section shows how to compress or stretch it without cutting corners.

Week 1: Mobile Devices and Networking (Core 1)

  • Read the official 220-1201 objectives for domains 1.0 (Mobile Devices) and 2.0 (Networking) before touching any other material.
  • Work through laptop hardware: what's field-replaceable vs. what needs a full teardown, display types, and wireless expansion.
  • Drill networking cold: common port numbers, the 802.11 standards table, cable categories, and how DHCP/DNS actually work.
  • Finish the week with end-of-domain practice questions for 1.0 and 2.0, and re-drill whatever you miss.

Week 2: Hardware (Core 1)

  • Work through domain 3.0 one component group at a time: RAM, storage/RAID, motherboards and CPUs, then power supplies.
  • Learn cable and connector types by sight, not just by name — video, peripheral, and power connectors all show up on PBQs as photos.
  • Cover printer maintenance procedures for laser, inkjet, thermal, and impact printers — CompTIA tests the differences between them directly.
  • End-of-domain practice questions for 3.0 before moving on; it's one of the largest domains on Core 1.

Week 3: Virtualization & Cloud and Troubleshooting (Core 1)

  • Domain 4.0 is small — cloud service and deployment models, plus client-side virtualization — and can be finished in a day or two.
  • Domain 5.0 is the biggest domain on Core 1: learn CompTIA's troubleshooting methodology in its exact order and practice applying it, not just reciting it.
  • Drill symptom-to-cause pairings across hardware, printers, and networking until the likely cause is automatic, not a guess.
  • Practice questions for both 4.0 and 5.0, weighting extra time toward 5.0.

Week 4: Core 1 review and exam

  • Take a full timed practice test covering all five Core 1 domains and log every miss by domain.
  • Spend the week re-drilling weak domains only — don't re-study material you already have cold.
  • Do a final push of PBQ drilling; try a free practice test at examwizardz.app/practice-test/comptia-a-plus-core-1 to check readiness.
  • Sit Core 1 (220-1201).

Week 5: Operating Systems (Core 2)

  • Domain 1.0 is tied for the largest Core 2 domain (28%) — start with Windows editions, features, and built-in utilities.
  • Practice the same task through both the GUI and the command line (Task Manager vs. msconfig, for example) so a PBQ can't box you into an interface you haven't used.
  • Cover macOS and Linux basics, OS installation types, and NTFS vs. exFAT vs. APFS vs. ext4 file systems and permissions.
  • End-of-domain practice questions for 1.0.

Week 6: Security (Core 2)

  • Domain 2.0 is the other 28% domain — build a comparison table for malware types and social-engineering tactics so you can tell similar-sounding ones apart under time pressure.
  • Cover physical and logical security controls, wireless and workstation hardening, and multifactor authentication.
  • Learn secure data destruction methods and when each one applies.
  • End-of-domain practice questions for 2.0 — this domain and 1.0 together make up more than half of Core 2.

Week 7: Software Troubleshooting and Operational Procedures (Core 2)

  • Domain 3.0 (23%): Windows symptoms, PC security symptoms, mobile OS issues, and the malware removal procedure — memorize it as a fixed 7-step order, since it's one of the most frequently tested ordered sequences on the exam.
  • Domain 4.0 (21%): documentation and change management, backup strategies, safety and ESD precautions, professionalism, and basic scripting concepts.
  • Don't skip 4.0 because it feels like "soft skills" — it's more than a fifth of Core 2 and the questions are usually straightforward if you've read the objectives once.
  • End-of-domain practice questions for 3.0 and 4.0.

Week 8: Core 2 review and exam

  • Take a full timed practice test covering all four Core 2 domains and log every miss by domain.
  • Re-drill weak domains, with extra attention to the malware removal order and other ordered-procedure PBQs.
  • Do a final push of PBQ drilling; try a free practice test at examwizardz.app/practice-test/comptia-a-plus-core-2 to check readiness.
  • Sit Core 2 (220-1202).

Adjusting the plan

This 8-week structure assumes a moderate daily pace. If you already have IT experience — help desk work, building your own PCs, comfortable troubleshooting Windows — you can often compress it to around 6 weeks by combining the Hardware and Troubleshooting weeks, or the Security and Software Troubleshooting weeks, since the material overlaps more than it does for a complete beginner. If you're studying under 5 hours a week, stretch the same content over 12 weeks instead of compressing the material — add buffer, don't skip domains or the review weeks.

Consistency beats cramming. Start daily flashcards in week 1 — 15-20 minutes a day on ports, standards, and command-line syntax compounds far more than a single long weekend cram session ever will.

Ready to actually study for it?

ExamWizardz turns the official A+ objectives into a guided plan with practice tests, realistic PBQs, and a readiness score.

Start studying free

Frequently asked

Is 8 weeks enough to prepare for CompTIA A+?

For most candidates with a few focused hours most days, yes. Your actual timeline depends on your background — some IT experience can shorten it, being a complete beginner or studying fewer hours a week can lengthen it.

Can I take Core 1 and Core 2 in the same month?

It's possible if you study intensively, but it's tight — most people prepare for and sit Core 1 first, then use a few focused weeks for Core 2 rather than studying both exams' material in parallel.

What if I fall behind on a week of this plan?

Extend the timeline rather than cutting the review or PBQ-drilling weeks — those are the weeks that catch weak spots before exam day, and skipping them is exactly what leads to a first-attempt fail.

Keep reading