CompTIA A+ 220-1101 Core 1: Retired Exam and Current Hardware Skills

CompTIA A+ 220-1101 was the Core 1 exam in the A+ 1100-series certification, covering mobile devices, networking, hardware, virtualization and cloud computing, and hardware/network troubleshooting. The English-language 1100-series examinations retired on September 25, 2025, with the transition to the 1200 series completed for other languages later that year. In October 2026, candidates beginning A+ should use the current 220-1201 Core 1 and 220-1202 Core 2 exam objectives. This page preserves the older Core 1 technical foundation while clearly distinguishing it from an available exam.

The 220-1101 subject remains useful because technicians still troubleshoot the same basic hardware and network failures that appear in current workplaces. A failing storage device does not become a different problem because the credential version changes. What can change is the emphasis given to newer interfaces, wireless standards, devices, and support practices. Older notes should therefore support conceptual learning, not replace the current CompTIA objective list or be used to make scheduling decisions.

Establish a structured hardware troubleshooting method

A support technician needs a repeatable way to work from symptoms to a justified repair. Begin by confirming the complaint and its scope, recording recent changes, and protecting user data. Determine whether the system fails to power on, fails its startup checks, cannot find a bootable device, overheats, or works intermittently under load. These symptoms suggest different paths through power, memory, CPU cooling, storage, peripherals, firmware, and software. Replacing several components without testing introduces cost and obscures the original cause.

For a computer that shuts down during heavy use, examine thermal conditions, fans, ventilation, power-supply capability, and relevant system logs. A device that suddenly fails to boot after a drive replacement may need storage interface or firmware investigation. ESD precautions, power isolation, handling of batteries, and manufacturer service guidance must govern physical work. A technically successful repair is not acceptable if it creates electrical risk or destroys data.

Document the hypothesis, observation, action, and result. If a technician suspects memory failure, conduct a suitable diagnostic and verify the outcome before purchasing replacement modules. A machine that boots after components were reseated may still have a hardware defect that returns under movement or temperature change. Re-test under realistic conditions and record what evidence confirms a durable fix.

Compare modern storage and platform components

Storage technologies differ in interface, latency, capacity, endurance, and failure symptoms. SATA hard drives, SATA SSDs, and NVMe SSDs can all hold an operating system, but they have different performance and connectivity characteristics. A drive that appears physically compatible may not be supported by a specific slot or platform configuration. The NVMe, SATA SSD, and HDD comparison is useful because physical form factor, electrical interface, and storage protocol should not be treated as interchangeable.

RAID can improve availability or performance under particular configurations, but it is not a substitute for backups. RAID 0 can increase capacity and speed while exposing data to loss on member failure; mirrored and parity-based arrays make different capacity and recovery trade-offs. Understand how a degraded array behaves, how replacement and rebuild affect performance, and why a second failure may be catastrophic during reconstruction. The RAID 0, 1, 5, and 10 troubleshooting material extends these considerations beyond memorized level names.

Other hardware topics include motherboard form factors, processors, memory types, power supplies, displays, connectors, and peripheral interfaces. A faster connector name does not guarantee a peripheral will work at a corresponding speed; host capabilities, cable specifications, negotiated mode, and device support also matter. The USB-C, USB4, and Thunderbolt discussion reinforces why connector shape and protocol support are different questions when diagnosing docking-station failures.

Troubleshoot networking by layer

A wired or wireless client needs a usable link, addressing, routing, name resolution, and application connectivity. A workstation may connect to Ethernet successfully but fail to obtain a valid address; another may have an address yet no usable DNS resolver. Verify link indicators and adapter state, inspect IP configuration and default gateway, then use appropriate reachability and name-resolution tests. A failed browser request does not automatically prove the internet is down; the defect could be limited to proxy settings, DNS, TLS, or one application.

Common networking topics include Wi-Fi security and bands, router versus switch behavior, DHCP, DNS, address translation, cabling, network ports, and basic troubleshooting tools. A wireless connection with strong signal can still deliver poor performance under interference, channel contention, or inadequate backhaul capacity. The Wi-Fi 6, 6E, and 7 troubleshooting material is newer than the historical exam but relevant when moving old study notes toward the current Core 1 objective set.

