Browse CompTIA Certification Guides

CompTIA 220-1201 Hardware and Network Troubleshooting Guide

CompTIA 220-1201 troubleshooting guide covering method, power, boot, connectivity, and mobile fault patterns.

This is the largest and most applied Core 1 domain. A+ is not looking for wild guesses or part-swapping. It is testing whether you can classify the symptom, form a reasonable theory, choose the safest next step, and verify the result like a real support technician.

Least intrusive step: The next move that tests your theory while minimizing risk, downtime, or unnecessary change.

Fault lane: The main symptom bucket the problem belongs to, such as PC hardware, mobile device, printer or peripheral, or network path.

Current weight in the objectives

CompTIA currently weights this domain at 28% of Core 1.

Work this domain in order

Lesson Focus
5.1 Method & Safety Use CompTIA’s six-step method, ESD awareness, and safe escalation logic.
5.2 PC Boot & Display Sort no power, no boot, slow boot, missing storage, and display-fault symptoms.
5.3 Mobile Faults Diagnose battery drain, overheating, app failure, pairing issues, and broken mobile connectivity.
5.4 Printer Faults Map printer symptoms and external-device failures to the most likely first checks.
5.5 Connectivity Faults Diagnose APIPA, DNS, weak Wi-Fi, cabling, gateway, and SOHO internet issues systematically.

Fast routing inside this chapter

If the question is really about… Go first to…
the formal CompTIA troubleshooting order 5.1 Core Troubleshooting Method & Safety
desktops or laptops that will not power, boot, detect storage, or display video 5.2 PC Power, Boot, Storage & Display Issues
phone or tablet battery, heat, sync, or radio symptoms 5.3 Mobile Device Fault Patterns
printer defects, jams, ghosting, streaking, or scanner failures 5.4 Printer and Peripheral Fault Patterns
DHCP, DNS, Wi-Fi, cabling, or internet edge problems 5.5 Wired, Wireless & Internet Connectivity Issues

What this chapter keeps separate

If the answers all sound like “troubleshooting” Keep this distinction clear
no power vs no boot vs no display electrical start, startup path, and video path are different lanes
page defect vs jam image-engine behavior is different from paper movement
DNS vs DHCP vs cabling naming, automatic addressing, and physical link are different failures
battery drain vs charging failure runtime loss is different from failure to take power correctly

What strong answers usually do

  • test the simplest likely cause first
  • avoid replacing parts before basic verification
  • distinguish link issues from service issues
  • document the result and prevent the same failure if the question gives that option

If two answers both sound right in this chapter

Use these tie-breakers:

  • choose the least intrusive useful next step
  • classify the fault as hardware, network, printer, or mobile before acting
  • trust repeatable symptom patterns more than generic “replace the part” instincts
  • keep page defects, feed-path issues, and network access issues separate

Common A+ traps

  • choosing a disruptive fix before a quick evidence-gathering step
  • mistaking DNS issues for physical-network issues
  • forgetting that printers and displays often show repeatable defect patterns
  • jumping to OS reinstallation when the symptom still points to a narrower physical or service boundary

Late-stage review bias

When time is tight, review this chapter before almost anything else except the heaviest hardware lessons.

In this section

Revised on Sunday, May 10, 2026
4. Cloud
Study Plan