CompTIA A+: Why You Should Take Core 2 Before Core 1

Cedric: Hello there! Grab a seat, get comfortable—maybe a fresh cup of tea? I’ve been looking at something today that really flips the script on how people start their tech careers. You know, most people who decide to get their CompTIA A+ certification just follow the numbers. They take Core 1, then they take Core 2. It sounds logical, right? One comes before two. But what if I told you that for a lot of people, that’s actually the harder way to do it?

Kate: It’s so true. We’re conditioned to think linearly—step A, then step B—but in the IT world, the "right" order is often about where your brain already lives. If you’re more of a "software and people" person than a "screwdrivers and motherboards" person, starting with Core 1 can feel like hitting a brick wall right at the starting line.

Cedric: Exactly! And that’s the tension we’re diving into today. The A+ is actually two distinct exams—the 220-1201, which is Core 1, and the 220-1202, which is Core 2. You have to pass both to get the badge, but nobody says you have to do them in order. In fact, as of mid-2026, the price for each attempt has gone up to $274. That’s over 500 dollars to get certified. You really don't want to fail because you chose an order that fought against your natural strengths.

Kate: That’s a huge point. If you’re paying nearly $300 an attempt, you want the path of least resistance. Core 1 is often called the "hardware-and-wires" exam, while Core 2 is the "software-security-and-procedures" exam. For some, diving into the abstract world of security and operating systems in Core 2 first is actually the smarter, more strategic move. It’s about building momentum.

Cedric: I love that idea of a "strategic flip." It’s a bit contrarian, isn't it? Challenging the status quo right away. But before you decide to jump straight into the deep end of software troubleshooting, we should probably look at what these two exams actually represent. Why is there even a split in the first place? Let's pull back the curtain on the "Hardware versus Software" divide and see where you might actually fit.

Kate: To really understand why you might want to take Core 2 first, you have to look at the "clean split" CompTIA created with these exams. It’s not just a random pile of info. Core 1, or the 220-1201, is very tangible. It’s the physical layer of IT—things you can touch, like motherboards, RAM, and printers. If you’ve ever built a PC, a lot of this will feel like home.

Cedric: Right, it’s the "how things work" phase. But then you have Core 2, the 220-1202, which moves up the stack. It’s more about the "what you do with it" phase. We’re talking about Windows, macOS, Linux, and—this is a big one—security and operational procedures. It’s much more abstract. You aren't plugging in a cable; you're managing a change request or hunting down malware.

Kate: And that’s where the difficulty gap starts to show. Even though they’re both 90-minute exams with up to 90 questions, the passing scores are different. You need a 675 out of 900 for Core 1, but for Core 2, the bar is higher—you need a 700. That higher threshold is a signal. CompTIA is saying, "We expect a higher level of precision when it comes to software and security."

Cedric: That’s fascinating—a higher bar for the "invisible" stuff. It reminds me of how Core 2 is often described as "scenario-based." In Core 1, a question might be "what port does DHCP use?" You either know it’s 67 and 68, or you don’t. But in Core 2, you might get a scenario where a user’s account is compromised, but they have a deadline in twenty minutes. What do you do first?

Kate: Exactly! It’s a judgment call. Do you fix the tech or follow the security protocol? People with a background in customer service or "soft" IT often find those scenarios much more intuitive than memorizing the pins on a DDR5 RAM stick. If that sounds like you, Core 2 might actually be your "easy" win, even if the stats say it's the harder test.

Cedric: It’s interesting how we assume the "foundation" has to be the physical hardware. But in 2026, so much of what we do is in the cloud or virtualized. Maybe the "real" foundation for a modern IT worker is actually the software and the procedures. If you start there, does the hardware stuff just... fall into place later? It’s a gamble, certainly, but for the right person, it’s a gamble that pays off in confidence.

Kate: Let’s talk about that confidence factor. There is a real psychological edge to passing the exam you find "easier" first. If you’re someone who spends all day in Windows settings or resetting passwords, Core 2 is going to feel like a conversation you’re already having. Passing that first gives you a "win" in the bank before you have to go back and memorize T568A versus T568B wiring standards for Core 1.

