A+ is two exams, not one. That single fact reshapes how you should study for it, and it's the thing most first-timers underestimate. You don't pass A+ by cramming for "the A+ exam." You pass it by treating Core 1 (220-1101) and Core 2 (220-1102) as two related but distinct projects, usually two months apart.
The rest of this CompTIA A+ study guide is built around that assumption. What's actually on each exam, how long it realistically takes, what trips people up, a condensed week-by-week plan for each exam, and the specific things I'd spend more time on than the average study plan tells you to.
The Basics You Need Before Anything Else
Both exams have the same shape: 90 questions, 90 minutes, a mix of multiple choice and performance-based questions (PBQs). Core 1 passes at 675/900 (roughly 75%), Core 2 at 700/900 (roughly 78%). That 25-point gap matters more than people realize — Core 2 is harder, and it has a higher bar. Don't plan your study time evenly.
PBQs are the scenario questions where you actually do something: drag components, simulate a terminal, match items to a diagram. They're weighted similar to multiple choice, but they eat more time. Usually 6–10 of them per exam, near the start. A lot of candidates freeze on the first PBQ, burn 12 minutes, and then panic through the rest of the exam. More on that later.
Core 1 (220-1101): The Hardware Half
Core 1 is the tangible side of IT — what the parts are, how they connect, and what breaks. The five domains and their weights:
| Domain | Weight |
|---|---|
| Mobile Devices | 15% |
| Networking | 20% |
| Hardware | 25% |
| Virtualization and Cloud | 11% |
| Hardware and Network Troubleshooting | 29% |
Troubleshooting is the biggest domain. Hardware is the second biggest. Together they're more than half the exam. If you've ever cracked open a desktop and replaced RAM, you're already partway there.
The part that catches most people off-guard: printers. Printers show up constantly on Core 1 — not because they're glamorous, but because CompTIA loves them. Laser printer imaging process (the seven steps, in order), inkjet vs. thermal vs. impact vs. 3D, paper jams, toner issues, driver and connectivity problems. I've seen candidates with years of IT experience fail Core 1 on the printer questions alone because they figured "printers are easy" and skipped the detailed review. They aren't. Budget a full study session just for printers.
Networking is the other domain worth extra time. The port-number memorization is unavoidable — HTTP 80, HTTPS 443, FTP 21, SSH 22, Telnet 23, DNS 53, DHCP 67/68, POP3 110, IMAP 143, LDAP 389, SMB 445. Add SMTP 25, RDP 3389, and a few others. Make flashcards. You will see at least a handful of these questions and there's no way to reason your way to the answer.
Mobile devices, virtualization, and cloud are more skim-friendly. Know the difference between IaaS, PaaS, and SaaS (more responsibility = lower in the stack), know what a Type 1 vs. Type 2 hypervisor is, know what an MDM actually does. You don't need to go deep.
Core 2 (220-1102): The Harder One
Core 2 is software, security, and process — and it's where people who assumed A+ was "easy" start struggling. The weights:
| Domain | Weight |
|---|---|
| Operating Systems | 31% |
| Security | 25% |
| Software Troubleshooting | 22% |
| Operational Procedures | 22% |
Operating Systems is almost a third of the exam on its own. That's Windows 10/11 navigation, Windows command line, macOS fundamentals, and Linux commands. The Linux piece is the one people skip. They see five or six commands on the objectives list and think "I'll memorize those in a night." Then the exam asks about chmod notation (what does 755 actually grant?), the difference between sudo and su, what grep -r does, how ls -la output is structured. Spend real time with a Linux VM or WSL. Running the commands is worth more than reading about them.
Security on A+ is conceptual, not technical. Malware types and what each one does. Social engineering. Wireless encryption evolution from WEP through WPA3 (know why each was deprecated). Authentication vs. authorization. If you're coming from any other security background, this domain is fast.
Software troubleshooting is where Windows utilities live — Task Manager, Event Viewer, Device Manager, Services, MSConfig, Resource Monitor. These are exactly the tools you'd use on the job, and the exam tests them as scenarios: "a user reports slow performance, which tool do you use first?" Hands-on practice on an actual Windows machine beats any flashcard for this domain.
Operational procedures covers the boring-but-testable stuff: change management, documentation standards, environmental controls, incident response, professionalism. It reads like common sense until you realize CompTIA has a very specific "right answer" for what you do first in a given scenario. The documentation-first / safety-first / escalation-when-appropriate instinct is what they're testing. When in doubt, pick the answer that involves documenting something or checking with a supervisor. And don't treat it as filler — it's 22% of the exam, so skipping it caps your score at 78% before you've missed a single technical question.
Which Exam First
Core 1. Almost always.
Hardware before software maps to how the field actually works — you need to know what's in the box before troubleshooting the OS running on it. Core 1's passing score is lower, so you build some confidence. And CompTIA's own data shows candidates who pass Core 1 first have higher Core 2 pass rates, though they don't publish exactly how much higher.
The one exception: if you've been doing Windows admin or helpdesk work for a while and barely know what's inside a computer, consider Core 2 first while your OS knowledge is fresh. But this is rare. Most people should take Core 1 first.
Gap between exams: 4–8 weeks is the sweet spot. Less than 4 and you're burned out from the first exam. More than 8 and your momentum is gone. Book Core 2 within a week of passing Core 1, even if the test date is six weeks out — having the date locked in keeps you from drifting.
How Long to Study
Without prior IT experience: 8–12 weeks total, 10–15 hours per week. Split roughly evenly across both exams, with the exam dates stacked.
With some IT experience (helpdesk, building PCs, light Windows admin): 6–8 weeks. You'll still learn new things, but mostly you're filling gaps and learning CompTIA's specific language.
With several years in IT: 3–5 weeks. Your challenge isn't the content — it's learning how CompTIA asks questions. The "most correct" answer on A+ is sometimes not what you'd actually do in the field. You need to practice questions until your instincts match CompTIA's.
One pattern I've noticed: people who study for A+ while working full-time in a non-IT job consistently overestimate how many hours they'll actually study. The first two weeks go great. By week four, life interferes, and the plan collapses. If you're working full-time, plan for 8–10 hours a week, not 15. A plan that assumes you're a robot will fail in ways a realistic plan won't.
A Study Approach That Actually Works
The broad shape: foundation first, then heavy practice questions, then full-length practice exams under real conditions.
The foundation phase is short — maybe two weeks. Pick one primary resource (Wiley's A+ Study Guide is thorough, Professor Messer's free videos are excellent, CompTIA CertMaster is official but expensive) and use it to build a rough mental map of the material. Don't try to master everything here. You're building a scaffold, not a house.
Then move to practice questions as fast as possible. This is where most of the learning actually happens. The feedback loop of "try a question, get it wrong, understand why, try a related question" is what wires the knowledge in. Twenty-five to fifty questions a day, reviewing every wrong answer in detail. Not just "oh, it was B." Understand why A, C, and D were wrong. CompTIA's wrong answers are usually wrong in specific, testable ways.
Use domain-specific question sets while you're working through a domain, and save random shuffled sets for the final review week when you're testing retention. Random questions early on tell you very little about where your gaps are.
Flashcards for the brute-memorization stuff — ports, laser printer imaging steps, wireless standards, RAM types, Linux commands. Fifteen minutes a day. Anki or Quizlet, doesn't matter. What matters is that you hit them daily.
In the last two weeks, do full-length timed practice exams. Two or three minimum, per exam. Same conditions you'll face: 90 minutes, quiet room, no notes, no phone. This is where you find out whether you can actually finish in time and whether your stamina holds up in the last 20 questions. Most candidates who fail didn't fail on content — they failed on pacing.
Another pattern I've seen: candidates who only do practice questions 25 at a time feel confident and then hit a wall at question 60 because they've never sat in front of a screen for 90 straight minutes. A related trap is studying only on your phone — phone-only studiers feel prepared and score lower, because flashcards build familiarity without making you reason through a scenario at full length. Mix your study mediums.
When you review a missed practice question, sort it into one of three buckets: content you didn't know (fix: study more), content you knew but misread (fix: slow down, read twice), or content you knew but second-guessed (fix: trust yourself next time). That third bucket is the one 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.
A+ Core 1 Study Plan: Six Weeks
Six weeks at 10–12 hours a week is what works for most people on the 220-1101 — long enough to get through the hardware and troubleshooting content without rushing, short enough that you don't lose momentum. The plan is weighted toward what the exam weights toward.
Week 1 — Mobile devices and the hardware on-ramp. Knock out Mobile Devices first; most of it is recognition (laptop components, connectivity standards, display types). Then start Hardware: motherboard form factors, CPU basics, the physical layout of a machine. If you can get your hands on an old desktop, open it up. Target: 30–40 practice questions across Domains 1 and 3.
Week 2 — The rest of hardware. The heavy week: storage (HDD vs. SSD, M.2, NVMe, RAID), RAM (DDR3/4/5 and socket pairing), CPUs, cooling, power supplies, peripherals, and printers — including troubleshooting ghosting, jams, streaks, and wrong colors. Aim for 60–70 questions concentrated in Domain 3. Under 65% on Hardware by Friday means another pass on storage and RAM specifically, where wrong-answer patterns are most punishing.
Week 3 — Networking. Ports and protocols need to be cold — the number comes out before you finish reading the question. Then OSI basics, networking hardware, wireless standards (Wi-Fi 5, 6, 6E), and DHCP/DNS/NTP as services. Start port flashcards every morning for the rest of your prep, and run Wireshark once on your own traffic so real DNS, DHCP, and TLS stop being abstract. Target 50–60 questions.
Week 4 — Virtualization, cloud, and the troubleshooting methodology. Domain 4 takes about three days: Type 1 vs. Type 2 hypervisors, snapshots, the cloud models with real examples (AWS EC2 is IaaS, Salesforce is SaaS), cloud characteristics. Spend the rest of the week memorizing the six-step troubleshooting methodology in order — identify the problem, establish a theory, test the theory, establish a plan, implement and verify, document. The exam gives you a scenario and asks what step comes next. Free points.
Week 5 — Troubleshooting deep, and your first full practice exam. Domain 5 is pattern recognition: won't POST → check this first; vertical lines on printouts → these causes; no connectivity → this order. Half the week on hardware troubleshooting, half on network troubleshooting, then a full-length timed practice exam with no pauses. 70%+ is on track; 60–70% means a ruthless Week 6; below 60% usually means adding a week, which is cheaper than a retake.
Week 6 — Review, second practice exam, decision time. Targeted 20-question quizzes on your weak domains, not random sets. Mid-week, a second full-length exam aiming for 80% — not 75%, because the real exam will have questions that feel weirder than your practice set. At 80%+, book it. At 75–80%, book it or take a few more days. Below 75% this late, add a week on your bottom two domains.
A+ Core 2 Study Plan: Six Weeks
Same shape — six weeks, 10–12 hours a week — but with hands-on time every week, because Core 2 PBQs drop you into a simulated Windows or terminal interface and tell you to do something. Candidates who study only from flashcards sometimes score 85% on the multiple choice and still fail. If you've never opened PowerShell, you'll freeze when asked to use it under a timer.
Week 1 — Windows. The week that matters most: Windows is nearly a third of the exam and where PBQs cluster. Know which features exist only in Pro and above (BitLocker, Group Policy, domain join, Remote Desktop host, Hyper-V) — tested directly. Run the command-line tools (ipconfig, tracert, nslookup, netstat, systeminfo, tasklist, chkdsk, sfc /scannow, dism, gpupdate, diskpart) and read their output; for PowerShell know the verb-noun structure and a few cmdlets (Get-Process, Get-Service, Stop-Service), because the exam mixes cmd and PowerShell syntax into trap answers. Then Control Panel vs. Settings: a common PBQ has you set a static IP, enable Remote Desktop, or change the UAC level, and you have to know where to click. 40–50 Windows questions to close.
Week 2 — macOS, Linux, Chrome OS, file systems. Functional knowledge, not mastery. macOS: APFS, Time Machine, Keychain, Spotlight, Gatekeeper, FileVault. Linux: the command list above, plus permissions in numeric notation — chmod 755 cold, because it shows up in PBQs. Chrome OS gets an hour. File systems: NTFS, FAT32, exFAT, APFS, ext4 — which OS uses which and why it matters. 30–40 mixed-OS questions; under 70% here is almost always Linux commands.
Week 3 — Security. Needs all seven days. Malware categories as scenarios ("a program encrypts files and demands payment"); social engineering with its picky naming (spear phishing vs. whaling, vishing, smishing, pretexting, tailgating, evil twin). Windows security features: BitLocker vs. BitLocker To Go, EFS, UAC, Secure Boot, TPM. The classic trap is NTFS vs. share permissions — the most restrictive wins when combined. Then MFA factors, Active Directory groups, MDM and remote wipe, and SOHO security (WPA3, disabling WPS, guest networks, why MAC filtering isn't real security). 50+ scenario-weighted questions.
Week 4 — Operational procedures, and your first full practice exam. Change management (RFC, approval, rollback), documentation and ticketing, backup types (full, incremental, differential, synthetic), the 3-2-1 strategy, RTO vs. RPO. Scripting is recognition only: what .bat, .ps1, .sh, .py, .vbs, and .js are for, and the risks of running scripts. Professionalism and chain of custody show up more than you'd expect. Then a full-length exam — whatever you score is your real baseline. Review every miss using the three buckets above.
Week 5 — Software troubleshooting. One piece shows up on nearly every exam: the seven-step malware removal process, in strict order — investigate and verify symptoms, quarantine, disable System Restore, remediate (update anti-malware, scan and remove), schedule scans and run updates, re-enable System Restore and create a restore point, educate the user. People trip on steps 3 and 6 because disabling System Restore before cleaning feels counterintuitive; the logic is that restore points can re-infect the machine. Beyond that: boot issues and BSOD stop codes, recovery options (Safe Mode, startup repair, bootrec, reset), browser problems (cert errors, redirects, hijacked search), mobile app issues. 40–50 troubleshooting questions, with PBQs if your bank has them.
Week 6 — Final review and two more practice exams. Two or three focused days on your two weakest domains. Mid-week, a second full-length exam — you should be at 75–80%; if you're at 70% or below, push the real exam back a week rather than paying for a reality check. End of the week, a third, aiming for consistent 80%+. The day before: light review, confirm logistics and ID, sleep.
Adjusting the Plans to Your Life
Four weeks (strong IT background). For Core 1: Domains 1, 3, 4 in Week 1; finish 3 and start 2 in Week 2; finish 2 and start 5 in Week 3; finish 5 plus two practice exams in Week 4. That's 14–16 hours a week and only works if you already know the hardware content from your job. For Core 2, six months of help desk experience usually lets you fold Week 2 into Week 1.
Eight to ten weeks (full-time job or school). Spread each plan out at 6–8 hours a week, two weeks per block. The risk is losing momentum around Week 5, so schedule a full practice exam earlier than the plan says to keep the urgency up.
One trade that's almost always wrong: skipping practice exams because "there's no time" while still finding an hour for more flashcards. Full-length practice exams are the single best predictor of exam-day performance.
Hands-On Is the Unfair Advantage
A+ rewards people who have actually touched hardware and used the tools. The knowledge sticks differently. If you can:
Open a desktop (powered down, unplugged, grounded). Identify the CPU, RAM slots, storage, PSU, motherboard. Swap RAM. Reseat a drive. Find the CMOS battery.
Enter the BIOS/UEFI on any machine you have access to. Change boot order. Look at the hardware info screens. Five minutes, and it makes half the hardware domain concrete.
Explore your own router's admin page. Look at the DHCP lease table, change the DNS server, and watch what happens.
Install VirtualBox or VMware Workstation Player. Spin up a Windows 10 VM and a Linux VM (Ubuntu is fine). Run commands. Break things. Fix them. You'll remember ifconfig vs. ipconfig forever after doing it twice.
Use Windows admin tools on your actual machine. Open Event Viewer, find a warning, click into it. Open Task Manager and end a process.
None of this requires a lab budget. Five hours of this across a six-week plan will outperform five hours of re-reading a textbook.
The PBQs — Don't Let Them Eat Your Time
Here's the mistake: PBQs come at the start of the exam, they're intimidating, and candidates spend 15 minutes on the first one trying to get it perfect. That leaves 75 minutes for the remaining 80+ questions. Bad trade.
The right approach: if a PBQ isn't clicking within 3–4 minutes, flag it and move on. Finish the multiple-choice questions first. They're faster, and you'll have cleared most of the exam by the time you come back. Then use your remaining time on the PBQs with a clearer head.
PBQs are also partial-credit — you don't need a perfect answer to get points. Get what you can get, then move on. A half-right PBQ plus 15 correct multiple choice answers beats a perfect PBQ and a guessed-through final section.
The Topics That Most Often Cost People the Exam
Printers on Core 1. Already covered. Go back and spend a study session on this.
Linux commands on Core 2. Memorizing them without running them doesn't stick. Use WSL or a VM.
Port numbers. There's no shortcut — flashcards, daily, until they're automatic. But memorize with understanding: the questions that hurt aren't "what port is HTTPS," they're "the user can reach http:// but not https://, what's the most likely cause."
Laser printer imaging process. Seven steps, specific order: processing, charging, exposing, developing, transferring, fusing, cleaning.
The seven-step malware removal process and the six-step troubleshooting methodology. Both tested as strict sequences.
NTFS permissions vs. share permissions. Most restrictive wins.
Wireless encryption. WEP (broken), WPA (better), WPA2 (AES), WPA3 (current), and "enterprise" vs. "personal" mode.
Cloud models. IaaS is the most responsibility, SaaS is the least. Who manages what at each level.
After A+
Most people going for A+ are aiming for the CompTIA "trifecta": A+, Network+, Security+. That combination is the standard entry-level IT package, and it opens most helpdesk, support, and junior security roles. If that's your path, start Network+ within 2–3 months of passing A+. The networking knowledge overlaps, and you'll get through Network+ faster while Core 1 material is still fresh.
If your target is specifically cybersecurity, consider skipping straight from A+ to Security+ — you can, and it's a valid route. Network+ is genuinely useful but not strictly required.
One Last Thing
If you're about to start studying, the most useful thing you can do today isn't buy another course — it's figure out where you actually stand. Most people overestimate their hardware knowledge and underestimate how much Linux and Windows command line they'll need. A 30-minute diagnostic tells you that before you commit to a plan, and lets you redistribute the weeks above to match where your gaps actually are — someone with help desk experience can skim Core 2's Week 1 in three days, while someone new to Windows administration may need two weeks on it.
LearnZapp has a free CompTIA A+ diagnostic that covers both Core 1 and Core 2 objectives, sourced from the Wiley A+ Official Study Guide. No signup, domain-level results so you can see where your real gaps are: Take the free CompTIA A+ diagnostic.