A+ Core 1: the biggest domain is not hardware, and how to split 70 hours

Candidates who love hardware often study the part that carries the second-most marks.

The five domains

The weights add to 100%, and the objectives add to 27. Troubleshooting has just six objectives yet the biggest weight, 28%, while hardware needs eight for 25%.

A 70-hour split

Take a plan of 70 hours for Core 1, which fits inside the 60 to 90 hours per core that CredenTrek assumes. Applying the weights gives:

That adds up to 70. Treat it as a starting point and move hours towards your lowest self-ratings.

Learn the order of the method

The published method has four steps: identify the problem, establish and test a theory, plan and fix, then verify and document. CompTIA states that the method itself is not tested. It is still a reliable way to think when a question asks what to do first or what to do next.

Many candidates memorise ports and cables well, then lose marks on the order of steps. A question may describe a clear symptom and offer four plausible actions. Only one is right at that moment.

Practise with faults you make

You will not learn this from reading. Use a spare machine and create faults on purpose: unplug a cable, change a setting, pull a memory module (machine off and unplugged, ESD strap on), then power on and see what the machine does. For each fault, write a line in a log:

After ten entries, you will have a feel for the order that no flashcard gives.

The cheap fix comes first

Consider a desktop that restarts under load, with dust packing the fans. A technician who orders a new power supply has skipped the cheaper theory. Clean first, test, then escalate. The same logic runs through mobile, network and hardware questions.

What to rehearse in the other four domains

Networking is where ports and protocols live, and Remote Desktop on 3389 is a good test of recall: can you say the number without the answer options in front of you? Mobile devices and virtualisation are smaller, so a short, steady routine of 20 minutes a day suits them better than an occasional long session. Hardware rewards handling the parts, which is another reason to keep the spare machine on the table.

Pair it with the other domains

Hardware, networking and mobile topics also appear inside the troubleshooting domain. A network fault is a networking question and a troubleshooting question at once, so practise the two domains together.