Cedric: I can see that. It’s like starting a marathon at the halfway point because you like the scenery better there. But there’s a catch, right? If you skip Core 1, aren't you missing the ground underneath your feet? The experts often warn that Core 2 troubleshooting scenarios actually assume you already know the networking and hardware basics from Core 1.

Kate: That’s the "Missing Basics" risk. Imagine a Core 2 question about a user who can’t connect to a network. To solve that "software" problem, you might need to understand DNS or DHCP, which are technically Core 1 networking topics. If you take Core 2 first, you’re basically trying to solve a puzzle while some of the pieces are still in the other box.

Cedric: So it’s a tradeoff between "I’m good at this software stuff, let’s get a win" and "I might be confused because I don't know how the network actually moves the data." It’s a bit like learning to drive a car by starting with the GPS and the infotainment system before you learn how the engine works. You can do it, but you might feel a bit lost when the car won't start.

Kate: That’s a perfect analogy. And there’s also the "momentum" argument. If you struggle with the hardware—maybe you find printers and RAID levels incredibly dull—starting with Core 1 might burn you out before you even get to the stuff you actually enjoy in Core 2. Flip the order, and you’re studying the "fun" stuff first to build that habit of sitting down to learn.

Cedric: It really comes down to whether you’re okay with a bit of "fragmented" learning. You’ll see terms in Core 2 that you haven't officially studied yet. But for a lot of people, especially those already working a help desk or in a support role, those terms aren't "new"—they’re just part of the job. So, the risk of "missing basics" is much lower for them. It makes you wonder: is the "standard" order just a relic of how we used to teach IT?

Kate: It’s a really provocative question. Think about where IT is in 2026. We’re dealing with AI-assisted troubleshooting, Zero Trust security architectures, and software-defined networking. These are all Core 2-heavy concepts. The days of needing to know the exact voltage of a power supply are becoming less central to the average IT job than knowing how to navigate a command line or manage a security breach.

Cedric: Right, the "software-first" mindset. If you look at the domain weights, Core 2 puts a massive 28% on Operating Systems and another 28% on Security. That’s over half the exam right there. If you’re comfortable in those areas, you’re already sitting on a gold mine of points. Meanwhile, Core 1 spreads its weight across mobile devices, networking, and hardware troubleshooting. It feels a bit more scattered.

Kate: And the Core 2 material is what you actually do on day one of a help desk job. You’re going to be removing malware, fixing Windows update errors, and documenting your work—all Core 2 topics. You aren't usually cracking open a laptop to replace a screen on your first day. So, taking Core 2 first is almost like a "job readiness" first-pass.

Cedric: That’s a powerful argument for the flip. You’re prioritizing the skills that get you hired and keep you from getting fired in the first week. But we have to be honest—Core 2 is famously picky. It loves procedures. Like the seven-step malware removal process. You can’t just "know" it; you have to know it in the exact order CompTIA wants.

Kate: Oh, absolutely. That’s where the "Software-First" crowd can get cocky and fail. They think, "I know how to fix a computer," but they don't know the "CompTIA way." For example, step three of malware removal is "Disable System Restore," and step six is "Enable System Restore and create a restore point". If you get those out of order, it doesn't matter how good your technical skills are—you're getting the question wrong.

Cedric: It’s almost like a language you have to learn. Even if you speak "IT," you have to learn to speak "CompTIA." This brings us back to that uncertainty—is the "harder" exam actually easier if you’re already "speaking the language" at work? If you’re a software native, maybe the hardware foundation is the thing you should save for last, like a dessert you don't really want but have to finish to leave the table.

Kate: You mentioned the "CompTIA way," and we have to talk about the biggest hurdle in Core 2: Operational Procedures. It’s 21% of the exam. This isn't about technology; it’s about professionalism. Change management, documentation, safety, and even how you communicate with a distressed user.

Cedric: That sounds like the part of the exam most people would ignore until the night before. "Oh, I know how to talk to people, I’ll be fine." But is it that simple?

Kate: Definitely not. This is where the "fix it fast" people fail. In the real world, if a server is down and you can fix it in five minutes, you just do it. But on the Core 2 exam, the "correct" answer might be "Document the issue and follow the change management process". It feels counter-intuitive to a technician, but it’s exactly what the exam is testing: are you a professional or just a hobbyist?

