Short version: you're taking both. The CompTIA A+ Core 1 vs Core 2 question isn't really which exam to take — it's which one to take first, and how to split your prep time between them. The A+ credential requires passing both 220-1101 (Core 1) and 220-1102 (Core 2). No shortcuts, no "I'll just take the harder one."
So the real decisions are about ordering and emphasis. That's what this post is actually about.
What Each Exam Actually Covers
The split is cleaner than most two-part certs. Core 1 is the hardware-and-wires exam. Core 2 is the software-people-process exam.
Core 1 (220-1101) has five domains. In rough terms: mobile devices, networking fundamentals, PC hardware, virtualization and cloud basics, and hardware/network troubleshooting. Troubleshooting is the biggest slice at 29%, with hardware right behind at 25%. If you've ever cracked open a laptop, swapped RAM, set up a home router, or argued with someone about DHCP leases, a chunk of Core 1 will feel familiar before you even start studying.
Core 2 (220-1102) has four domains that weight very differently: operational procedures (31%), security (25%), operating systems (22%), and software troubleshooting (22%). Notice what's not on that list. No hardware domain. No networking domain. Core 2 assumes you already know that stuff and moves on to what you do with it — which is exactly why most people take Core 1 first.
If you want the official domain-by-domain blueprint, CompTIA publishes it on their exam page. No point re-typing it here.
A+ 220-1101 vs 220-1102: Where the Difficulty Actually Lives
Ask around on r/CompTIA or any IT subreddit and the consensus lands in the same place: Core 2 trips people up more often. I agree, but not for the reason most posts give.
The usual explanation is "Core 2 is scenario-based." That's true-ish but misleading. Both exams have scenarios. The real difference is that Core 2 scenarios are judgment calls without clean answers.
Core 1 scenario: a user can't reach a specific internal server, you've verified local connectivity, what do you check next? There's a technically correct answer rooted in how networking actually works.
Core 2 scenario: a user reports suspicious activity on their account, they need to finish a presentation in 20 minutes, what do you do first? Now you're weighing security policy, user impact, documentation, and escalation all at once. Multiple answers look reasonable. The exam wants the one that prioritizes the right thing in the right order, according to how CompTIA thinks about operational procedure.
That's where candidates stumble. People with hands-on tech backgrounds tend to default to the "fix it fast" answer. Core 2 often wants the "follow the procedure" answer — document it, escalate it, communicate with the user. It's an exam about being a professional IT worker, not just a technical one.
One pattern I've seen repeatedly: someone scores 85%+ on Core 2 practice tests on their first pass, walks into the real exam, and fails by 30 points. When they review their wrong answers, they realize they kept picking the technically sharpest response instead of the one that matched CompTIA's operational framework. That's a judgment gap, not a knowledge gap. It takes a different kind of studying to close — more reading of CompTIA's own material on procedures, fewer flashcards, more practice with explaining why the "correct" answer is correct even when it isn't the one you'd actually pick at work.
Which One to Take First
Core 1. Almost always Core 1.
A few reasons, in order of how much they actually matter:
The networking foundation in Core 1 makes Core 2's security domain click much faster. You can't really reason about network segmentation, firewalls, or wireless security if you're shaky on OSI layers and how DNS resolution works. Taking Core 1 first means Core 2's security material lands on prepared ground instead of floating in the air.
There's also a momentum argument. Core 1 is more learnable from a book and a practice question bank — the concepts are concrete and the answers crisper. Passing it first builds the confidence you'll need for the harder test. Flip the order, struggle with Core 2 out of the gate, and it's easy to convince yourself the whole A+ is too hard and stall out halfway through.
The one case I'd flip: if you already work help desk or MSP and your day is mostly Windows, password resets, and user support, Core 2 might be closer to your actual job than Core 1. Even then I'd still usually recommend Core 1 first — but the gap is smaller, and if Core 2 is the one you can schedule next week, take Core 2 next week.
How Long Between the Two
Most people need 4–6 weeks of focused study per exam, which puts the full A+ at 8–12 weeks. What that looks like in practice depends entirely on where you're starting from.
Zero IT background? Plan closer to 12 weeks. Core 1's hardware domain alone has a lot of memorization, and you'll want hands-on time — ideally an old desktop you can open up and poke at, or at minimum a virtualization setup so the OS material in Core 2 isn't purely theoretical.
One or two years of help desk or desktop support? You can probably compress it to 6–8 weeks total. You'll coast through some domains and have to slow down on others, usually Core 2's operational procedures, which (for whatever reason) doesn't come up much in day-to-day work but is 31% of that exam.
A tactical note on scheduling: don't book both exams up front. Book Core 1. Take it. Then book Core 2 based on how that went. Crushed Core 1 with a 780+? You can tighten the Core 2 timeline. Scraped by? Give yourself the extra time and actually use it. Your Core 1 certificate doesn't expire while you're studying for Core 2, and there's no bonus for finishing fast.
If you want a detailed plan for either half, LearnZapp has week-by-week breakdowns for Core 1 and Core 2. They're built around the domain weights above instead of giving every topic equal time.
Studying Both Without Burning Out
A few things that actually make a difference when you're running an 8–12 week plan across two exams:
Don't split study time evenly across domains. If troubleshooting is 29% of Core 1 and virtualization is 11%, your time should reflect that — not just because of scoring weight, but because troubleshooting pulls in knowledge from every other domain anyway.
Do your practice questions in smaller batches, with review. Answering 100 questions and skimming the explanations is worse than answering 30 and reading every explanation, including the ones you got right. The explanations teach you how CompTIA frames their thinking, and for Core 2, that framing is half the battle.
If you're working full-time, expect the last two weeks before each exam to feel like a second job on top of your first one. That's normal. It's also the window where most people either commit or drop off — and if you can push through the two weeks before Core 1, you've already proved to yourself you can do it again before Core 2.
(You can also start reviewing Core 2 material while you're still in Core 1 prep, especially the OS sections that lean on Core 1's networking content. Just don't let it distract from the exam in front of you.)
So What Should You Actually Do
If you're still reading, you've probably already got a sense of which exam is closer to your comfort zone. Take Core 1 first anyway unless you have a real reason not to. Build the 8–12 week plan around both exams from the start. Weight your time toward the high-percentage domains and your own weak spots, not evenly across topics.
And before you lock in that plan, it's worth finding out where you actually stand instead of where you think you stand. Most people are wrong about their weak spots — I've watched candidates swear they were rock solid on networking, then miss half the Core 1 networking questions on a diagnostic. Take a free A+ diagnostic — no signup, about 20 minutes, and you'll get a domain-level breakdown for both cores. That's the honest starting point.