CompTIA A+ Core 1 220-1201 is the current V15 hardware, networking, mobile-device, virtualization/cloud, and troubleshooting exam. CompTIA’s current objectives document lists up to 90 questions in 90 minutes, multiple-choice and performance-based questions, twelve months of recommended hands-on IT support experience, and a passing score of 675 on the 100–900 scale. Core 1 must be paired with Core 2 220-1202 to earn A+.
The current 220-1201 blueprint has five domains: Mobile Devices at 13%, Networking at 23%, Hardware at 25%, Virtualization and Cloud Computing at 11%, and Hardware and Network Troubleshooting at 28%. The largest domain is troubleshooting, which means the exam rewards symptom-to-cause reasoning rather than parts-list memorization.
Mobile Devices covers repair, connectivity, and support
The 13% mobile domain includes batteries, keyboards, RAM, HDD/SSD, wireless cards, privacy/security hardware, antennas, cameras, microphones, accessories, USB/Lightning/NFC/Bluetooth, docking stations, port replicators, cellular/Wi-Fi/hotspot, SIM/eSIM, location services, MDM, and mobile synchronization.
The emphasis is practical: given a symptom, identify the likely component, connection, policy, or support action.
Networking is a broad 23% foundation
Core 1 includes common TCP/UDP ports, DNS, DHCP, HTTP/HTTPS, SMB, SSH, RDP, wireless bands/channels/standards, Bluetooth/NFC/RFID, server roles, network appliances, IoT, DNS record types, DHCP configuration, VLANs, VPNs, networking hardware, SOHO configuration, internet connection types, and tools.
A subnetting and IPv4 refresh helps because many SOHO and troubleshooting questions assume comfort with address, mask, gateway, DHCP, and APIPA behavior.
Wireless knowledge includes modern 6 GHz concepts
The V15 objectives explicitly include 2.4 GHz, 5 GHz, and 6 GHz frequency bands, channel selection, widths, regulations, and 802.11 standards. Candidates should understand interference, range, channel overlap, and why a client may connect poorly even when the access point is functioning.
Bluetooth, NFC, and RFID belong to the same domain but solve very different short-range communication problems.
Hardware is 25% and spans the whole PC lifecycle
The hardware domain covers displays, cables/connectors, RAM, storage devices, RAID, motherboards, CPUs, add-on cards, UEFI/BIOS settings, TPM/Secure Boot, cooling, power supplies, printers/MFPs, and printer maintenance.
The exam expects compatibility reasoning: correct socket, form factor, connector, wattage, storage interface, memory type, expansion slot, or display cable for the scenario.
Storage now emphasizes NVMe, M.2, RAID, and device fit
Candidates should compare HDD and SSD characteristics, SATA, NVMe, PCIe, SAS, M.2, mSATA, removable media, optical storage, and RAID 0/1/5/6/10. The strongest preparation links each choice to performance, redundancy, form factor, and compatibility.
A support technician should be able to explain why a drive is not detected, why an array is degraded, or why the selected interface cannot work in the available slot.
Motherboard and firmware objectives include modern security
ATX/microATX/ITX, CPU sockets, PCI/PCIe, power, SATA, headers, M.2, boot settings, USB permissions, TPM, Secure Boot, firmware passwords, temperature monitoring, virtualization support, x86/x64 and ARM all appear in the objectives.
The technician needs enough firmware literacy to distinguish a hardware problem from a disabled feature or incorrect boot/security setting.
Virtualization and cloud computing account for 11%
The exam covers VM purposes, sandboxing, development/test, application virtualization, legacy/cross-platform use, VDI, containers, Type 1/Type 2 hypervisors, private/public/hybrid/community cloud, IaaS/PaaS/SaaS, shared versus dedicated resources, metering, elasticity, availability, file synchronization, and multitenancy.
A cloud-computing foundation should remain support-focused: know what the model means for where resources live, who manages them, and how users consume them.
Troubleshooting is the largest domain at 28%
Hardware/network troubleshooting covers motherboards/RAM/CPU/power, drives/RAID, displays/projectors, mobile devices, networks, and printers. The objective language repeatedly says “Given a scenario,” signaling applied diagnosis rather than simple recall.
The current objectives document also includes CompTIA’s troubleshooting methodology as recommended job practice while explicitly noting that the methodology itself is not a formal exam objective. The role still heavily tests troubleshooting in context.
Core 1 now reflects newer support environments
V15 adds or emphasizes 6 GHz wireless, containers, DDR generations, NVMe/M.2, TPM/Secure Boot, modern mobile management, cloud models, and current endpoint/network troubleshooting. CompTIA A+ 2025 changes are worth reviewing so older 1101 study materials do not silently define your scope.
The Core 1 objectives also make clear that support technicians need customer-facing judgment as well as technical knowledge. A component may be replaceable, but the technician still needs to choose the safest and least disruptive action, preserve data where possible, verify the user’s original need, and document the result. Performance-based questions can combine several of these steps.
Networking ports should be learned with service purpose rather than as a random number list. DNS, DHCP, HTTP/S, SSH, SMTP, IMAP/POP, SMB, LDAP, RDP, FTP, and legacy NetBIOS each support recognizable workflows. A port question becomes easier when you picture the client/server interaction the protocol enables.
DNS records are more detailed in V15 than many older A+ notes suggest. A, AAAA, CNAME, MX, and TXT records appear, with TXT examples including SPF, DKIM, and DMARC for mail security. The technician is not expected to administer enterprise DNS deeply, but should understand what each record type is intended to represent.
SOHO configuration also includes IPv6 and not just private IPv4. Candidates should recognize static versus dynamic configuration, APIPA behavior, subnet mask, gateway, and the broad difference between IPv4 and IPv6 addressing. The practical skill is deciding whether a client has a valid local configuration before blaming the ISP.
Network hardware should be linked to function. Routers choose paths between networks; switches forward within a LAN; access points provide wireless access; patch panels organize cabling; firewalls enforce policy; PoE can power edge devices; modems/ONTs terminate access technologies; NICs connect endpoints. Knowing the role makes topology scenarios much easier.
Hardware compatibility is one of the most valuable Core 1 habits. CPU socket, memory generation/form factor, motherboard size, PSU wattage/connectors, storage interface, expansion slot, cooling clearance, and display/output standard all need to match. A part can be technically newer or faster and still be wrong for the system.
Printers are emphasized because they combine physical maintenance with software and network support. PCL versus PostScript, firmware, print servers, duplex/tray configuration, secured printing, scan-to-email/SMB/cloud, ADF, and technology-specific maintenance all appear in the objectives. Do not treat printers as a small legacy topic.
The troubleshooting domain’s mobile section includes swollen batteries and liquid damage, which should trigger safety awareness. A swollen battery is not a “keep testing until it works” problem. Entry-level support includes recognizing when to stop using hardware and follow safe handling or escalation procedures.
Network troubleshooting symptoms such as jitter, latency, intermittent wireless, port flapping, poor VoIP quality, and authentication failure should be mapped to likely layers. A wireless-channel problem looks different from a DHCP failure; a flapping wired port suggests link instability; bad VoIP can be congestion or latency rather than headset hardware.
Use the current V15 objectives as the final scope boundary. If an older 1101 course omits 6 GHz Wi-Fi, containers, modern mobile/MDM behavior, current hardware, or the updated troubleshooting emphasis, supplement it before relying on it for final review.
The troubleshooting methodology section in the official objectives is worth reading even though CompTIA explicitly says it is not a formal exam objective. It captures good job behavior: identify the problem, form and test a theory, implement a plan, verify full functionality, and document. The exam’s 28% troubleshooting domain still rewards that structured mindset through scenario-based symptoms.
Networking tools are easy marks only if you know their purposes. A crimper and stripper prepare cable, a punchdown tool terminates conductors on blocks, a toner/probe identifies cable runs, a cable tester checks wiring, a loopback plug tests interfaces, a Wi-Fi analyzer examines radio conditions, and a network tap allows observation of traffic. Tool choice should follow the question you need to answer.
The hardware domain also expects candidates to recognize display technologies and attributes. IPS, TN, VA, OLED, and mini-LED have different characteristics, while resolution, refresh rate, pixel density, and color gamut describe display behavior. Troubleshooting questions may combine a display symptom with the wrong source/input/cable rather than a failed panel.
Power supply questions are practical compatibility questions. Input voltage, 3.3/5/12V outputs, motherboard and component connectors, wattage, modular design, redundancy, and efficiency all matter. An undersized PSU can produce instability that looks like motherboard or GPU failure.
Cooling should be studied with symptom awareness. Fans, heatsinks, thermal paste/pads, and liquid cooling protect CPUs and other components from thermal throttling or shutdown. Overheating symptoms can include sluggish performance, crashes, or random shutdown rather than a clear temperature warning.
Core 1’s mobile objective also includes corporate application support and synchronization. Calendar, contacts, mail, cloud storage, data caps, MDM policy, and network settings can create support tickets even when the device’s hardware is healthy. Mobile troubleshooting is therefore both physical and service-oriented.
Internet connection types—fiber, cable, DSL, cellular, satellite, WISP—should be compared by medium, expected latency, availability, and equipment rather than by memorized marketing speeds. The technician needs to understand what termination device or signal path is likely in the scenario.
Cloud computing questions stay at a fundamentals level. IaaS, PaaS, SaaS, private/public/hybrid/community cloud, elasticity, metered use, multitenancy, file synchronization, and shared/dedicated resources are enough to identify how responsibility and consumption differ.
Performance-based preparation should reflect the official equipment list: desktops/laptops, mobile devices, SOHO router/switch, AP, VoIP phone, printers, hypervisor host, patch panel, UPS, common cables, storage, power, RAM, and network tools. You do not need every item physically, but visual and functional familiarity matters.
The current A+ 1200-series update is best treated as a job-role refresh rather than a completely new certification. Core support fundamentals remain, but the hardware, networking, cloud, mobile, and troubleshooting examples have been modernized for today’s entry-level technician environment.
Within the broader CompTIA certification path, 220-1201 is foundational but practical. A candidate who can recognize symptoms, choose compatible hardware, configure basic networks, and troubleshoot methodically is closer to the exam’s intended job role than someone who only memorizes acronyms.