For a reproducible lab, compare a client connected to the correct SSID but assigned the wrong VLAN with one connected correctly but unable to resolve a service hostname. Their user-facing symptom may be identical. The first demands a network-access and addressing investigation; the second points to resolver or application configuration. Record the exact test and result so another technician can repeat the reasoning.

Support mobile devices and peripherals safely

Smartphones, tablets, laptops, and other mobile devices introduce battery, display, wireless, synchronization, and peripheral-management issues. Charging problems may arise from a cable, power adapter, device port, battery health, or firmware state. The correct response is to identify what can be safely tested without opening a sealed or damaged battery system. User data protection and device-management policy matter when recommending resets or replacement.

Mobile network connectivity can differ from a laptop's because of radio capabilities, captive portals, saved credentials, certificate stores, and operating-system restrictions. A phone reaching a website over cellular but not corporate Wi-Fi gives useful evidence about the path, but not yet a complete diagnosis. Compare the same application on another managed device and inspect whether policy or identity conditions differ. Be cautious with factory resets: they can remove unsynchronized data and company enrollment state.

Printers and scanners require similarly structured troubleshooting. A print job may fail because the device is offline, the spooler is stuck, the driver uses an incorrect language, the network address changed, or a consumable is depleted. The printer symptom-diagnosis explanation supports the principle of looking for evidence before replacing a cartridge or hardware assembly. Test a locally generated configuration page to separate device mechanics from client-to-printer communication.

Understand virtualization and cloud without overstating scope

The retired Core 1 syllabus introduced virtualization hosts and guests, desktop virtualization, cloud models, and shared-resource concepts. Technicians should know the difference between a virtual machine and a physical host, and understand that guest storage, network connectivity, and available memory depend on the underlying platform. A virtual machine may report an operating system problem while the real cause is resource contention or a disconnected virtual switch.

Cloud services introduce shared responsibility for identity, configuration, endpoint access, and data handling. A user unable to reach a cloud application might have a network problem, a local browser issue, a failed identity policy, or a service-side outage. Diagnose the client and network path before telling users to reinstall software. Escalation should include precise times, account context without revealing secrets, steps to reproduce, and evidence that narrows the scope of the fault.

The newer A+ objectives place additional emphasis on evolving technologies and practical support scenarios. Legacy 220-1101 notes are still useful for baseline networking and hardware knowledge, but the official CompTIA certifications and current 1200-series blueprints should determine which examples and device capabilities a candidate must know for certification.

Build a hardware-and-network triage exercise

Create three support cases. First, a laptop has normal power indicators but cannot locate its boot drive after a storage upgrade. Second, a workstation works over Ethernet but loses access to one internal application when moved to wireless. Third, a network printer produces a local test page but fails from a user workstation. For each, write at least two plausible causes, choose the next safe test, and record the result that would narrow the fault.

Repeat one case after intentionally introducing a misleading symptom, such as a valid-looking IP address with an incorrect DNS server. A good technician does not stop after discovering one abnormal value; the repair must be followed by functional validation. Finish with a ticket note identifying the issue, root cause if established, steps taken, post-repair tests, and any remaining user action. This process illustrates why the technical material remains useful after retirement.

A hardware incident should also address the firmware-to-operating-system trust chain. A laptop that stops booting after a firmware update may have changed Secure Boot, TPM, storage-controller, or boot-order behavior. Do not assume a drive is defective merely because the firmware cannot find a bootable system. Check the platform's documented recovery steps, identify whether device encryption or a recovery key is involved, and avoid destructive partition operations until the data-protection plan is clear. In managed environments, a technician may need the organization's endpoint administration team to recover a device's trust state. This makes firmware configuration and account control part of the same support decision rather than unrelated troubleshooting topics.

For current A+ candidates, this historical Core 1 page should serve as background only. Pair the active Core 1 220-1201 objectives with the active Core 2 220-1202 requirements; do not plan to sit the retired 220-1101 exam. The best preparation is demonstrable ability to diagnose real hardware and connectivity faults, supplemented by the currently published assessment blueprint.