⚡ The short version
CompTIA A+ requires passing two exams — Core 1 (220-1201) and Core 2 (220-1202). Most people pass with 2–4 months of consistent study using a good textbook, practice exams, and hands-on practice. The exam isn't about memorising facts — it's about applying knowledge to realistic troubleshooting scenarios. That distinction is why people who only read textbooks fail, and people who combine reading with practice questions pass.
2
Exams required
90
Questions per exam
675 / 900
Passing score (Core 1)
700 / 900
Passing score (Core 2)

What the A+ exam actually tests

A lot of people go into A+ expecting a hardware quiz and are surprised by how much troubleshooting, operating systems, networking, and security content appears. The exam tests whether you can think like a technician — given a real scenario, what would you do first, what would you check, and what's the most likely cause?

Performance-based questions (PBQs) appear at the start of each exam and require you to interact with simulated environments — drag-and-drop cable connections, configure settings in a simulated OS, or work through a troubleshooting scenario. These take longer than multiple choice and cannot be skipped entirely. Many candidates underestimate them.

Domain Core 1 weight What it covers
Mobile Devices
15%
Laptops, tablets, smartphones — hardware, connectivity, synchronisation
Networking
20%
TCP/IP, ports, protocols, wireless standards, network hardware
Hardware
25%
CPUs, RAM, storage, motherboards, power supplies, printers
Virtualisation & Cloud
11%
Cloud models (IaaS/SaaS/PaaS), hypervisors, virtual machines
Hardware & Network Troubleshooting
29%
Systematic troubleshooting methodology, diagnosing hardware and network problems
Domain Core 2 weight What it covers
Operating Systems
27%
Windows, macOS, Linux, Chrome OS — installation, management, command line
Security
25%
Malware, threats, physical security, wireless security, data destruction
Software Troubleshooting
22%
OS problems, malware removal, application issues, mobile device troubleshooting
Operational Procedures
26%
Documentation, change management, safety, environmental controls, professionalism

How long does it take to study for A+?

The honest answer is 2–4 months for most people studying part-time (1–2 hours per day). That said, your starting point matters significantly:

🆕
Complete beginner
No IT background at all — budget 3–4 months. The hardware and networking content will be mostly new and needs time to sink in through practice.
🖥️
Some IT experience
You've built PCs, worked help desk, or studied IT casually — 2–3 months is realistic. You'll move faster through hardware but may need more time on troubleshooting methodology.
💼
Working in IT already
Active IT role — 6–8 weeks is achievable. Focus your time on domains outside your daily work. Don't assume job experience covers exam content; the domains are broader than most IT roles.
🔁
Retaking after a fail
2–4 more weeks focused on your weak domains. Pull your score report, identify the lowest-scoring areas, and target those specifically rather than re-studying everything.

The study plan that works

Most people who fail A+ studied too passively — they read or watched videos but didn't do enough practice questions. The study plan below is built around active recall, which is how you actually retain technical material.

1
Weeks 1–4 — Build the foundation
Core 1 content: hardware, networking, mobile devices

Work through a structured study guide (Walker Bridge's CompTIA A+ Core Study Guide or Professor Messer's free course) covering Core 1 domains. Don't rush — understanding the hardware and networking fundamentals deeply makes everything else easier. After each chapter, do 10–15 practice questions on that topic.

Read or watch the hardware domain in full — CPUs, RAM, storage types, motherboard components
Cover the networking domain — TCP/IP, ports, protocols, wireless standards
Do 15–20 practice questions per domain as you go
Build or explore a PC physically if possible — hands-on accelerates retention dramatically
2
Weeks 5–6 — Core 1 practice and review
Practice exams, identify weak areas, targeted review

Stop reading new material and switch entirely to practice exams. Take full timed practice tests to simulate exam conditions. Review every wrong answer — not just what the right answer is, but why the other options are wrong.

Take 2–3 full Core 1 practice exams under timed conditions
Score each domain separately — identify where you're below 75%
Go back to weak domains only — don't re-study what you already know
Target 80%+ consistently on practice tests before booking the real exam
3
Sit Core 1 — then start Core 2
Don't wait too long between exams

Book and sit Core 1 when you're consistently hitting 80%+ on practice tests. Then begin Core 2 immediately — don't take a long break. Core 2 covers operating systems, security, software troubleshooting, and operational procedures. The security content here overlaps with what Security+ covers at a deeper level.

Book Core 1 when practice scores are consistently 80%+
Start Core 2 study within a week of sitting Core 1
Pay extra attention to Windows command line — it's heavily tested
Don't neglect operational procedures — it's 26% of Core 2 and often under-studied
4
Weeks 9–12 — Core 2 practice and exam
Same process — practice heavy, targeted review

Repeat the same process for Core 2. Switch to practice exams after covering the content, target weak domains, and book the exam when scores are consistent. Many people find Core 2 harder than Core 1 because the operating system and troubleshooting scenarios require more judgment calls.

Take 2–3 full Core 2 practice exams under timed conditions
Focus extra time on OS troubleshooting and security scenarios
Practice PBQ-style questions — simulate, don't just read
Book and sit Core 2 when practice scores are consistently 80%+

Exam day tips

🚩
Flag and skip PBQs first
PBQs appear at the start and take 5–10 minutes each. Flag them, skip to multiple choice, answer everything you can, then return to PBQs with remaining time. This alone improves scores for many candidates.
🔍
Read every option before answering
A+ scenario questions often have two plausible answers. The right answer is usually the "best first step" — systematic troubleshooting methodology matters. Read all four options before committing.
⏱️
Watch your time
90 minutes for up to 90 questions. That's 1 minute per question maximum. Don't spend 4 minutes on one question — flag it and move on. Unanswered questions are wrong; guesses have a chance.
🧠
Trust your preparation
If you've been hitting 80%+ on practice tests consistently, you're ready. Exam anxiety causes more failures than lack of knowledge. The real exam format matches quality practice tests closely.
📋
Use the notepad
You get scratch paper or a digital notepad at the testing centre. Use it to write down subnetting formulas, port numbers, or anything else you've memorised before the timer starts.
🔄
Change answers carefully
Your first instinct is usually right. Only change an answer if you have a specific reason — not just because you feel uncertain on review. Second-guessing without new information usually hurts scores.
⚡ The most common reason people fail

Not enough practice questions. Reading and watching videos feels productive but it's passive. The exam tests application, not recall. If you can't consistently score 75%+ on practice tests, you're not ready — regardless of how much you've read. Switch to active practice earlier than feels comfortable.

The second most common reason: underestimating Core 2 operational procedures. It's 26% of the exam and covers documentation, change management, and professionalism — topics that feel boring to study but appear constantly on the actual exam.


Ready to start studying?

The best A+ study guide, practice exams, and Professor Messer's free course for 2026.

See A+ Study Resources →

Related Articles