Core 2 is the job, not the hardware shelf
Core 1 asks what the parts are. Core 2 asks what you do when a user cannot log in, a browser keeps opening the wrong home page, or a ticket says "the printer works for everyone except accounts". The exam still checks knowledge, but most items are framed as a task. Read the symptom first, then the constraint, then the answer.
The four domains are operating systems (28%), security (28%), software troubleshooting (23%) and operational procedures (21%). Operating systems and security are tied for the lead, so do not treat security as a guest chapter.
Take Core 1 first
CompTIA requires both exams for the A+ certification. Core 1 gives you the hardware vocabulary and the networking basics that Core 2 assumes. If you have not passed Core 1, finish it first. If you already work a help desk and know the hardware, you can start Core 2 and fill gaps as they appear.
Six weeks at about an hour a day
- Week 1: Windows from the inside. User accounts, NTFS permissions, services, Event Viewer, Task Manager, Resource Monitor, Registry basics. Practice the tools until you can name the one that answers a symptom.
- Week 2: Command line by job. Learn commands in groups: disk (diskpart, chkdsk), boot (bootrec, bcdedit), files (robocopy, xcopy), network (ipconfig, ping, tracert, netstat), permissions (icacls), system files (sfc, dism). For each, write one sentence starting "Use this when...".
- Week 3: macOS and Linux at the support level. Finder and Disk Utility, users and permissions, terminal basics, package management concepts. You do not need to become a Linux admin. You need to recognise the equivalent task on each OS.
- Week 4: Security. Malware types, removal order, social engineering, wireless security, browser security, least privilege, MFA, encryption, disposal. Security is 28% and it is full of scenario questions.
- Week 5: Software troubleshooting. Application crashes, compatibility, malware symptoms, mobile app issues, Windows update failures. Pair each symptom with the first diagnostic step, not the final fix.
- Week 6: Operational procedures and simulations. Safety, environmental controls, privacy, communication, scripting basics, change management. Then two timed mixed sets and a review of every miss.
The malware removal order
The exam likes sequence questions. Memorise and rehearse this order:
- Investigate and verify the symptoms.
- Quarantine the system.
- Disable System Restore in Windows if the procedure calls for it.
- Remediate: update definitions, scan, remove.
- Re-enable System Restore and re-scan.
- Educate the user.
Different textbooks phrase the middle steps differently, so learn the logic: identify, isolate, remove, verify, prevent repeat. If a question offers "reimage immediately" before any investigation, it is usually a distractor.
The ticket mindset
Core 2 operational procedures are free points if you read like a technician. When a question describes a user who is upset, the best answer usually includes active listening and a clear next step, not a technical shortcut. When it asks about safety, the cautious answer wins: power off, unplug, follow disposal rules, wear the right protection.
Privacy matters too. Do not remote into a user's machine without consent. Do not discuss a ticket in a public channel. Do not keep credentials in a note. These are not soft skills bolted on; they are scored objectives.
A study day that fits a job
- 10 minutes: flashcards for commands and ports.
- 25 minutes: one domain set, with confidence marked honestly.
- 15 minutes: one lab or simulation. Reset it and do it again from memory.
- 10 minutes: turn misses into notes, then stop.
The subnet drills and ports sheet are useful even on Core 2, because networking questions do not disappear. The A+ Core 1 plan covers the other half of the certification.
Practise with labs and PBQs
Core 2 is the half of A+ where labs and questions converge: a ticket is a procedure with a clock. The 220-1202 pack holds 39 performance-based questions and 69 labs, all graded on the state you leave behind, and the counts come from the live catalogue rather than a landing page.
Work them by domain weight. Weeks 1 and 4 are operating systems and security, which are tied at 28%, and both are ticket-heavy: an account that must be unlocked and reset, a policy that must actually apply, a machine that must stop starting the wrong thing. Week 5 is software troubleshooting, where the exam asks for the first diagnostic step rather than the final fix, so practise stopping after one change and one check. Week 6 is procedures, which labs teach better than reading: documentation, change control, and the note nobody wants to write.
The 220-1202 lab catalogue sorts by objective, and the labs hub shows the Core 1 bench tasks if you have not sat that exam yet. Run each task twice: the first pass teaches the steps, the second pass is where you notice the one you skipped. If you are still deciding what to buy for each core, the A+ resources comparison covers the platforms and their honest limits.
Book when the pattern is boring
Book when two fresh timed sets land where you want them and the explanations feel obvious after the fact. Not when you have memorised the same set. The app's readiness view uses fresh questions for that reason. If you keep scoring well on repeats and poorly on new items, you are recognising, not learning.