CompTIA A+ Study Guide 2026: Core 1 and Core 2 Breakdown

The CompTIA A+ requires passing two separate exams. Not one. Two. Each with its own objectives, its own domain weights, and its own passing score. You can take them in any order, months apart if you want, but you don't hold the certification until both are done. This is the first thing new candidates miss, and it affects everything about how you should plan your study time.

The current exam codes are 220-1201 (Core 1) and 220-1202 (Core 2), released March 2025. They replaced the 220-1101/1102 series and will remain active through 2027-2028. If you're starting now, you have plenty of runway before retirement.

Two Exams, Two Different Tests

Core 1 and Core 2 don't just split the A+ material in half. They test fundamentally different skill sets. Core 1 is hardware-heavy: physical components, networking infrastructure, mobile devices, cloud computing. Core 2 is software-heavy: operating systems, security practices, troubleshooting methodology, operational procedures.

The passing scores are different too. Core 1 requires 675 out of 900. Core 2 requires 700 out of 900. That higher threshold on Core 2 isn't arbitrary; the software and security content has more ambiguity in its answer choices, and CompTIA sets the bar accordingly.

Both exams give you 90 questions in 90 minutes. That's 60 seconds per question on average, which sounds manageable until you factor in the performance-based questions that can eat 5-10 minutes each.

Core 1 (220-1201): Hardware, Networking, and Cloud

Core 1 is the more concrete exam. Most of what it tests, you can see and touch: cables, connectors, motherboard components, printer types. The domain breakdown:

• Mobile Devices (13%) — Laptop components, display types, connection methods, mobile device accessories and connectivity
• Networking (23%) — TCP/IP, ports, protocols, Wi-Fi standards, network hardware, cabling
• Hardware (25%) — Motherboard form factors, RAM types, storage drives, power supplies, peripheral devices
• Virtualization and Cloud (11%) — VM setup, cloud service models (IaaS, PaaS, SaaS), cloud deployment types
• Hardware and Network Troubleshooting (28%) — Troubleshooting methodology, common hardware failures, network connectivity issues

Troubleshooting is the heaviest domain at 28%. This is where CompTIA tests whether you can actually diagnose problems, not just identify components. You'll get scenarios describing symptoms and have to pick the most likely cause or the correct first step. The troubleshooting methodology matters here: identify the problem, establish a theory, test the theory, establish a plan of action, verify, document. CompTIA expects you to follow this sequence, and questions often hinge on which step comes next.

What to Focus On for Core 1

Port numbers. You need to know TCP/UDP port numbers cold: 21 (FTP), 22 (SSH), 23 (Telnet), 25 (SMTP), 53 (DNS), 67/68 (DHCP), 80 (HTTP), 110 (POP3), 143 (IMAP), 443 (HTTPS), 445 (SMB), 3389 (RDP). These appear as both direct recall questions and as part of troubleshooting scenarios where identifying the port tells you which service is affected.

Cable types and connector identification will appear on the exam. Know the difference between Cat 5e, Cat 6, and Cat 6a. Know fiber types (single-mode vs. multimode). Know your video connectors: HDMI, DisplayPort, DVI, VGA. These are free points if you've studied them and lost points if you haven't, since there's no way to reason your way to the answer without prior knowledge.

For the cloud and virtualization section, understand the service models well enough to classify real scenarios. "A company wants to run its own applications on someone else's infrastructure" is IaaS. "A company wants to use pre-built software through a browser" is SaaS. The definitions are simple; the exam tests whether you can apply them to described situations.

Core 2 (220-1202): Software, Security, and Operations

Core 2 is more conceptual than Core 1. The content shifts from physical hardware to software configuration, security policies, and professional procedures. The domain breakdown:

• Operating Systems (28%) — Windows, macOS, Linux, mobile OS installation, configuration, and management
• Security (28%) — Malware types, social engineering, authentication, encryption, endpoint protection
• Software Troubleshooting (23%) — OS issues, application crashes, browser problems, malware removal
• Operational Procedures (21%) — Documentation, change management, disaster recovery, scripting basics, professionalism

Operating Systems

Windows dominates this domain, but Linux and macOS questions appear too. You need to know Windows command-line tools: ipconfig, sfc, chkdsk, diskpart, gpupdate, gpresult. Know which tool does what, and know the flags that matter. sfc /scannow repairs system files. chkdsk /r finds bad sectors and recovers data. These are tested directly.

For Linux, know basic commands: ls, cd, chmod, chown, grep, apt-get/yum, sudo. You don't need to be a Linux admin, but you need to navigate a filesystem, change permissions, and install packages. The exam also tests file system types (ext4, NTFS, FAT32, APFS) and when each is appropriate.

