Six weeks at 10–12 hours a week is what works for most people on the 220-1101. Not because it's magic, but because it's long enough to get through the hardware and troubleshooting content without rushing, and short enough that you don't lose momentum halfway through.
The plan below is the one I'd actually hand a friend who asked. It's weighted toward the things the exam weights toward — which a lot of study guides pretend isn't a factor but absolutely is.
What you're actually preparing for
A+ Core 1 is up to 90 questions, 90 minutes, and a 675/900 passing score that translates to roughly 75%. There are five domains, but don't let that number fool you — two of them (Hardware at 25% and Troubleshooting at 29%) account for over half the exam. Everything else is fighting over the remaining 46%.
The exam also has performance-based questions (PBQs) at the start. Most people spend too long on them, panic, and then rush through the last 60 multiple-choice questions. One pattern I've seen repeatedly: candidates who are technically ready but never practiced under time pressure finish the PBQs with 45 minutes left — instead of the 60+ they'd need to go at a comfortable pace.
That's the real exam. Now the plan.
The weekly breakdown
Week 1 — Mobile devices and the hardware on-ramp
Start with Domain 1 (Mobile Devices, 15%) and get the first third of Domain 3 (Hardware) down. Mobile is the easiest domain to knock out in a week because most of it is recognition — laptop components, connectivity standards (Bluetooth, NFC, cellular generations), the difference between display types. You're not reasoning, you're remembering.
Then start Hardware from the top: motherboard form factors, CPU basics, the physical layout of a machine. If you can get hands on an old desktop this week, open it up. I know that sounds quaint, but people who touch the hardware remember it noticeably better than people who just look at diagrams. There's a reason.
End of week target: 30–40 practice questions across Domains 1 and 3. You should be able to walk through the inside of a desktop and name every major component out loud.
Week 2 — The rest of hardware
This is the heavy week. Storage (HDD vs. SSD, M.2, NVMe, RAID levels), RAM (DDR3/4/5 and what pairs with which CPU socket), CPUs, cooling, power supplies, peripherals, and — yes — printers.
Printers get underestimated. They show up on the exam more than you'd expect for how boring they are, and the questions aren't just "what is a laser printer." They want you to troubleshoot them: ghosting, paper jams, streaks, wrong colors. Spend an hour just on printers. It's not exciting, but it's high ROI for how quickly the questions can be answered when you know them.
Aim for 60–70 practice questions this week, heavily concentrated in Domain 3. If you're scoring under 65% on Hardware questions by Friday, slow down and do another pass on storage and RAM specifically — those are the two sub-topics where wrong-answer patterns are the most punishing.
Week 3 — Networking
Domain 2 is 20% of the exam but feels bigger because the content density is high. Ports and protocols alone could be its own week: HTTP/HTTPS, DNS, DHCP, FTP, SSH, RDP, SMTP/POP3/IMAP, SNMP. You need these cold — not "I can figure it out" cold, but "the port number comes out of my mouth before I finish reading the question" cold.
The rest of Week 3: OSI model basics, networking hardware (routers, switches, APs, firewalls), wireless standards (Wi-Fi 5 and 6, and 6E if you want to be safe), and DHCP/DNS/NTP as services.
Two things that help a lot here:
- Flashcards for ports. Do them every morning for the rest of your prep. Five minutes. This is the one place where pure memorization pays off more than any other study technique on this exam.
- Wireshark. Fire it up, capture five minutes of your own traffic, poke around. You don't need to become an analyst — you just need to have seen real DNS and DHCP and TLS traffic once. It makes the abstract concrete.
Target 50–60 questions for the week.
Week 4 — Virtualization, cloud, and the start of troubleshooting
Domain 4 (Virtualization and Cloud, 11%) is the lightest domain and probably the one you'll spend the least time on. Hypervisors (Type 1 vs. Type 2), VM snapshots, the three cloud models (IaaS/PaaS/SaaS with actual examples — AWS EC2 is IaaS, Salesforce is SaaS, stop confusing them), and the general cloud characteristics (on-demand, elastic, metered, etc.).
That's maybe three days of study. Use the rest of the week to start Domain 5 by getting the six-step troubleshooting methodology fully memorized:
- Identify the problem
- Establish a theory of probable cause
- Test the theory
- Establish a plan of action
- Implement the solution and verify functionality
- Document findings
You will get questions on this. They'll give you a scenario and ask what step comes next, or they'll give you a step and ask what you do first. Know the order. Know what belongs in each step. This is free points if you internalize it.
Week 5 — Troubleshooting, deep, and your first full practice exam
Troubleshooting is 29% of the exam. It's also the domain where reading about it only gets you halfway. The questions are scenario-based and they reward pattern recognition: computer won't POST → check this first; printer output has vertical lines → narrow to these causes; no network connectivity → walk through this order.
Spend the first half of the week on hardware troubleshooting (boot issues, display failures, overheating, weird noises, BIOS/UEFI diagnostics) and the second half on network troubleshooting (DNS issues, IP conflicts, slow connections, wireless signal problems).
Then, take a full-length practice exam. Time yourself. Don't pause. Don't look anything up. Treat it like it's Pearson VUE.
If you score 70% or above, you're on track. If you score 60–70%, you're not behind, but Week 6 needs to be ruthless about your weak domains. Below 60% usually means you need an extra week, and that's fine — it's much cheaper to delay than to retake.
The review matters more than the score. Go through every question you missed and figure out why you missed it. Three categories:
- Content I didn't know (fix: study more)
- Content I knew but misread (fix: slow down, read twice)
- Content I knew but second-guessed (fix: trust yourself on the next one)
That third category is the one most people don't notice. If half your misses are "I had the right answer and changed it," you don't have a knowledge problem — you have a test-taking problem, and the fix is different.
Week 6 — Review, second practice exam, decision time
Revisit the weak domains from your Week 5 practice exam. Do targeted quizzes — 20 questions at a time on a specific topic, not random full-domain sets. If storage form factors tripped you up, drill them until you can rattle off M.2 vs. 2.5" vs. mSATA in your sleep.
Mid-week, take a second full-length practice exam. Your goal is 80% or higher. Not 75% — 80%. The real exam will have at least a few questions that feel weirder than your practice set, and you want margin for that.
If you hit 80%+, schedule the real exam. If you're between 75–80%, you can either schedule it and trust yourself or give yourself a few more days of focused review. If you're below 75% on a full practice exam this late in the plan, don't book yet. Add a week, target your bottom two domains, and try again.
The shorter and longer versions
Not everyone has six weeks. Here's how to compress or stretch:
Four weeks (for people with strong IT background already). Week 1: Domains 1, 3, 4. Week 2: finish 3, start 2. Week 3: finish 2, start 5. Week 4: finish 5, two practice exams. You'll need 14–16 hours a week. This works if you already know most of the hardware content from your job — if you're starting from scratch, four weeks is tight.
Eight weeks (for people studying alongside a full-time job or school). Spread the above out: two weeks each on Mobile+Hardware basics, Hardware deep, Networking, and Cloud/Troubleshooting. 6–8 hours a week. The risk with longer plans is losing momentum by Week 5, so build in a practice exam earlier — around Week 5 or 6 of 8 — to keep urgency up.
Where people lose points they shouldn't
A few patterns I see over and over with A+ Core 1 candidates:
Skipping PBQ practice. PBQs are 4–5 questions worth a disproportionate amount of the exam score. They're also unfamiliar — drag-and-drop, simulations, labeling diagrams. If you've never done one before test day, you'll burn 30+ minutes panicking on the first one.
Memorizing without understanding. You can memorize that port 443 is HTTPS, but if you don't know why HTTPS needs a port in the first place, the troubleshooting questions will eat you alive. The ones that hurt aren't "what port is HTTPS" — they're "the user can reach http:// but not https://, what's the most likely cause."
Studying only on the phone. Phone-only studiers tend to feel prepared and score lower. The material feels familiar from flashcards but they haven't practiced reasoning through a scenario at full desktop length. Mix your study mediums.
Believing the "I'll figure it out on test day" line about the troubleshooting methodology. You won't. You'll freeze on question 42, pick the thing that feels right, and it'll be the step that comes after the correct one. Memorize the order.
The hands-on stuff actually matters
A+ rewards people who've touched hardware. You don't need a lab — a single old desktop, or a laptop you're willing to open, is enough. Pull the RAM. Reseat it. Identify the SATA connectors. Find the CMOS battery. Five hours of this across your six-week prep will outperform five hours of re-reading a textbook.
For networking, explore your own router's admin page. Look at the DHCP lease table. Change the DNS server and watch what happens. Set up a VirtualBox VM and connect it to a virtual network. These aren't things you need to master — you just need to have done them once so the exam questions stop feeling abstract.
Using LearnZapp alongside this plan
LearnZapp has 10,524+ A+ questions sourced from Wiley, with breakdowns by domain and sub-topic. The honest best use isn't "do all of them" — it's diagnostic first, then targeted practice in your weak areas.
What I'd actually recommend: take the free diagnostic before Week 1 to see where your baseline is. If you're already at 50%+ on Hardware because you've worked helpdesk for a year, you can spend less time there and more on Domain 4 or the ports. If you're coming in cold, the diagnostic tells you which domain to start with on Day 1.
During the plan, use domain-specific question sets after each week instead of random shuffled questions. Random is for Week 6 when you're testing retention. Weeks 1–5 are for building depth in each domain one at a time.
Take a free CompTIA A+ diagnostic test — no signup, gives you a per-domain breakdown in about 20 minutes. Use it to figure out where your actual weak spots are before you pick a start point. Most people are wrong about where they're weak, and that's the cheapest mistake to fix.