Ask a hiring manager what they want from a newly A+ certified technician and they will not ask whether you can recite the pin count of a DDR5 module from memory. They will ask whether you can walk up to a machine that will not boot, a laptop with a dead screen, or a printer that has decided today is the day it stops cooperating, and work the problem to a fix without making it worse. That is exactly what CompTIA A+ Core 1 (220-1201) tests, and it is why so many candidates who memorized flashcards still fail it: the exam grades your troubleshooting judgment, not your vocabulary.
Core 1 covers hardware, networking, mobile devices, virtualization, and cloud basics, plus the troubleshooting methodology that ties them together. Core 2 (220-1202) covers operating systems, security, and operational procedures. Together they earn the A+ certification, the entry-level credential that still opens the most help-desk and field-technician doors. This article focuses on Core 1, because Core 1 is where candidates discover that knowing what a component is and knowing what to do when it fails are two very different skills.
The methodology question hiding inside every scenario
CompTIA publishes a six-step troubleshooting methodology: identify the problem, establish a theory of probable cause, test the theory, establish a plan of action, verify full system functionality, and document findings. On the exam, this methodology is not a trivia topic. It is the hidden structure of nearly every scenario question.
A typical question describes a user whose laptop intermittently loses its Wi-Fi connection, gives you four possible next steps, and asks which you should do first. The candidates who fail pick the most technically impressive action — replace the wireless card, update the driver, reset the router. The candidates who pass pick the step that matches where they are in the methodology. If you have not yet identified the problem, you gather information first: does it happen on other networks, does it happen for other users, what changed recently? If you have a theory, you test it with the least invasive step first. Replacing hardware before testing a theory is not thorough; on the exam, it is wrong.
Train yourself to read every scenario question twice: once for the symptoms, and once for the stage. Ask, "What has already been done in this story?" The question almost always tells you. If a technician already swapped the cable and the problem persists, the cable is eliminated, and the answer is not to swap it again. If nobody has asked the user anything yet, the answer is almost certainly to gather more information. The methodology is a filter that eliminates two of the four options on most questions before you even reach the technical detail.
Hardware: think in symptoms, not in spec sheets
Core 1 hardware questions reward people who can map a symptom to a subsystem. A computer that powers on, spins its fans, and shows nothing on screen is a different problem from a computer that shows nothing at all, and both differ from a computer that boots and then crashes under load. Each symptom points somewhere: no power at all suggests the power supply or the power path; fans with no display suggests memory, video, or the motherboard's ability to complete POST; crashes under load suggest heat, a failing power supply, or unstable memory.
Study hardware by failure mode, not by feature list. For each major component — motherboard, CPU, RAM, storage, power supply, display — learn its three most common failure symptoms and its simplest diagnostic test. RAM fails with beep codes, random crashes, and boot failures, and you test it by reseating or swapping a stick. Storage fails with slow performance, disappearing drives, and SMART errors, and you test it by checking connections and SMART status before you ever reach for a replacement. Displays fail with backlight problems, dead pixels, and inverter or cable faults on laptops, and you test them with an external monitor before you condemn the panel.
Performance-based questions, the simulations and drag-and-drop items, test the same thinking in a hands-on format. You may be asked to select the right cable for a connection, assemble a workstation from parts, or configure a RAID array. The trick is the same: the question gives you constraints — a budget, a use case, a compatibility requirement — and the right answer satisfies all of them. A gaming build and an office build do not get the same storage or power supply, even though both are "computers."
Networking: the small set of concepts that carry the whole domain
Candidates often over-study networking for Core 1, memorizing port numbers and cable categories, and under-study the handful of concepts the exam actually leans on. Know the common ports that appear in real support work — HTTP, HTTPS, DNS, DHCP, SSH, RDP, SMB — and know what breaks when each service fails. If DNS fails, names stop resolving but IP addresses still work; if DHCP fails, new devices get no address at all. That distinction alone answers several questions.
Know the cable and connector families by use case: twisted-pair copper for most LAN runs, fiber where distance or interference demands it, coaxial largely as a legacy technology you will recognize but rarely install. Know the difference between a switch, a router, and an access point in terms of what problem each solves, and know Wi-Fi standards well enough to explain why a device on an old 2.4 GHz network is slow — not because the standard is "bad," but because the band is crowded and the standard is old.
Then practice the diagnostic sequence the exam loves: check the physical layer first (is it plugged in, is the link light on?), then the local configuration (does the device have a valid IP address, is it on the right network?), then the service layer (can it reach the gateway, can it resolve names?). Questions that describe a user who "cannot get online" almost always have their answer at the earliest layer where something is actually broken, and the distractors are fixes for layers that are fine.
Mobile devices and the laptop repair questions
Mobile devices are a larger share of Core 1 than many candidates expect, and the questions are practical: replacing a laptop screen, dealing with a swollen battery, troubleshooting a phone that overheats or drains overnight, syncing and securing mobile devices. The safety questions matter here. A swollen battery is not a "replace it when convenient" item; it is a safety hazard, and the exam expects you to treat it that way — power the device down, do not puncture or bend the battery, and follow proper disposal procedures.
Laptop questions test component knowledge through repair scenarios: which component to replace for a given symptom, what to check before disassembling, and how to handle the common gotchas like hidden screws, ribbon cables, and the need to disconnect the battery first. If you have never opened a laptop, watch a teardown video for a common model and follow along mentally. The exam cannot ask you to open a machine, but it can ask what you would do first, and "disconnect power and remove the battery" is the right first move more often than candidates expect.
Virtualization and cloud: the concepts, not the console
Core 1's virtualization and cloud content is conceptual, and candidates either skip it or overcomplicate it. You need to know what a hypervisor does, the difference between a host and a guest, why a virtual machine needs allocated CPU, memory, and storage, and what resource contention looks like when too many guests share one host. For cloud, you need the service models — infrastructure, platform, and software as a service — and the deployment models, public, private, and hybrid, plus the basic characteristics that define cloud computing: on-demand resources, scalability, and metered usage.
The exam questions here are almost always "which model fits this scenario" questions. A company that wants to stop managing servers but still run its own applications wants infrastructure as a service. A company that wants to use an application without managing anything wants software as a service. Learn the models as answers to business needs, not as definitions, and these questions become free points.
A four-week Core 1 study plan
Week 1: Methodology and hardware foundations. Learn the six-step methodology cold, then study each hardware component by failure symptom and diagnostic test. Build a symptom-to-subsystem map and drill it until it is automatic.
Week 2: Networking and mobile. Ports, protocols, cable types, Wi-Fi, and the layered diagnostic sequence. Then mobile devices: laptop components, battery safety, common phone and tablet faults, and mobile device management basics.
Week 3: Virtualization, cloud, and performance-based practice. Service and deployment models, hypervisor concepts, and hands-on practice: build a parts list for a given use case, practice cable and connector matching, and work through scenario questions under time pressure.
Week 4: Timed practice and weak-spot repair. Take full-length practice exams under exam conditions — 90 questions, 90 minutes, no notes. For every question you miss, write down not just the right answer but the methodology stage you were at and why the distractor tempted you. That error log is worth more than another pass through your notes.
A free practice test for the exam is a good place to start that final week: timed, exam-style questions for CompTIA A+ Core 1 (220-1201) are available at https://study4pass.com/study-material/comptia/220-1201 — use it to find your weak domains before exam day, not after.
Bottom line
Core 1 does not reward the candidate who knows the most facts. It rewards the candidate who, faced with a broken machine and four plausible actions, picks the one a good technician would actually do first. Study the methodology until it is instinct, learn hardware by symptom, diagnose networks layer by layer, and treat every practice question as a rehearsal for a real support call. Pass that way, and the certification means something on your first day on the job — because the exam tested the job, not the textbook.
Top comments (0)