Cedric: That’s a sharp distinction. It makes me think that taking Core 2 first is actually a great way to "un-learn" some of those bad habits early on. If you start with Core 1, you’re learning "this cable goes here." It’s very binary. But Core 2 forces you to think about the impact of your actions on the organization. It’s a much more "corporate" mindset.

Kate: Exactly. And that mindset applies to the command-line tools too. Core 2 expects you to know Windows commands like sfc /scannow for system files or chkdsk for drive errors, and even Linux commands like chmod for permissions. You can’t just wing it. If you take Core 2 first, you’re diving into the command line before you even fully understand the networking protocols that those commands are often interacting with.

Cedric: It’s a bit of a "trial by fire." If you can master the command line and the rigid operational procedures of Core 2, then going back to Core 1 and learning about USB-C standards or RAM types might feel like a breeze. But if you fail Core 2 because you couldn't wrap your head around the "professionalism" scenarios, it might crush your motivation to even look at Core 1.

Kate: It’s the ultimate "high risk, high reward" strategy. You’re tackling the "judgment" exam first. If you pass, you’ve cleared the highest hurdle in the A+ certification journey. But if you struggle with the abstract nature of it, you might find yourself wishing you had that solid "hardware and wires" foundation to lean on.

Cedric: So, if someone is listening to this and thinking, "Okay, I'm doing it. I'm taking Core 2 first," what does that actually look like? It’s not just a matter of swapping the books, is it? You’re using "unconventional study resources" at that point because most courses assume you're doing Core 1 first.

Kate: Right, you have to be your own architect. A standard 8-to-12 week plan usually spends the first half on Core 1. If you flip it, you need to be careful. You might want to spend 4 to 6 weeks purely on Core 2, but you’ll occasionally need to "peak" into Core 1 materials—especially the networking domain—to understand things like IP addresses or port numbers that pop up in Core 2 security questions.

Cedric: It’s like reading the middle of a mystery novel first. You have to occasionally flip back to the beginning to see who the characters are. But for the "software-native," this might actually be more engaging. You’re starting with the "why" and then going back to the "how."

Kate: And the study methods have to change. Core 1 is great for flashcards—"What is this port? What is this cable?" But Core 2 rewards "active recall" of processes. You should be walking through the malware removal steps while you’re brushing your teeth. You should be opening a virtual machine and actually running those ipconfig and netstat commands so they aren't just words on a page.

Cedric: I like that—making it "real." And we should mention the Performance-Based Questions, the PBQs. These are the "hands-on" simulations. On Core 2, you might be dropped into a simulated Windows environment and told to configure a firewall or fix a boot error. If you’re taking Core 2 first, you really need to spend time in these labs because you don't have the "easy" hardware identification questions to pad your score.

Kate: That’s a vital point. In Core 1, a PBQ might be "drag and drop the labels onto this motherboard diagram". In Core 2, it’s much more likely to be "solve this user's problem using only the command line." It’s more intense. But if you’re already a "power user," that might actually be where you shine. It’s all about playing to your strengths while being hyper-aware of the procedural traps CompTIA sets.

Cedric: It’s a very intentional way to study. It’s not for the casual learner. It’s for the person who says, "I want to master the hardest part of the job first." It’s a bold move. But as we’ve seen, the A+ is a journey of two halves, and there’s no rule saying you have to start at the bottom of the mountain if you’ve already got a helicopter to the midpoint.

Kate: Okay, so let’s get practical. How do you actually decide? Because "I like software" is a bit vague when $274 is on the line. Most experts suggest a diagnostic first. Don't guess where your weak spots are—take a practice test for both and see the "domain-level breakdown".

Cedric: That’s the "honest starting point." If you score a 40% on a Core 1 practice test but a 65% on Core 2, the choice is pretty obvious. You’re closer on Core 2, but you still need more study before it’s ready. Why would you spend six weeks learning about laser printer drums when you could spend four to six weeks polishing your security knowledge and get a whole exam out of the way?

