CompTIA A+ 220-1201 Core 1: Hardware, Networking, and Troubleshooting

CompTIA A+ Core 1 exam 220-1201 is the current V15 hardware-and-networking half of the A+ certification. CompTIA launched the V15 pair in March 2025. Candidates earn A+ by passing both 220-1201 and 220-1202 Core 2 from the same version. The current Core 1 objectives use five domains: Mobile Devices, Networking, Hardware, Virtualization and Cloud Computing, and Hardware and Network Troubleshooting.

The exam is designed for entry-level IT support work, but “entry level” should not be confused with purely theoretical. CompTIA uses multiple-choice and performance-based questions, and the blueprint emphasizes tasks technicians actually perform: configure devices, connect users, choose components, diagnose failures, and explain the safest next step. The current objectives list up to 90 questions in 90 minutes with a passing score of 675 on a 100–900 scale.

The CompTIA A+ certification combines this Core 1 exam with Core 2 inside the broader CompTIA certification program. Candidates coming from the retired 220-1101 Core 1 should preserve durable V14 skills, then remap every final study objective to the active 220-1201 blueprint.

Mobile-device support begins with compatibility and user workflow

The mobile domain covers laptops, accessories, displays, wireless connectivity, and support considerations around portable devices. The most useful study method is to connect components with symptoms. A failing battery, damaged display path, incompatible dock, storage issue, or wireless configuration problem can produce very different user complaints even when the device appears simply “unreliable.”

Practice identifying replaceable components and safe service steps on a laptop you can afford to disassemble, or use detailed vendor service documentation if hardware access is limited. Pair physical work with configuration tasks such as Bluetooth, Wi-Fi, peripheral setup, and synchronization. The exam rewards technicians who understand both the physical endpoint and the connections that make it useful.

Networking is large enough to require hands-on packet-path thinking

Networking represents a major share of Core 1. Candidates need working knowledge of ports, protocols, IP addressing, wireless standards, network devices, cabling, SOHO configuration, DNS, DHCP, and common services. The objective is not advanced routing design; it is the ability to put a client on the network and isolate why communication fails.

Build a small lab with a router or virtual network, multiple clients, DHCP, DNS, wired and wireless access, and at least one intentionally wrong configuration. Use ipconfig or equivalent tools, ping, name-resolution checks, interface status, and router information to trace the path. If this domain becomes your strongest interest, Network+ N10-009 is the natural deeper networking step after A+.

Hardware questions are easiest when parts are studied as systems

Core 1 hardware includes motherboards, processors, memory, storage, power, expansion, peripherals, displays, printers, and installation decisions. Avoid studying each part in isolation. A motherboard choice constrains CPU, memory, storage interfaces, expansion options, case compatibility, and power requirements. A storage upgrade changes performance and may affect migration or boot configuration.

Use a compatibility-first checklist in practice. Identify the requirement, inspect current hardware, select a compatible part, protect data and equipment, perform the change, then verify the operating system sees the expected result. This sequence prepares you for scenario questions where several components are individually valid but only one fits the system and user requirement.

Virtualization and cloud concepts belong in the support technician’s toolkit

The current blueprint retains virtualization and cloud computing because endpoints increasingly depend on hosted services and virtual resources. Candidates should understand virtual machines, hypervisors, resource allocation, cloud service models, elasticity, synchronization, and the difference between local and remote responsibility. A support incident may originate in the endpoint, the network, the virtualization layer, or the service provider.

Run at least one local virtual machine and observe CPU, memory, storage, networking, snapshots, and guest tools. Then compare that experience with a hosted SaaS application or cloud console. The goal is to see boundaries clearly: what can the endpoint technician change, what belongs to the virtualization platform, and what depends on a remote provider.

Hardware and network troubleshooting is a method, not a list of symptoms

The largest Core 1 domain is troubleshooting. Learn the formal process well enough that it becomes natural: identify the problem, establish and test a theory, plan and implement the fix, verify functionality, and document the result. The sequence matters because an unsupported guess can create a second problem and hide the evidence from the first.

Create repeatable fault labs. Use a wrong gateway, bad DNS entry, disconnected storage device, loose memory module in a safe test machine, printer queue problem, thermal issue, or wireless interference scenario. Before touching the configuration, write down what evidence would confirm or reject the leading theory. That habit improves both exam performance and real support accuracy.

