CompTIA A+ covers a broad reality of IT support: a device has stopped working, the person using it needs a safe fix, and the technician must identify the cause without losing data or making the situation worse. Core 1 emphasizes hardware, mobile devices, networks, virtualization, and infrastructure troubleshooting. Core 2 focuses on operating systems, security, software troubleshooting, and operational procedures. Studying them as two halves of one service workflow produces more durable competence than memorizing individual device facts.
The active 2026 A+ exam pair is 220-1201 (Core 1) and 220-1202 (Core 2). Older 220-1101/220-1102 material may explain lasting concepts, but those codes are historical; they should not be presented as current booking or preparation instructions. Before scheduling, confirm the issuer’s published objectives and policies for the two required exams. The exact sections and item coverage can change with the version even when the general IT support work looks familiar.
Start with a problem a customer would actually report
A customer says their laptop connects to Wi-Fi but cannot access the company’s intranet. Another device on the same network works. A novice might immediately reinstall a driver, replace hardware, or disable the firewall. A competent support technician first establishes scope: is the problem one user, one device, one application, a DNS name, a permission issue, or an entire connection path? Ask what changed, reproduce the symptom, and record the current configuration before acting.
Use the same case to study both exams. Core 1 knowledge helps inspect wireless signal, interface configuration, IP addressing, DNS resolution, routing, and basic network devices. Core 2 knowledge helps inspect user identity, endpoint security policy, operating-system state, application access, and safe troubleshooting procedure. A working network connection does not prove the user is authorized to reach an application, and a login failure does not prove the cable or wireless radio is defective.
A good lab log describes the reported symptom, observations, hypotheses, tests performed, risk of each change, fix, and verification. The value of the exercise is the reasoning sequence. The customer should not have to pay for a full operating-system rebuild because a technician never checked name resolution or account access.
Core 1: Hardware and mobile devices in service context
Understand how a computer’s processor, memory, storage, power, cooling, display, firmware and peripherals interact. Component identification matters, but diagnostics matter more. A system that unexpectedly restarts under load might have a thermal, power, driver, firmware or hardware problem. Measure a symptom and isolate one variable at a time. Know which steps risk data loss, which require authorized maintenance windows, and which are appropriate for a user’s device warranty.
Practice comparing solid-state and hard-drive behavior, RAM failures, common port and cable limitations, display defects, and battery issues. On a mobile device, understand enrollment, application permissions, backup and restore, wireless connectivity and remote management. Do not assume every user can remove a battery or install software; managed devices can be constrained by business policy, security tooling or manufacturer support rules.
Build a small hardware service scenario with a documented intake form, safe diagnostics, approved repair action and verification. Record the device model, symptoms, asset owner, backup state, parts used, and whether the problem recurred. This connects technical facts to the operational work that a help desk or field technician performs.
Core 1: Networks and cloud foundations are about boundaries
An IT support technician need not be a network architect, but should distinguish local connectivity, IP reachability, DNS behavior and application access. Learn basic subnet concepts, gateways, DHCP, common ports, wireless authentication, and the purpose of switches, routers and access points. In a lab, deliberately break one layer at a time: invalid DNS server, missing route, disabled interface, incorrect Wi-Fi credential, or blocked service. Observe how the symptoms differ.
Virtualization and cloud concepts matter because desktop support now reaches beyond one physical machine. A user may run an application on a virtual desktop, synchronize files through a hosted identity system, or connect to software that lives in another region. Distinguish the customer’s device, guest operating system, network path and service provider boundary. Changing a local client setting may solve one issue while masking a remote configuration problem. Build a habit of checking the service status and the scope of affected users before making local changes.
Performance troubleshooting should use evidence. A high ping time is not always the cause of a slow application; jitter, packet loss, overloaded hosts, storage latency and application logic can also matter. State the limitation of the diagnostic tool and what it has actually measured. A realistic study scenario rewards the candidate who chooses the next safe test, not the one who uses the most commands.
Core 2: Operating systems and software failures
Core 2 tests the judgment to configure and troubleshoot major operating-system environments. Learn accounts, services, startup behavior, processes, event logs, drivers, updates, file permissions, disk management, recovery and basic scripting concepts. On Windows, Linux or macOS, the labels and tools differ, but the diagnostic process remains familiar: reproduce, inspect a trusted signal, isolate the failing layer, make a controlled change, verify, and document.
Simulate a system that fails after an update. Investigate recent change history, boot or service logs, application dependencies, and available recovery points. Decide whether rollback is safer than forcing a new driver or deleting a profile. In a managed environment, check who authorizes a software rollback and whether security controls would be weakened by the proposed workaround. An exam explanation that ignores that business context may teach a dangerous habit even if the device boots again.
Practice software installation and removal with respect for licensing, privilege and user data. Never treat reinstalling or resetting as the default first step. Understand how to collect information without exposing private files, passwords, or security tokens. Operational maturity is visible in small choices: confirm backups before destructive commands, record administrator approval, and preserve a rollback path.
Core 2: Security is part of every repair
A+ security coverage is not limited to malware definitions. Support workers routinely decide whether a device should join a network, whether a user receives privileged access, whether a downloaded installer is trustworthy, and what to do with a suspected compromised account. Learn least privilege, multifactor authentication, encryption, endpoint protection, secure network configuration and physical access controls. Connect each control to the threat it addresses and its impact on the person receiving support.
Suppose a user reports a suspicious browser extension and a sudden credential prompt. An unsafe technician might disable security tooling to ‘fix’ the browser. A better response is to record symptoms, consider whether credentials were exposed, follow approved isolation and reporting policy, and then investigate software state. Escalate rather than improvising an incident response beyond the technician’s authority. The objective is reliable and recoverable service, not a dramatic shortcut.
Also learn privacy rules and data handling. A help desk may encounter personal photographs, payroll files or health-related information while repairing a system. Access only what is necessary and document permission before copying or transferring user data. The ability to protect customers while troubleshooting is as important as remembering the difference between a worm and a Trojan.
Operational procedure ties the two cores together
Ticketing, change management, asset records, communication and safety are not filler subjects. They prevent a correct technical fix from becoming a repeat incident or an unaccountable change. A ticket should show the original report, diagnostic steps, action taken, verification and what the user was told. If a repair affects shared infrastructure, record approval and rollback. For electrical or hardware work, follow equipment handling and workplace safety requirements rather than rushing through a simulation.
Practice a complete support shift with three cases: an intermittent wireless problem, an endpoint update failure, and a security concern requiring escalation. Use a time budget and describe why you prioritize one case over another. Ask a peer to review the ticket without your spoken explanation. If they cannot reproduce or understand your decision, the documentation needs improvement even if the problem was fixed.
Communication is a technical skill in support roles. Translate the result into plain language, state what was tested, and identify any remaining risk. A user who understands the limitation of a temporary workaround is less likely to mistake it for a permanent solution. Good follow-up notes also prevent the next technician from repeating diagnostics and potentially damaging the device.
Prepare for the current two-exam structure without false shortcuts
The original approved site inventory contains distinct CompTIA A+ 220-1201 and CompTIA A+ 220-1202 exam destinations. Those are contextual links to the correct current code family; the workbook does not establish that any particular page has been independently HTTP-tested or is bookable through this site. Use CompTIA’s first-party objectives to verify each domain before your appointment.
Start with diagnostic labs, then use ethical practice questions to identify weak reasoning. For a missed item, write why the attractive incorrect choices were wrong. Recreate the fault on a system you control when possible. Do not use unauthorized real-exam dumps; leaked questions cannot substitute for troubleshooting and may violate examination policy. Practice under time constraints only after you understand the task, because rushing through guessed answers can train bad habits.
The older 220-1101/220-1102 versions can be cited in historical comparisons, but do not call them the two exams that ‘comprise the current A+’. Their retirement does not make fundamental hardware or support experience useless. It simply means that a current candidate should study the 220-120x blueprint and demonstrate the modern tool and operational expectations it contains.
An A+ pass is a useful foundational credential, not an automatic guarantee of employment or a salary level. The more durable result is someone who can troubleshoot a system safely, tell the customer what happened, recover when a change fails, and leave a record that another technician can trust. That is the skill story worth taking into both Core 1 and Core 2.