An older CompTIA A+ article can teach useful hardware troubleshooting and still send a candidate to the wrong exam. The difference is the version number. As of October 2026, the current A+ V15 certification exams are Core 1 (220-1201) and Core 2 (220-1202). Older materials built around 220-1101 and 220-1102 may remain useful for fundamentals, but their administrative details and objective coverage should not be presented as instructions for a new booking.
The safest starting point is to identify the exact official objectives for each core and decide what kind of hands-on evidence would demonstrate the required skill. CompTIA’s V15 objectives describe installation and maintenance of endpoints, networking fundamentals, security, diagnosis, documentation and support communication. They still test whether a technician can make a sensible decision under incomplete information rather than recognize a fashionable tool name. This article distinguishes the two cores, explains where their topics overlap in real work, and suggests how to prepare without memorizing a stale exam checklist.
One certification, two complementary assessments
A+ is an entry-level support and troubleshooting credential, not a single general-knowledge quiz. Candidates must satisfy requirements for both cores. Core 1 concentrates on devices and infrastructure: mobile devices, networks, hardware, virtualization/cloud fundamentals and hardware or network troubleshooting. Core 2 centers on operating systems, security, software troubleshooting and operational procedures. The distinction is useful for planning study, but real service problems rarely respect it.
Suppose a laptop is connected to Wi-Fi but cannot reach a company application. A candidate may need Core 1 knowledge to inspect addressing, DNS and wireless connectivity, plus Core 2 knowledge to investigate endpoint security, operating-system settings, a broken client update and user permissions. The objective is not to guess which core the problem belongs to; it is to narrow the failure domain and document the evidence. A useful preparation plan deliberately combines related topics in diagnostic exercises while tracking coverage against the actual two official blueprints.
A+ exams also include performance-based tasks in addition to conventional questions. They reward selecting an appropriate procedure, identifying the consequences of a configuration and distinguishing a reversible test from a change that risks user data. Someone who can recite definitions but cannot carry out a safe diagnosis will find these scenarios harder than expected. That is why a small repair lab, screenshots of validation steps and written reasoning often produce more lasting value than another stack of flashcards.
Core 1: diagnose the device and its connections
Core 1 begins with the practical lifecycle of a user device. Mobile devices require appropriate connectivity, account configuration, peripherals and safe handling of user data. A support technician should be able to distinguish a charging problem from a battery problem, a failed accessory from a port issue, and a faulty application from an operating-system restriction. The test is not a specialist mobile developer examination. It checks whether technicians can support devices responsibly within their authorized scope.
Networking adds more opportunities for disciplined reasoning. An endpoint can have working local connectivity while name resolution or upstream routing is broken. A physical link can report active even when the expected VLAN or address settings are wrong. A user may call a slow application a “network failure” when the relevant problem is a congested storage service or overloaded endpoint. Candidates should understand addressing, common protocols, wireless standards and simple diagnostic tools well enough to discriminate between these hypotheses.
Hardware knowledge remains important because no abstract cloud diagram can repair a damaged connector or incompatible component. Know how memory, storage, power supplies and peripherals affect system behavior, and understand the precautions involved in replacing parts. A good technician checks warranty and authorization, protects data, observes electrical safety and records the exact model before attempting a replacement. Hardware troubleshooting also requires knowing when not to open a device or make an irreversible change.
Virtualization and cloud fundamentals appear in Core 1 because even entry-level support now crosses local and hosted systems. Candidates need to recognize basic virtual-machine concepts, common cloud service models, resource allocation, connectivity and the practical implications of shared responsibilities. This does not require designing a multinational cloud architecture. It requires understanding what is running locally, what depends on a hosted service, and which team or provider has responsibility for the failing component.
Core 2: restore usable, secure software
Operating-system support is the heart of Core 2. The technician may have to identify what changed after an update, distinguish an application crash from a user-profile issue, or choose a safe recovery path when a device cannot boot. A competent approach begins with protecting user data and recording the symptoms. Blindly resetting a computer because a script suggests it is rarely the best first step, especially when the device contains business-critical information.
Security is not an isolated final chapter. It shapes every endpoint support decision: least privilege, safe software installation, malicious links, secure remote assistance, update policy, logging, and account recovery. A candidate should know why a temporary administrator privilege needs justification and expiry, why an unknown USB device cannot be trusted, and how a compromised device should be handled according to an organization’s incident process. The focus is operational judgment, not pretending an entry-level technician is the security incident commander.
Software troubleshooting includes application failures, bad updates, incompatible dependencies, security software interference and user-configuration problems. It helps to practice with reproducible faults. For example, create a test account with the wrong application permissions, compare the behavior with a working account, and confirm the result after repairing the rule. Then deliberately introduce an unrelated failure and ensure the same procedure does not produce a false diagnosis. Recording both the result and the reasoning teaches more than memorizing a single fix.
Operational procedures complete the picture. A technically correct change can still be poor support if the technician never seeks authorization, fails to update the incident ticket, disrupts another user’s work or loses track of the original configuration. Good communication includes explaining the risk, giving a realistic scope for the test, asking what the user was doing when the problem appeared and specifying what was verified before closing the issue. These habits are part of technical competence, not optional customer-service decoration.
What version updates mean for older study material
Older A+ guides can still explain CPU components, wireless fundamentals or file permissions accurately. Their risk comes from assuming an unchanged blueprint. An older guide may overemphasize a retired objective, omit current security or cloud-tool expectations, or use an exam number that is no longer the right booking choice. When a book advertises itself as “new” without naming 220-1201 and 220-1202, do not trust the cover date alone.
Use the official objective PDFs as the coverage checklist. Make a simple matrix with one row per domain and a column for evidence: a lab completed, a failure diagnosed, a configuration documented, or a concept explained. If a resource teaches a valid fundamental without mapping perfectly to the latest objectives, keep it as optional background. If it makes a dated claim about allowed tools, question counts, schedules or fees, verify those administrative details with CompTIA directly before acting.
This approach also prevents a common training mistake: replacing actual technical practice with a large set of unauthorized remembered exam questions. A legitimate practice question should challenge reasoning about a plausible support situation; it should not claim to reproduce restricted live items. CompTIA’s published objectives and candidate policies are the basis for preparing fairly and professionally. A candidate who studies to diagnose rather than memorize is better prepared for work after the certificate is earned.
Build a cross-core troubleshooting routine
Start with three deliberately modest lab scenarios. First, break wireless name resolution while leaving basic connectivity intact; record how you distinguish the two. Second, install a controlled software update that produces an application compatibility issue in a test environment; explain how to diagnose and roll back without affecting user data. Third, create a least-privilege account that cannot perform a required action; determine whether the fix belongs in a permission assignment or a changed workflow. These exercises cover multiple objectives and teach the habit of forming and testing one hypothesis at a time.
For each scenario, keep the same short record: symptom, business effect, initial observations, possible causes, tests performed, authorized corrective action, verification and follow-up. Include a case where the first guess was wrong. This prevents a “successful lab” from hiding a weak troubleshooting method and gives candidates something concrete to discuss in a support interview.
Do not turn the exercise into a competition to use the most commands. The effective technique is the one that safely discriminates among plausible causes and can be explained to someone else. Sometimes that means checking a cable or confirming a recent change rather than running a complex diagnostic tool. Candidates should know the purpose of tools, their permissions and limitations, and how to avoid altering evidence while testing.
How to organize study without repeating the same advice
Work through Core 1 and Core 2 in the order that exposes your biggest skills gaps, not solely the order in a commercial study bundle. Someone experienced with hardware but weak in endpoint security can devote more labs to permissions, incident handling and application troubleshooting. Someone comfortable with operating systems but new to networking may need extra practice tracing a packet from a user device through an access point, switch and upstream service.
The official objectives should anchor the plan, but they are not a substitute for understanding concepts. Review a topic, create or observe a failure, explain it without notes and return later to repeat the diagnosis. Track errors by cause: misunderstood vocabulary, a faulty assumption about a system, a missed safety step or a genuine skill gap. That classification is more useful than recording only a practice-test percentage. A high score produced by seeing identical questions repeatedly does not demonstrate operational readiness.
When closer to the test date, confirm the code, testing provider policies, accepted identification, language, location and currently offered delivery method through CompTIA. Policies may change without altering the technical concepts in the objectives. Avoid treating a blog’s historical timetable or price as a guaranteed current offer. The candidate is responsible for checking what will actually be delivered on the chosen date.
From passing A+ to doing competent support work
A+ can help organize foundational knowledge, but the most persuasive signal to an employer is how a candidate handles real operational uncertainty. Can they explain why a change was safe? Did they protect user data? Could they discriminate among competing causes? Did they test the fix and document its limitations? The current two-core curriculum gives opportunities to develop those habits, but candidates must practice them deliberately.
The essential version correction is simple: use CompTIA A+ 220-1201 and 220-1202 for the current V15 track, and regard earlier 220-110x materials as historical unless their technical explanations remain useful independently of the old exam. Study the underlying systems, not just the exam’s marketing. The result should be a learner who can safely support a device or service and explain the reasoning behind that work.