CompTIA 220-1201 Cheat Sheet: Hardware, Mobile, and Troubleshooting

CompTIA 220-1201 cheat sheet covering mobile devices, networking, hardware, cloud, and troubleshooting.

Use this for last-mile review. Core 1 usually rewards calm support logic: identify the fault lane first, choose the least intrusive useful next step, and do not confuse connector shape, feature support, printer engine faults, or network naming issues.

APIPA: Automatic private IPv4 address in the 169.254.0.0/16 range that usually signals a DHCP failure path.

Least intrusive step: The smallest useful action that tests the likely theory without creating unnecessary disruption.

SOHO: Small office or home office environment, which shows up often in router, Wi-Fi, and support scenarios.

Fast lane picker

If the symptom is really about… Focus first on… Strongest first move
no link, no address, or intermittent network cable, link light, DHCP, VLAN, DNS classify names vs addressing vs physical path
printer output or feed problem image path vs paper path decide whether the page is wrong or the paper movement is wrong
storage or boot behavior SATA vs NVMe, form factor, BIOS/UEFI, SMART separate connector, protocol, and startup-path issues
mobile or accessory issue radios, battery, pairing, sync, supported standard choose the feature boundary first
display or peripheral mismatch port shape vs capability support verify supported feature set, not just connector fit

Core 1 troubleshooting order

    flowchart LR
	  A["Read the symptom"] --> B["Pick the fault lane"]
	  B --> C["Hardware, network, printer, mobile, or display"]
	  C --> D["Choose the least intrusive next step"]
	  D --> E["Verify before replacing parts"]

220-1201 answer sequence

Use this when the stem mixes hardware, network, printer, mobile, or display clues.

    flowchart TD
	  S["Scenario"] --> L["Pick the fault lane"]
	  L --> A["Check addressing or physical path first"]
	  A --> H["Check hardware or connector capability"]
	  H --> V["Verify before replacing parts"]

What to notice:

  • many A+ misses come from replacing parts before proving the fault lane
  • the exam often rewards the safest useful next step, not the biggest fix
  • the line between connector, protocol, and capability matters a lot on Core 1

Ports and protocols you must know

Service Port(s) Fast cue
SSH 22 secure remote admin
HTTP / HTTPS 80 / 443 web traffic
DNS 53 name resolution
DHCP 67/68 address assignment
RDP 3389 remote desktop
SMTP 25 or 587 outbound mail
IMAP / POP3 143 / 110 plus TLS variants mail retrieval
LDAP / LDAPS 389 / 636 directory access

Addressing and naming quick rules

Clue What it usually means Strongest first check
169.254.x.x DHCP failure path scope, relay, VLAN, server reachability
names fail but IP works DNS problem ipconfig /all, nslookup, resolver path
intermittent drops duplicate IP, bad cable, duplex or link issue physical path before deeper theory
private IPv4 ranges 10/8, 172.16/12, 192.168/16 know them cold for quick elimination

High-confusion hardware pairs

Pair Fast distinction
M.2 vs NVMe form factor vs protocol
USB-C vs Thunderbolt connector shape vs higher-capability supported feature set
no power vs no boot electrical start failure vs startup-path failure
hotspot vs Wi-Fi join sharing mobile data vs joining an existing network
NFC vs Bluetooth tap-style proximity action vs ordinary accessory pairing
jam vs ghosting paper-feed problem vs printer image/fuser path problem

Connector and storage chooser

Requirement Strongest first fit Why
modern internal SSD with PCIe protocol M.2 NVMe if supported compact form factor with fast protocol
older 2.5-inch SATA SSD or HDD SATA data and power path common legacy or mainstream desktop fit
one-cable dock workflow supported USB-C or Thunderbolt capability shape alone is not enough
drive suddenly shows warnings SMART-driven backup and replacement path preserve data before deeper testing

Wi-Fi and SOHO chooser

Need Strongest first fit Why
stronger modern wireless security WPA3 best current consumer baseline where supported
broad compatibility with strong practical security WPA2 with AES/CCMP still very common and valid
crowded RF environment 5 GHz or 6 GHz where supported less interference than 2.4 GHz
tap-to-pay or tap-to-pair behavior NFC proximity interaction
simple home-router hardening change defaults, disable WPS, update firmware classic SOHO baseline

RAID and storage shorthand

RAID Fast memory hook
RAID 0 speed, no redundancy
RAID 1 mirror
RAID 5 parity with one-disk fault tolerance
RAID 10 mirror plus stripe, best redundancy + performance combo on the exam

Printer quick map

Symptom Likely cause Strongest first step
ghosting drum or fuser behavior inspect or replace imaging/fusing components
streaks or repeated marks drum, toner, or residue path clean or replace affected unit
jam rollers, path, humidity, feed issue clear path and inspect feed components
faint print toner/transfer issue replace toner or inspect transfer path
Laser process order Memory hook
processing -> charging -> exposing -> developing -> transferring -> fusing -> cleaning know the image path cold

Display and mobile quick map

Symptom Strongest first move
no signal on display check cable, input source, seating, and port compatibility
artifacts or tearing test cable, port, and driver path
battery draining fast background apps, radios, brightness, battery health
accessory will not pair verify radio, mode, pairing profile, and supported standard
phone needs tap-based payment or pairing think NFC before Bluetooth

CLI and support tools

Need Tool
IP and DHCP details ipconfig /all
path or reachability test ping, tracert
DNS test nslookup
file or disk repair chkdsk, diskpart
system file repair sfc /scannow, DISM
event review Event Viewer

Common Core 1 traps

  • choosing a disruptive fix before checking cable, link, power, or settings
  • confusing connector shape with protocol or feature support
  • treating snapshots like full backups
  • leaving WPS or default credentials enabled on SOHO gear
  • calling a DNS symptom a DHCP symptom just because both are “networking”
  • replacing a printer for an issue that is really a maintenance-part problem

Last 15-minute review

Review this Because it fixes…
APIPA, private IPv4, DNS vs DHCP network-name and addressing confusion
key ports and protocols service-identification misses
USB-C vs Thunderbolt, M.2 vs NVMe connector and capability confusion
RAID shorthand storage-choice misses
laser printer process and defects printer symptom mistakes
least-intrusive troubleshooting order overreaction and unnecessary replacement

What strong answers usually do

  • classify the symptom before naming the fix
  • choose the least intrusive useful next step
  • protect physical basics before chasing advanced explanations
  • separate connector, capability, and protocol cleanly

Quiz

Loading quiz…

From here, use the study plan if you need pacing, the glossary if terms blur together, and the resources page when you need current official CompTIA references.

Revised on Sunday, May 10, 2026