CompTIA A+ is one certification, but the current version is earned by passing two separate exams: Core 1 (220-1201) and Core 2 (220-1202).
That split matters when you study.
Core 1 is not simply the first half of one giant topic list, and Core 2 is not the second half. Each exam has its own domains, weights, passing score, and style of decisions.
A learner who treats all nine domains as one pile can spend a lot of time reviewing material that belongs to the other exam while neglecting the one that is actually scheduled next.
The useful question is not which core matters more? You need both to earn A+.
The useful question is what does this core expect me to know and do, and where am I weakest?
2. Core 1 and Core 2 Are Two Halves of A+
The current A+ V15 series uses:
- Core 1: 220-1201
- Core 2: 220-1202
CompTIA requires both exams to earn the certification.
That does not mean the two exams should share one undifferentiated study plan. Core 1 concentrates more heavily on devices, networking, hardware, virtualization and cloud concepts, and hardware or network troubleshooting. Core 2 shifts toward operating systems, security, software troubleshooting, and operational procedures.
A simple way to remember the difference is:
Core 1 leans toward the device and the connection. Core 2 leans toward the operating environment and the user.
That is a study shortcut, not a hard boundary. The exams overlap because real support work overlaps.
3. Core 1 vs. Core 2 at a Glance
| Area | Core 1 | Core 2 |
|---|---|---|
| Exam | 220-1201 | 220-1202 |
| Domains | 5 | 4 |
| Center of gravity | Devices, networking, hardware, cloud concepts, physical and network troubleshooting | Operating systems, security, software troubleshooting, support procedures |
| Largest domain | Hardware and Network Troubleshooting, 28% | Operating Systems and Security, 28% each |
| Typical study question | What component, connection, or symptom fits this situation? | What configuration, tool, control, or procedure fits this situation? |
| Cert Happens guide | Core 1 Study Guide | Core 2 Study Guide |
Both exams can include multiple-choice and performance-based questions. Both reward knowing what to do with a concept rather than only recognizing the term.
4. What Core 1 220-1201 Covers
Core 1 has five domains:
| Domain | Weight | Main study focus |
|---|---|---|
| Mobile Devices | 13% | Laptop and mobile hardware, accessories, connectivity, synchronization, and support. |
| Networking | 23% | Ports, protocols, wireless, network devices, addressing, services, internet connections, SOHO configuration, and tools. |
| Hardware | 25% | Cables, memory, storage, motherboards, processors, power, peripherals, printers, and compatibility. |
| Virtualization and Cloud Computing | 11% | Virtual machines, hypervisors, containers, cloud models, and cloud characteristics. |
| Hardware and Network Troubleshooting | 28% | Use symptoms and evidence to isolate device, storage, display, mobile, network, and printer failures. |
Core 1 rewards being able to connect a physical or network symptom to the subsystem that deserves attention.
A laptop that will not charge, a printer that produces repeated defects, a desktop that fails during startup, a wireless client that cannot reach the gateway, and a storage device that is not detected all begin with different evidence.
The largest single Core 1 domain is troubleshooting, but troubleshooting depends on the earlier domains. You cannot diagnose a memory problem if memory types and compatibility are still unfamiliar. You cannot narrow a Dynamic Host Configuration Protocol (DHCP) failure if basic addressing is unclear.
That is why Core 1 study should not become a list of symptoms detached from the hardware and networking underneath them.
5. What Core 2 220-1202 Covers
Core 2 has four domains:
| Domain | Weight | Main study focus |
|---|---|---|
| Operating Systems | 28% | Install, configure, navigate, and support Windows, macOS, Linux, mobile systems, applications, and common administrative tools. |
| Security | 28% | Accounts, permissions, endpoint and network hardening, malware, data protection, physical security, and common threats. |
| Software Troubleshooting | 23% | Use symptoms and evidence to isolate operating-system, application, browser, mobile, and security problems. |
| Operational Procedures | 21% | Documentation, change management, backups, safety, professionalism, scripting, remote support, privacy, and support processes. |
Core 2 is more evenly weighted than Core 1. No domain is small enough to treat as an afterthought.
It also tends to move closer to the operating system and the support process. A question may ask which Windows tool provides the evidence you need, which account should receive a permission, what a malware symptom suggests, what backup action is appropriate, or what should be documented after a change.
Definitions still matter. The exam becomes easier when every definition is attached to a job.
6. Where Core 1 and Core 2 Overlap
The split is useful, but real systems do not respect exam boundaries.
Troubleshooting appears in both
Core 1 has a dedicated Hardware and Network Troubleshooting domain. Core 2 has Software Troubleshooting, and troubleshooting also appears throughout operating-system and security scenarios.
The difference is usually what layer owns the symptom.
A computer with no network connection may involve a cable, wireless signal, network adapter, addressing problem, operating-system setting, firewall, malware, or account policy. The same incident can touch concepts from both cores.
Security appears in both
Core 2 has the dedicated Security domain, but Core 1 still expects safe device and network decisions. Wireless settings, firmware, physical hardware, network devices, and mobile support all have security consequences.
Mobile devices appear in both
Core 1 emphasizes mobile hardware, accessories, connectivity, and synchronization. Core 2 can involve mobile operating systems, application behavior, security, and troubleshooting.
The point is not to force every topic into one mental box. The point is to know which exam objective is testing the decision in front of you.
7. Which Core Feels Harder?
There is no useful universal answer.
Core 1 may feel easier if you have built computers, replaced components, configured home networks, worked with printers, or already understand common ports and network devices.
Core 2 may feel easier if you spend a lot of time in Windows, manage accounts and permissions, use command-line tools, troubleshoot applications, work with security settings, or follow support procedures at work.
The reverse is also common.
Someone who is comfortable installing hardware may discover that Windows tools and operational procedures require more deliberate study. Someone who works in software support all day may need more time with cables, storage interfaces, printer technologies, or wireless standards.
Use that difference instead of fighting it. Your study plan should reflect your gaps, not somebody else's claim that one core is always harder.
8. How to Decide Where to Focus Your Study Time
Start with two pieces of evidence: the official domain weights and your own performance.
Use weights to understand exam emphasis
For Core 1, three large areas dominate the blueprint:
- Hardware and Network Troubleshooting: 28%
- Hardware: 25%
- Networking: 23%
That makes weak hardware or networking knowledge expensive because it also makes troubleshooting harder.
Core 2 is more balanced:
- Operating Systems: 28%
- Security: 28%
- Software Troubleshooting: 23%
- Operational Procedures: 21%
If one Core 2 domain is weak, there is no tiny domain elsewhere that can safely absorb the loss.
Let practice results change the plan
Do not divide study time only by percentages.
If Mobile Devices is 13% of Core 1 but you miss nearly every mobile scenario, it deserves attention. If Hardware is 25% but you are consistently strong there, repeating hardware flash cards may be a poor use of another evening.
Use a fresh A+ practice session for the core you are studying. Review misses by domain, then ask why the answer failed:
- Did you not know the concept?
- Did you confuse two similar technologies?
- Did you miss a clue in the scenario?
- Did you know the definition but not the next action?
- Did you change your answer because the wording made you uncertain?
That diagnosis tells you what kind of review you need.
9. Use the Cert Happens Resource That Matches the Gap
The A+ resources are deliberately separated by core. Use the complete study guide when the topic is unfamiliar, a Quick Review when the concept is familiar but distinctions are fuzzy, practice when you need to apply the material, and Final Review when the exam scope is already familiar.
Core 1 resources
- Core 1 220-1201 Study Guide for the complete five-domain roadmap.
- Hardware and Network Troubleshooting Quick Reference for symptom-to-cause and next-check decisions.
- Hardware, Cables, Storage, and Printers Quick Reference for compatibility and component decisions.
- Networking, Wireless, and SOHO Quick Reference for ports, wireless, network services, devices, and small-office networking.
- Core 1 Final Review when the material is familiar and you want a compact whole-exam refresher.
- A+ Practice Test and choose Core 1 for a randomized 220-1201 session.
Core 2 resources
- Core 2 220-1202 Study Guide for the complete four-domain roadmap.
- Operating-System Tools and Commands Quick Reference for Windows, macOS, Linux, commands, and recovery tools.
- Security, Malware, and Software Troubleshooting Quick Reference for controls, malware response, hardening, and software symptoms.
- Operational Procedures, Backup, and Remote Support Quick Reference for change control, backups, safety, privacy, scripting, remote support, and artificial intelligence (AI) use.
- Core 2 Final Review when the material is familiar and you want a compact whole-exam refresher.
- A+ Practice Test and choose Core 2 for a randomized 220-1202 session.
Not sure what to open next? If the topic still feels new, use the study guide. If you know the topic but keep mixing up close choices, use the matching Quick Review. If you think you know it, test that assumption with a fresh practice set.
10. A Practical Study Sequence for Either Core
A simple sequence works for both exams:
- Read the objective scope. Know which exam you are studying and what its domains contain.
- Use the full study guide. Build enough understanding to explain the topic and perform the basic task.
- Use Quick Reviews selectively. Repair close comparisons, commands, symptoms, and common decision points.
- Take a fresh practice set. Use the result as evidence, not as a score to memorize.
- Return to weak domains. Review the reason for each miss and practice the underlying skill.
- Use Final Review late. It is a refresher, not a replacement for learning unfamiliar material.
- Take another fresh practice set. Check whether the weakness actually improved.
That sequence also helps keep Core 1 and Core 2 from blending together.
11. Which Core Should You Study First?
If you already have an exam scheduled, the answer is easy: focus on that core and keep the other one out of the way until you are ready for it.
If you are beginning A+ from scratch, Core 1 can be a natural starting point because devices, hardware, networking, and physical troubleshooting provide context that appears again in support work. That does not make Core 1 more important, and it does not make Core 2 a continuation of the same blueprint.
Whichever core you start with, finish building a usable mental model for that exam before constantly switching between both sets of objectives.
The shared concepts will still help you later. The separate study plan keeps you clear about what the exam in front of you actually measures.
12. The Difference That Matters
Core 1 asks you to understand and troubleshoot the devices and connections people depend on.
Core 2 asks you to operate, secure, troubleshoot, and support the software environment and procedures around those systems.
There is overlap because real IT support does not have a Core 1 side of the desk and a Core 2 side of the desk.
For studying, though, the separation is useful. Know which exam you are preparing for, use its domain weights to understand emphasis, use your practice results to find personal weak spots, and open the CH resource that matches the gap.