CompTIA 220-1201 Study Plan: 30, 60, and 90 Days

Use this study plan when you want a disciplined path through CompTIA A+ Core 1 220-1201 without turning the exam into a random list of ports, printer parts, Wi-Fi settings, and laptop components. The goal is to build a field-tech support model: identify the symptom, classify the likely fault domain, and choose the safest next move.

Miss log: A short list of mistakes rewritten as rules you want to remember on the next set.

Mixed drill: A short review block that intentionally combines hardware, networking, mobile, and troubleshooting instead of staying in one topic lane.

Weight the plan to the exam

A practical six-week sequence

1. Week 1: 3. Hardware and 1. Mobile
2. Week 2: 2. Network
3. Week 3: finish 2. Network and start 5. Troubleshooting
4. Week 4: finish 5. Troubleshooting
5. Week 5: 4. Cloud, then mixed review
6. Week 6: review using the cheat sheet, glossary, faq, and resources

Weekly loop

    flowchart LR
	  R["Read one lesson"] --> L["Do one small lab or support drill"]
	  L --> M["Log misses as short rules"]
	  M --> C["Review cheat sheet or glossary"]
	  C --> Q["Do mixed questions"]

Drill mix that matches the exam better

Do not let all practice collapse into flashcards. A stronger Core 1 mix is:

• one hardware-compatibility or connector drill
• one networking or Wi-Fi settings drill
• one printer or troubleshooting classification drill
• one short mixed quiz block

That mix keeps the exam’s real variety visible.

Lab kit that pays off quickly

You do not need an enterprise rack. A small Core 1 kit is enough:

• an older laptop or desktop you can open safely
• one spare SATA drive or USB drive
• one router or Wi-Fi access point you can reset and reconfigure
• one smartphone or tablet for Bluetooth, Wi-Fi, tethering, and sync settings
• optional tools such as a multimeter, cable tester, crimper, and antistatic strap

What strong prep usually does

• revisits Hardware and Troubleshooting more than once
• turns misses into rules such as “names fail but IP works points to DNS before cabling”
• does one small support action after each reading block
• protects safety, ESD, and least-disruptive troubleshooting habits from the start

Booking gate before you schedule

You do not need perfect scores before booking, but you should be able to do these things cleanly:

• classify whether a symptom is mostly hardware, network, printer, or mobile
• explain the laser printer process in order without staring at notes
• separate M.2, SATA, NVMe, USB-C, and Thunderbolt without blending form factor and protocol
• identify whether a clue points first to DHCP, DNS, Wi-Fi, cabling, or gateway behavior
• finish a short mixed drill without panicking when the topic changes

PBQ prep moves that matter

When you practice PBQ-style work, bias toward:

• reading the whole exhibit before clicking
• identifying whether the question is really about hardware, mobile settings, network path, or printer process
• choosing the next action that tests the theory without creating more damage
• leaving one slow PBQ and coming back after faster items

High-yield drills that pay off late

When time gets tighter, these drills usually return more value than random rereading:

• explain the laser printing process from memory and map one symptom to one stage
• classify APIPA, DNS, gateway, and Wi-Fi clues without looking at notes
• compare M.2, SATA, and NVMe in one sentence each
• identify when a symptom is no power, no boot, or no display
• decide whether a desk-setup question is really asking for a dock, adapter, or wireless accessory

Final 72-hour plan

In the last three days:

• reread Hardware and Troubleshooting first
• use the cheat sheet to tighten ports, Wi-Fi, printers, and storage
• use the glossary only for high-confusion pairs
• use the faq and resources to confirm current exam logistics and scope

Final 24-hour bias

In the last day, do less new reading and more calm classification:

• run one short mixed drill
• reread one router page and one appendix page, not five random lessons
• review your miss log as rules, not as a pile of wrong answers
• stop early enough that fatigue does not create fake weakness on exam day

If your misses cluster in one lane

Use the miss pattern to route your review:

30-minute fallback loop

If you are short on time on a workday:

1. reread one lesson table or one chapter router section
2. perform one tiny drill such as ipconfig /all, Wi-Fi settings review, or printer-process recall
3. review one high-confusion pair from the cheat sheet
4. log one miss as a one-line rule

Quiz