Marcus wanted his A+ Core 2 done before the end of the month. He had been drilling questions for weeks, and his last three full practice tests came back at 79, 80, and 82 percent. On paper, that looks like someone ready. He booked the exam, sat it, and missed the cut. When he pulled his practice history apart afterward, the reason was sitting there the whole time: his Security questions were landing at 68 percent while everything else carried him into the low 80s. The overall number was hiding a domain that was quietly failing him.
Marcus is made up, but the numbers you are about to see are the kind I watched wreck real attempts for years before I ever taught anyone to study. I came off a help desk, not out of a classroom, so this is the most common self-inflicted wound I know: people trust the big number at the top of the results screen. That number is an average, and averages lie about exactly the thing you need to know. What follows is the method I wish Marcus had run before he paid for his seat. It is four steps, it uses his full spread of numbers, and it points you at the one domain worth most of your remaining time.
Short answer: The exam is not graded as one flat pool of questions. Each CompTIA domain carries a fixed share of the test, and your weighted result is what decides pass or fail.
CompTIA A+ Core 2 (220-1202) sets its passing mark at 700 on a scale of 900, which works out to roughly 78 percent, per the official CompTIA A+ certification page. Core 1 (220-1201) passes at 675 out of 900. Those are scaled scores rather than raw percentages, but the practical target most people aim for on practice tests is mid-80s and up.
Here is the trap. If one heavily weighted domain sits well below your average while two lighter ones sit above it, the average still looks fine. The exam does not average the way your confidence does. A weak domain that happens to be worth a quarter of the test can sink you even when your headline score reads like a pass.
Two definitions before the steps, because the rest of this leans on them.
Domain mastery is your percent correct inside a single CompTIA domain, scored on its own, separate from every other domain.
Your Pareto domain is the one domain whose improvement would raise your pass probability more than any other. The name comes from the Pareto principle, the 80/20 idea that a small share of causes drives most of the results. In exam prep, one domain usually holds most of your risk.
Step one: gather enough data. Step two breaks the score into domains. Step three weights the domains. Step four spends your hours where the points are. Marcus runs through all four below.
One practice test tells you almost nothing about a single domain. A domain might only hold ten or twelve questions on one test, and a couple of unlucky guesses can swing that domain 15 points in either direction. That is noise, not a signal.
Larger samples give steadier estimates, which is the entire reason sample size matters. Take three full-length tests from the same question bank, and you pool roughly 250 to 270 questions, which spreads 60 to 75 questions across each domain. That is enough that a low domain score actually means something.
Two rules keep the sample honest. Use fresh questions each time, because retaking a test you have already seen inflates your score on memory, not knowledge. And take the full length under time, because a rushed domain and a relaxed domain behave like different animals.
Marcus took three fresh 90-question tests. Pooled together, that gave him 271 questions to work with.
Now split those pooled questions by domain and score each one on its own. This is where a raw results screen stops being enough. You want a per-domain performance breakdown, and ideally, the ability to run questions from one domain at a time so you can gather a clean sample for the domain you suspect is weak.
Not every prep tool shows this. Some only hand you a final score. The ones worth using report accuracy per domain and let you filter by objective. Crucial Exams is one of the platforms built around that exact workflow. Its CompTIA A+ Core 2 practice test runs on an exam-aligned question bank of around a thousand questions, with domain filtering on custom-timed tests and a per-domain breakdown after each attempt, so you can look at Security on its own instead of buried inside an average. That per-domain view is the raw material for everything that follows. Whatever tool you pick, the requirement is the same: it has to report your accuracy inside each domain, not just overall.
Here is what Marcus's pooled 271 questions looked like once split out:
Weight those by the exam blueprint, and you land back on his 80 percent overall. Every domain looks survivable except one. Security is the outlier, and it is not a small domain.
A low domain score only matters in proportion to how much of the exam it controls. So multiply, do not eyeball. Take each domain's gap below your target and multiply it by that domain's weighting. The biggest product is your Pareto domain.
These are the current V15 weightings, straight from the objectives:
|
Exam |
Domain |
Weighting |
|---|---|---|
|
A+ Core 1 (220-1201) |
Hardware and network troubleshooting |
28% |
|
A+ Core 1 (220-1201) |
Hardware |
25% |
|
A+ Core 1 (220-1201) |
Networking |
23% |
|
A+ Core 1 (220-1201) |
Mobile devices |
13% |
|
A+ Core 1 (220-1201) |
Virtualization and cloud computing |
11% |
|
A+ Core 2 (220-1202) |
Operating systems |
28% |
|
A+ Core 2 (220-1202) |
Security |
28% |
|
A+ Core 2 (220-1202) |
Software troubleshooting |
23% |
|
A+ Core 2 (220-1202) |
Operational procedures |
21% |
Set a target of 90 percent, comfortably above the pass line, and run Marcus's gaps:
Security scores 6.16. That is more than the other three domains added together, and roughly 63 percent of all the score lift available to him. That is his Pareto domain. It is both far below target and worth 28 percent of the exam, which is the worst possible pairing.
Add up the lift values: 1.40 plus 6.16 plus 1.84 plus 0.42 is 9.82. Turn each one into a share of your study time.
Marcus had roughly 20 study hours left before a retake. That math put about 12 of them into Security, four into Software Troubleshooting, three into Operating Systems, and one skim pass over Operational Procedures. Notice he does not stop touching his strong domains. He just stops pouring time into a domain already sitting at 88 percent, where another hour buys him almost nothing.
He spent two weeks front-loading Security: port numbers, malware removal steps in the right order, social engineering types, and the Windows security settings he had been guessing at. Then he re-ran the diagnostic with three fresh tests.
Security climbed from 68 to 84 percent. Nothing else moved much, because he barely touched it. His new weighted overall landed near 85 percent, but the number that mattered was Security clearing the bar with room to spare. He passed the retake. Same brain, same weeks of effort, different target.
Sometimes you pour hours into a domain, and it stalls at the same score. That usually points to one of three things, and none of them gets fixed by grinding more questions.
You might be memorizing answers instead of concepts. Switch to a study mode that shows the explanation for every question, right or wrong, and make yourself say out loud why the wrong options are wrong.
The domain might be hands-on by nature. Security and troubleshooting reward doing over reading. Build a cheap lab, break something, fix it. Performance-based questions on the real exam simulate that kind of task, so rehearse the task, not the trivia.
Or your weak domain might really be a weak sub-objective hiding inside it. Filter down to the specific objective, sample it, and you will often find that two topics out of six are dragging the whole domain down. Regulars on r/CompTIA will tell you the same thing: the "hardest domain" is usually two stubborn objectives wearing a domain's name.