Kate: Exactly! Here is a little checklist for taking Core 2 first. One: You already work in IT support or a help desk role. Two: You have a strong background in Windows or security—maybe you’ve even looked at Security+ material. Three: You find hardware concepts like RAID levels or RAM speeds incredibly difficult to memorize, and you need a "win" to keep your motivation up.

Cedric: And on the flip side, who should absolutely not do this? I’m guessing the "zero experience" beginner?

Kate: Spot on. If you’re brand new to IT, the traditional Core 1-then-Core 2 path is the "gold standard" for a reason. It builds the ladder one rung at a time. Jumping to Core 2 first when you don't know what a router actually does is just going to lead to frustration. You’ll be trying to learn "Zero Trust Architecture" without knowing what an IP address is.

Cedric: It’s a "know thyself" moment. Are you a "builder" or a "fixer"? Builders often love Core 1—putting the pieces together. Fixers often love Core 2—solving the puzzle of why things aren't working. If you’re a natural fixer, starting with the fixing exam might be the spark you need to finish the whole certification.

Kate: And remember, the goal isn't just a piece of paper. It’s about being a competent technician. Whether you take Core 2 first or last, you still have to master the material. The order is just a tool to help you get there without losing your mind—or your wallet—in the process.

Cedric: We’ve covered a lot of ground today. From the "hardware-and-wires" of Core 1 to the "software-and-scenarios" of Core 2. It’s funny, I started this thinking the order was just a formality, but it’s really a strategic decision that can change your whole experience of the certification.

Kate: It really is. And we haven't even touched on the "mix and match" rule. You have to pass both exams from the same version. Right now, in 2026, that’s the V15 series—220-1201 and 220-1202. If you pass Core 2 now, but wait so long that CompTIA retires the V15 series, your pass doesn't count toward the next version.

Cedric: Oh, that’s a huge "don't wait too long" warning! So, if you take the contrarian route and pass Core 2, you’ve got to keep the pressure on and knock out Core 1 before the series expires. It’s a commitment. But the payoff? Once you have both, that A+ badge is your "door-opener" for roles like Desktop Support or Junior System Admin, with salaries ranging anywhere from 40 to 75 thousand dollars depending on where you are.

Kate: It’s the entry ticket to the industry. And for many, that ticket is easier to get if they don't have to fight their own learning style. Whether you go 1-then-2 or 2-then-1, the key is that 8-to-12 week window of "second job" level focus. It’s going to be hard work either way.

Cedric: I think that’s the real takeaway. There is no "easy" path, only a "more compatible" path. It’s about finding the order that keeps you showing up to study every night when you’re tired. If that’s Core 2 because you love security, then go for it. Be the contrarian.

Kate: I love that. Don't be afraid to flip the script if it means you're more likely to cross the finish line. The IT world doesn't care which exam you took first once you have the certification on your resume. They just care that you know how to handle the "software, the people, and the procedures" that keep the world running.

Cedric: Well, we’ve reached the end of our little deep dive. It’s been quite a journey through the guts of the CompTIA A+, hasn't it? I’m left thinking about how often we just follow the "1, 2, 3" of life without asking if "2, 1, 3" might actually work better for us.

Kate: It’s a great lesson for IT and beyond. Strategy is about knowing your own strengths. If you're standing at the base of this mountain, don't just look at the path everyone else is taking. Look at your own map. Are you ready for the abstract challenges of Core 2? Or do you need the concrete foundation of Core 1 first?

Cedric: There’s no wrong answer, as long as it gets you to the top. So, as we wrap things up, I want you to think about your own "IT personality." Are you a "software-native" who’s been putting off the hardware stuff? Maybe this is your sign to tackle Core 2 first and get that momentum going.

Kate: Or maybe you’ve realized you do need those basics first. Either way, the most important step is just... starting. Take that diagnostic test. See where you stand. The data will tell you which way to go.

Cedric: Exactly. Trust the data, and trust your own learning style. Thank you so much for spending this time with us today. It’s been a blast exploring this with you.

Kate: It really has. Good luck with your studies—whichever core you choose to tackle first. We’re rooting for you!

Cedric: Take care, and we’ll be thinking of you when you’re sitting in that testing center. You’ve got this!