Most candidates walk into CompTIA A+ Core 2 (220-1202) carrying the wrong mental model. Core 1 (220-1201) tested whether you could identify hardware, connect networks, and troubleshoot a machine that would not boot. Core 2 tests something quieter and, for many working technicians, more consequential: whether you can support a person whose computer, operating system, and security posture all need attention at the same time.
That shift matters because the study habits that passed Core 1 do not transfer cleanly. Memorizing connector types will not save you when a question describes a user who clicked a suspicious attachment, a workstation that now behaves strangely, and a ticket that needs both a fix and a record of what changed. Core 2 rewards technicians who think in workflows, not in flashcards.
The four domains, read as a workday
Core 2 is organized around operating systems, security, software troubleshooting, and operational procedures. Read as a checklist, that list sounds dry. Read as a workday, it is the order in which a real support job unfolds.
You start the day in the operating system: installing, configuring, and maintaining Windows, macOS, Linux, and mobile platforms, and knowing which tool belongs to which problem. Then security intrudes, as it always does — a phishing report, a malware symptom, a user who shared a password to be helpful. Then something breaks in software, and you have to decide whether the fault is the application, the OS, the driver, or the user profile. And through all of it, operational procedures govern how you document, escalate, communicate, and dispose of equipment safely.
Candidates who study the domains in isolation often stumble on questions that deliberately cross them. A single scenario can begin as a software problem, turn out to be a security incident, and end as a documentation requirement. Practicing that way — scenario first, domain second — is the single best preparation habit for Core 2.
Operating systems: know the differences that change the answer
Core 2 does not ask you to be an expert in four operating systems. It asks you to know the differences that change what you do next. Where does each OS keep its settings? Which command-line tools diagnose a network problem, a disk problem, or a service that will not start? How do you partition and format storage, manage users and permissions, and recover a system that will not log in?
The trap here is studying features instead of actions. You do not need to admire an OS; you need to operate it under pressure. When you practice, give yourself a broken state and a goal: a user cannot print, a drive is full, an update failed halfway. Work out the first three steps before you look up the answer. On the exam, the questions that look like trivia are usually testing exactly that sequence — the right tool, in the right order, for the stated symptom.
Mobile operating systems deserve the same treatment. Core 2 treats phones and tablets as endpoints to support, not as accessories: connectivity, synchronization, security settings, and the difference between a device problem and an account problem. If your study plan skips mobile, you are leaving easy marks on the table.
Security: the domain where technicians become the control
Security on Core 2 is practical, not theoretical. Expect questions about malware types and their symptoms, about social engineering in its many everyday forms, and about the controls that actually stop incidents: strong authentication, least privilege, patching, encryption, and sensible handling of sensitive data.
The most common failure mode is answering security questions like a policy document instead of like a technician. The exam wants the action that reduces risk right now, in this situation, for this user. That might be isolating a machine, disabling an account, or verifying a sender before clicking anything — not writing a new policy. When two answers both sound secure, choose the one that fits the scenario's constraints: who is affected, what access is at stake, and what can be done without breaking the user's work entirely.
Also pay attention to physical and procedural security. Locking a screen, securing a device, disposing of storage media properly, and handling incident documentation are all Core 2 territory. Technicians are often the weakest or the strongest link in an organization's security, depending entirely on these habits.
Software troubleshooting: follow the symptom, not your first guess
Software troubleshooting questions reward a disciplined method. Identify the problem, establish a theory, test it, and — critically — verify the fix and document the outcome. Candidates lose marks by jumping to the most dramatic explanation: reinstalling the OS when a profile is corrupt, replacing hardware when a driver update is the fault, or blaming the network when an application setting changed.
A useful drill is to take any practice question you got wrong and write down, in one sentence, what evidence would have pointed to the right answer. Over a week, those sentences become a personal troubleshooting playbook: slow performance after an update suggests a driver or compatibility issue; an application that fails for one user but works for others suggests a profile or permissions problem; a system that fails the same way every time suggests a repeatable cause worth isolating rather than a random glitch.
This is also where Core 2 separates technicians who have supported real users from those who have only read about supporting them. Real users describe symptoms imprecisely. The exam mirrors that. Train yourself to translate vague reports — "it's slow," "it worked yesterday," "nothing changed" — into testable questions.
Operational procedures: the domain everyone underestimates
Operational procedures is the domain candidates study last and regret most. It covers documentation, change management, incident response steps, safety, environmental controls, and professional communication. None of it is glamorous. All of it appears on the exam, and all of it decides whether a technician is trusted with real systems.
The key insight is that procedures exist to protect the next person who touches the ticket. Good documentation is not paperwork for its own sake; it is how a colleague at 2 a.m. knows what you tried, what worked, and what not to repeat. Good change practice is how an organization avoids fixing one user's problem by breaking ten others. Good communication is how a frustrated user becomes a cooperative one.
Study this domain by imagining the consequences of skipping each step. What happens if you do not back up before a repair? If you do not verify a fix with the user present? If you dispose of a drive without wiping it? The exam's procedure questions usually hinge on exactly one skipped step, and the right answer is the one that prevents the downstream harm.
A study plan that matches the exam
A realistic Core 2 plan runs four to six weeks for someone who passed Core 1 recently, longer for someone returning to study after a break. Spend the first week on operating systems, hands-on, with a virtual machine or a spare system you can break and repair. Spend the second on security, using real-world examples: phishing emails you have actually received, malware symptoms you can recognize, settings you can check on your own devices. Spend the third on software troubleshooting, working through practice scenarios rather than rereading notes. Spend the fourth on operational procedures, which rewards careful reading more than lab time — and then spend the remaining time on mixed practice, where scenarios cross domains the way the exam does.
Two habits matter more than total hours. First, practice under exam conditions: timed sets, no notes, and a review pass where you explain every wrong answer aloud. Second, keep a running list of your recurring mistakes. If you keep choosing the most destructive fix first, or the policy answer instead of the technician's action, that pattern is more valuable than any single practice score — it tells you what to change before exam day.
One natural place to test yourself is the free 220-1202 practice test on Study4Pass: CompTIA A+ 220-1202 free practice questions. Use it the way the exam will use you — scenario by scenario, with a clock running — and treat every miss as a note about your method, not just your memory.
Bottom line
Core 2 does not ask whether you know computers. It asks whether you can support the people who use them: install and maintain their systems, protect them from the threats aimed at them, fix their software problems methodically, and leave a record the next technician can trust. Study it as a support job, not a second hardware exam, and the questions start to read differently — less like trivia, more like tickets you already know how to close.
