A+ Core 1 vs Core 2: What Actually Changes Between the Two Exams

Every A+ candidate eventually asks the same question: if I have to pass both, why are they two separate exams? The honest answer is that CompTIA A+ covers so much ground that a single 90-question test could not sample it fairly. So they split it — and the split is not arbitrary.

Core 1 (220-1201) is the physical and connective half: hardware, mobile devices, networking, and the troubleshooting that goes with them. Core 2 (220-1202) is the logical and procedural half: operating systems, security, software problems, and how a professional actually conducts themselves. You need both, but you should not study them the same way.

What the two exams share

The format is identical, and that matters for your preparation. Both are up to 90 questions in 90 minutes. Both mix multiple-choice with performance-based questions — the simulated tasks where you configure something or diagnose a fault. Both require a scaled score to pass, and both are unforgiving on time. If you have trained your pacing for one, that skill carries directly to the other.

They also share a troubleshooting methodology — identify, theorise, test, plan, verify, document. It appears in Core 1 for hardware and in Core 2 for software, and it is worth memorising as a sequence because CompTIA loves to ask which step comes next.

Where they split apart

Look at the domain weightings side by side and the personalities of the two exams jump out.

That even spread is the single biggest difference in how you prepare. In Core 1 you can gamble a little: master hardware and troubleshooting and you are most of the way there. In Core 2 that gamble does not exist. Security and operating systems are 28% each, but software troubleshooting and operational procedures are 23% and 21% — skip either and you have thrown away a fifth of the exam.

Which one to sit first

Sit Core 1 first. Not because it is easier — it is not — but because its hardware and networking foundation makes several Core 2 topics land more cleanly. Understanding how storage physically works helps when Core 2 asks about drive encryption. Knowing your ports from Core 1 makes the Core 2 security questions about closing services obvious.

The trap in each exam

Core 1's trap is the performance-based hardware questions. You can recite RAM types all day and still freeze when a sim shows you a motherboard and asks you to identify the failed component. Study with images and real teardown videos, not just bullet lists.

Core 2's trap is the command line. It will drop you at a Windows prompt and expect you to type the right command without a menu to click. There is no partial credit for knowing roughly what sfc does.

Core 2 — know these coldsfc /scannow            # repair protected system files
chkdsk C: /f /r         # fix disk errors, recover data
gpupdate /force         # reapply Group Policy now
ipconfig /flushdns      # clear stale DNS entries
net user /domain       # list domain accounts

Treat them as two exams with two temperaments and you will pass both. Treat them as one big exam split in half and Core 2 will surprise you.

How to split your study time between them

Because the two exams have different personalities, they deserve different tactics. Core 1 rewards depth in a few areas: if you truly master hardware and the troubleshooting method, you have covered over half the exam and can afford to be merely competent on virtualisation and cloud. That makes Core 1 a good candidate for front-loading — hit the heavy domains first while your energy is highest.

Core 2 does not allow that luxury. With four domains at 28, 28, 23 and 21 percent, there is no small domain to sacrifice. The right approach is even coverage with a deliberate extra pass on Operational Procedures, precisely because it is the domain people underrate. Treat Core 2 as a breadth exam and Core 1 as a depth exam, and you will allocate your hours where they actually pay off.

The overlap that saves you time

The two exams are not sealed off from each other, and the overlaps are gifts. The troubleshooting methodology — identify, theorise, test, plan, verify, document — appears in both, so learning it once earns marks twice. Networking knowledge from Core 1 makes Core 2's security questions about closing ports and services almost free. Understanding storage hardware in Core 1 makes drive-encryption and data-destruction topics in Core 2 intuitive. Study Core 1 properly and you have quietly done groundwork for Core 2 — which is the real reason to sit them in that order rather than the reverse.

One certificate, two mindsets

It helps to think of Core 1 as the exam for the hands and Core 2 as the exam for the head. Core 1 is where you prove you can work with the physical machine — open it, diagnose it, connect it, and reason about why it will not power on. Core 2 is where you prove you can manage the logical machine and behave like a professional around it — secure the operating system, fix the software, follow the procedures, communicate with the customer. Passing both is what makes A+ respected: it certifies that you are competent with the tangible and the intangible sides of the job, which is exactly the blend an entry-level IT role demands. Candidates who internalise this framing stop treating the second exam as "more of the same" and start preparing for the genuinely different challenge it is — and that shift in mindset is worth more than any single fact on the blueprint.