Security

Security is tied with Operating Systems as the heaviest Core 2 domain at 28%. Know your malware categories: viruses, worms, trojans, ransomware, spyware, rootkits. You also need to know the removal process CompTIA expects: identify malware symptoms, quarantine the system, disable System Restore, remediate, schedule scans, enable System Restore, educate the user. The order matters on the exam.

Social engineering comes up frequently. Phishing, vishing, tailgating, shoulder surfing, dumpster diving. The questions here are usually straightforward identification: a scenario describes an attack, you identify the type. But some ask for the best prevention measure, which requires understanding both the attack vector and the appropriate countermeasure.

Software Troubleshooting

This domain overlaps with Operating Systems but focuses specifically on diagnosis. Boot failures, blue screens, application crashes, slow performance. The troubleshooting methodology from Core 1 applies here too. A common question pattern: "A user reports their computer is running slowly. Which of the following should you check first?" The answer is almost always the simplest, least invasive diagnostic step, not the nuclear option.

Performance-Based Questions (PBQs)

Both exams include PBQs, and they're worth more than standard multiple-choice questions. PBQs drop you into a simulated environment where you configure a network, set up a firewall, troubleshoot a connectivity issue, or complete a similar hands-on task. You interact with a virtual interface rather than picking from a list.

The best strategy: skip PBQs on your first pass. They appear at the beginning of the exam, which is deliberate. CompTIA puts them there to eat your time early if you let them. Flag every PBQ, work through all the multiple-choice questions first, then return to the PBQs with your remaining time. You'll answer the multiple-choice questions faster because they build your confidence and sometimes give you context that helps with the PBQs.

Common PBQ scenarios on Core 1 include setting up a wireless network (SSID, security type, channel), configuring IP addresses, and identifying hardware components by dragging labels onto a diagram. On Core 2, expect PBQs around configuring Windows settings, setting file permissions, and following the malware removal process.

Building a Study Plan

Most people need 8-12 weeks total for both exams. Whether you take them back-to-back or space them out depends on your background. If you've worked in IT support, a lot of Core 1 will feel familiar and you can focus your time on Core 2. If you're coming from outside IT, give Core 1 the first 6 weeks and Core 2 the next 6.

For Core 1

• Weeks 1-2: Hardware identification and networking fundamentals. Memorize port numbers, cable types, and connector types. Get hands-on with hardware if you can; take apart an old computer.
• Weeks 3-4: Cloud and virtualization concepts. Set up a free-tier VM on any cloud provider or install VirtualBox locally. Practical experience here cements abstract concepts fast.
• Weeks 5-6: Troubleshooting practice and timed mock exams. Focus on the troubleshooting methodology and practice applying it to scenarios rather than jumping to solutions.

For Core 2

• Weeks 1-2: Operating system fundamentals. Practice Windows command-line tools in a VM where you can't break anything. Run through the Linux basics. Know the macOS equivalents for common tasks.
• Weeks 3-4: Security concepts and malware removal procedures. Memorize the removal steps in order. Study social engineering attack types and their countermeasures.
• Weeks 5-6: Troubleshooting and operational procedures. Take full-length timed practice tests. Review every wrong answer and track which domains need more work.

The Memorization Problem

A+ has more raw memorization than most CompTIA exams. Port numbers, cable specifications, connector types, command-line syntax, malware categories, troubleshooting steps in order. You can't reason your way to these answers; you either know them or you don't.

Spaced repetition is the most time-efficient method for this kind of material. The research is consistent: distributing your review sessions over time with increasing intervals produces better retention than cramming the same total hours into a shorter period. For A+ specifically, start memorization early and review daily in short sessions rather than weekly in long ones. Port numbers drilled for 10 minutes a day over 3 weeks stick better than port numbers crammed for 2 hours the night before.

Flashcards work, but only if you're honest about which cards you know. Flipping past a card because you "sort of remember it" defeats the purpose. If you can't state the answer before flipping the card, it goes back in the pile.

Test Day

Both A+ exams are administered at Pearson VUE test centers or via online proctoring. Arrive early. Bring two forms of ID. You get a dry-erase board or sheet at the testing center; use it.

Before you start answering questions, spend 2-3 minutes writing down everything you've been cramming on the dry-erase board: port numbers, troubleshooting steps, cable specs, whatever you're afraid you'll forget under pressure. This brain dump costs you a few minutes but saves you from blanking on recall items later in the exam when fatigue sets in.

Remember the PBQ strategy: flag them, do multiple-choice first, come back. Manage your time actively. With 90 questions in 90 minutes and PBQs mixed in, you need to move through the standard questions at about 45-50 seconds each to bank time for the simulations.