Performance-based preparation should combine configuration and explanation

PBQs often expose whether a candidate can apply several objectives together. A support scenario might require identifying the correct network device, assigning settings, choosing a cable or port, and verifying the final connection. Another may involve hardware compatibility plus troubleshooting. Practice small integrated tasks instead of only answering isolated multiple-choice questions.

After each lab, explain what you changed and why. If you can perform a task but cannot explain the effect, your understanding may be too procedural. If you can explain the concept but cannot complete the task efficiently, you need more hands-on repetition. Core 1 readiness sits between those two abilities.

Study the current V15 blueprint, not a recycled V14 checklist

The retired 220-1101 exam overlaps heavily with the current Core 1 at the conceptual level, which is why older resources can feel convincing. However, V15 changed emphasis and technology examples. Use current objectives to organize notes, then attach older explanations only where they still fit. Do not let a retired domain weight determine how you allocate final review time.

A useful migration exercise is to take one old 220-1101 chapter and tag every topic as unchanged, updated, moved, or no longer emphasized. Repeat only for material you actually plan to reuse. This keeps study efficient and makes version changes visible instead of allowing them to hide inside familiar course structure.

Pair Core 1 with Core 2 so the certification reflects a complete support role

Core 1 is not the full A+ credential. Hardware and networking problems often lead directly into operating-system, security, software, and operational-procedure work that belongs to 220-1202. Plan the two cores as connected halves: understand the physical and network platform in Core 1, then the user environment and support process in Core 2.

A strong final plan alternates objective review with labs, performance-based practice, and timed mixed questions. Keep error notes by root cause rather than by question number. If the same weakness appears repeatedly—subnetting, printer processes, laptop hardware, wireless standards, or cloud service models—build a targeted lab around it. That turns practice results into a concrete improvement cycle instead of a score-chasing exercise.

Storage deserves its own hands-on cycle because support technicians routinely encounter upgrades, failures, and migration questions. Compare SATA and NVMe behavior, partition and format test drives, observe SMART or health information where available, and practice cloning or reinstall decisions on disposable systems. A slow computer is not automatically a storage problem, but storage evidence should be part of a structured diagnosis when boot times, file errors, or capacity warnings appear.

Printer objectives are easy to underestimate because they feel older than cloud and mobile topics, yet business support environments still depend on them. Know the major print processes, consumables, maintenance kits, connectivity options, and common image defects. Practice separating a driver or queue issue from a network reachability issue and from a mechanical print-quality problem. This is exactly the kind of layered reasoning that performance-based questions can test efficiently.

Wireless preparation should move beyond memorizing standard numbers. Understand frequency bands, channel overlap, signal strength, interference, encryption choices, access-point placement, and the difference between authentication and connectivity. Build a small Wi-Fi troubleshooting checklist: verify the radio, confirm the correct SSID and security settings, inspect address assignment, test local gateway reachability, then test name resolution and external access. This sequence turns a vague “Wi-Fi is down” complaint into a tractable problem.

Core 1 also rewards safe work practices. Use ESD protection, disconnect power when servicing hardware, handle batteries and damaged components appropriately, and follow environmental disposal guidance. Safety questions may appear straightforward, but in real support work they determine whether a repair creates a second incident. Treat them as part of the same professional method used for troubleshooting, not as a separate theory chapter.

Device interfaces and cabling are best learned by handling them. Identify common USB variants, display connections, Ethernet cabling, storage interfaces, power connectors, adapters, and docking options. Then add the compatibility question: what bandwidth, direction, power delivery, or device class does the connection support? This is more reliable than remembering a connector by shape alone, especially when several generations share similar physical forms but different capabilities.

For final review, organize the five domains around real support calls rather than separate chapters. A laptop that cannot reach a cloud application may involve mobile hardware, Wi-Fi, IP configuration, DNS, virtualization or cloud dependency, and troubleshooting method in the same incident. Mixed scenarios reveal whether your knowledge transfers across domain boundaries. That is a better readiness signal than being able to recite each domain weight from memory.

Build one capstone lab that combines the major Core 1 tasks: assemble or inspect a workstation, configure firmware and storage, connect it to wired and wireless networks, attach a printer or peripheral, run a virtual machine, then introduce several faults and recover them. The value is not complexity for its own sake. It is seeing how hardware, networking, cloud dependency, and troubleshooting interact when the scenario is not labeled by domain.