Browse CompTIA Certification Guides

CompTIA 220-1201 Guide: A+ Core 1

CompTIA 220-1201 exam guide covering mobile devices, networking, hardware, cloud, and troubleshooting decisions.

This guide turns CompTIA A+ Core 1 220-1201 into a real technician workflow instead of a loose list of ports, cables, and printer facts. Core 1 is still entry-level, but the questions usually reward candidates who can choose the right part, setting, standard, or first troubleshooting step without overreacting.

PBQ: Performance-based question that asks you to troubleshoot, sequence, match, or configure something instead of only picking one definition.

SOHO: Small office or home office environment, the scale CompTIA often uses for router, Wi-Fi, DHCP, and VPN questions.

V15: The current A+ product version that contains the 220-1201 and 220-1202 exam pair.

Current exam snapshot

As of March 29, 2026, CompTIA’s current Core 1 page lists:

Item Current CompTIA signal
Version V15
Exam code 220-1201
Launch date March 25, 2025
Question count Maximum of 90
Exam style Single-response, multiple-response, drag-and-drop, and PBQ items
Duration 90 minutes
Passing score 675 on a 100-900 scale
Languages English, German, and Japanese
Recommended experience 12 months in an IT support specialist role
Retirement model Usually three years after launch (estimated 2028)
Full-cert rule Core 1 and Core 2 must be passed from the same V15 series

What Core 1 is really testing

CompTIA is not mainly testing whether you can memorize every connector name in isolation. It is testing whether you can:

  • recognize the most likely component, standard, or setting from a realistic symptom
  • understand which wired, wireless, storage, printer, or mobile detail actually matters
  • troubleshoot in a calm order instead of replacing parts blindly
  • apply support logic at the home, help-desk, and junior field-tech level

How this guide is structured

    flowchart LR
	  S["Study Plan"] --> D["5 official domains"]
	  D --> L["Lesson pages"]
	  L --> C["Cheat Sheet and Glossary"]
	  C --> F["FAQ and Resources"]

What to notice:

  • the chapter pages follow CompTIA’s official Core 1 domains directly
  • the lesson pages split the broadest objective groups into clearer support-sized learning units
  • the appendix pages help with review, but the lesson pages stay the main learning units

Coverage map for the current guide

Domain Weight Lesson count Focus
1. Mobile 13% 4 laptops, accessories, mobile networking, and phone or tablet triage
2. Network 23% 4 ports, addressing, SOHO setup, Wi-Fi, cabling, and basic tools
3. Hardware 25% 5 internal components, power, cooling, storage, connectors, and printers
4. Cloud 11% 2 hypervisors, VMs, VDI, thin clients, and cloud service models
5. Troubleshooting 28% 5 symptom-first diagnosis across PCs, mobile devices, printers, and networks

Best entry path by background

Starting point Protect these chapters first Why
new help-desk learner 3. Hardware, 2. Network, then 5. Troubleshooting most misses come from compatibility basics and weak fault classification
already working on tickets 5. Troubleshooting, 3. Hardware, then 1. Mobile operational readers usually need cleaner component and symptom vocabulary
pairing Core 1 with Core 2 3. Hardware, 2. Network, 5. Troubleshooting Core 1 provides the hardware and path model that later OS and security questions depend on

High-confusion boundaries this guide keeps separate

If two ideas feel similar Core 1 usually wants you to separate them like this
connector shape vs feature support a port can look correct and still lack the needed capability
no power vs no boot electrical start failure is different from startup-path failure
DNS vs DHCP naming is different from automatic addressing
image-quality defect vs feed-path issue the printed page can reveal whether the printer engine or paper movement is at fault
hotspot vs Wi-Fi join sharing a cellular connection is different from connecting to an existing network

If two answers both sound right

Use these tie-breakers:

  • choose the least disruptive step that still tests the theory
  • match the answer to the exact symptom boundary, not just the broad technology area
  • protect physical basics before chasing advanced software explanations
  • prefer the option that fits CompTIA’s support workflow rather than an enterprise-only design habit

Where to spend time if your misses still feel random

  • go back to 3. Hardware if you keep confusing connectors, storage, memory, or printer parts
  • go back to 2. Network if names, ports, Wi-Fi, or router behavior blur together
  • go back to 5. Troubleshooting if you jump to replacement before classifying the fault lane
  • go back to 1. Mobile if accessory, sync, pairing, or battery questions still feel vague

Support pages

Use these pages beside the main lessons, not instead of them:

In this section

Revised on Sunday, May 10, 2026
220-1202