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 | Laptops, tablets, smartphones — hardware, connectivity, synchronisation | |
| Networking | TCP/IP, ports, protocols, wireless standards, network hardware | |
| Hardware | CPUs, RAM, storage, motherboards, power supplies, printers | |
| Virtualisation & Cloud | Cloud models (IaaS/SaaS/PaaS), hypervisors, virtual machines | |
| Hardware & Network Troubleshooting | Systematic troubleshooting methodology, diagnosing hardware and network problems |
| Domain | Core 2 weight | What it covers |
|---|---|---|
| Operating Systems | Windows, macOS, Linux, Chrome OS — installation, management, command line | |
| Security | Malware, threats, physical security, wireless security, data destruction | |
| Software Troubleshooting | OS problems, malware removal, application issues, mobile device troubleshooting | |
| Operational Procedures | 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:
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.
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.
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.
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.
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.
Exam day tips
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.