CompTIA A+ Core 1 (220-1201) Study Routine: Hardware + Networking + Mobile + Virtualization + Troubleshooting (What toDo

If you want your first IT job (help desk, desktop support, field tech), A+ Core 1 is one of the fastest ways to prove you can handle real break/fix work. The catch is that 220-1201 is not a “memorize definitions” exam. You have to diagnose symptoms, pick the right tool, and fix the problem without making it worse.

This post gives you a specific routine you can start today: what to study, how to practice, and how to know you are exam-ready.

220-1201 in 60 seconds (so you plan correctly)

Core 1 (220-1201) is up to 90 questions in 90 minutes, and the passing score is 675 on a 900-point scale. The US exam voucher price is typically $265 per exam (A+ requires Core 1 and Core 2).

Core 1 domain weights (use these to budget time)

How to use this: if you have 40 total study hours, you should spend about 11 hours on troubleshooting (28%), 10 hours on hardware (25%), 9 hours on networking (23%), 5 hours on mobile (13%), and 4 hours on virtualization/cloud (11%).

The A+ Core 1 “two-pass” study system (works even if you are busy)

Most people fail Core 1 because they do one pass through content and then jump to random practice tests. Instead, use two passes:

Pass 1 (Build the map)

Goal: understand what each objective is asking you to DO.

- Watch/read content quickly.

- Build a one-page cheat sheet per domain.

- Do small, targeted quizzes (10-15 questions) immediately after each topic.

Pass 2 (Build the reflex)

Goal: fix problems fast under time pressure.

- Do mixed sets (40-60 questions) and review every miss.

- Practice troubleshooting as a process (symptom -> isolate -> test -> verify).

- Drill high-frequency tables (ports, Wi-Fi standards, cables, storage types).

A 14-day study schedule you can actually follow

This is a realistic plan for someone doing 60 to 90 minutes a day. If you have more time, keep the sequence but increase question volume.

Week 1: Build the map

Day 1 - Baseline + setup

- Take a 30-question diagnostic quiz.

- Create a “missed questions notebook” with 3 columns:

- What I chose

- Why it is wrong

- The rule I will use next time

Day 2 - PC hardware fundamentals (CPU, RAM, motherboard, power)

- Hands-on (15 minutes): open a PC (or watch a teardown if you cannot), identify components and connectors.

- Drill: RAM types, channels, and common symptoms (no POST, beep codes, intermittent crashes).

Day 3 - Storage (HDD vs SSD, SATA vs NVMe, RAID basics)

- Practice: match symptoms to likely cause:

- Slow boot + 100% disk usage

- Clicking HDD

- Drive not detected

- Know what you would try first: reseat cable, check BIOS/UEFI detection, SMART status, try another port.

Day 4 - Displays and peripherals

- Drill: connectors and use-cases (HDMI, DisplayPort, USB-C, Thunderbolt).

- Printer basics: laser vs inkjet, common maintenance items, and when to suspect driver vs hardware.

Day 5 - Mobile devices (laptops, battery, displays, input devices)

- Study like a technician:

- Battery not charging -> check AC adapter, wattage, DC jack, battery health.

- No display -> external monitor test, brightness/function keys, backlight/inverter (older), cable seating.

Day 6 - Networking essentials (the minimum you must memorize)

Build one table you can rewrite from memory:

- IP basics: DHCP vs static, default gateway, DNS.

- Common ports: at least 22, 23, 25, 53, 67/68, 80, 110, 143, 443, 3389.

- Tools: ping, ipconfig/ifconfig, tracert/traceroute, nslookup/dig.

Day 7 - Virtualization and cloud basics

- Define in your own words:

- What a hypervisor is

- What a VM needs (CPU/RAM/storage/network)

- IaaS vs PaaS vs SaaS (and a real example for each)

- Mini-lab: create a VM (VirtualBox/VMware) or review screenshots and identify settings (RAM, vCPU, NAT vs bridged).

Week 2: Build the reflex (troubleshooting-first)

Day 8 - Hardware troubleshooting patterns

Make a “symptom to first action” list:

- Random shutdowns -> overheating, failing PSU, bad fan.

- No power -> outlet, PSU switch, cable, PSU test, motherboard.

- No boot device -> boot order, drive detection, cable, OS not found.

Day 9 - Wired network troubleshooting

Practice diagnosis by layers:

- Link light off -> cable, port, NIC, switch.

- APIPA address (169.254.x.x) -> DHCP issue, cable, VLAN, scope.

- DNS failure -> test by pinging IP vs name, then switch DNS.

Day 10 - Wireless troubleshooting (where exam questions get sneaky)

Be ready to choose the best next step:

- “Connected, no internet” -> check gateway/DNS, captive portal, IP settings.

- Slow Wi-Fi -> channel overlap, interference, distance, band steering.

- Cannot join -> wrong password, security mode mismatch (WPA2/WPA3), MAC filtering.

Day 11 - Mixed set (60 questions) + deep review

Rules for review:

- If you miss a question because of memorization (ports, cable types), add it to flashcards.

- If you miss because of process (troubleshooting), write the decision rule.

- If you miss because of vague reading, rewrite the question in your own words.

Day 12 - PBQ-style practice (even without full PBQs)

Simulate tasks using checklists:

- Configure a SOHO network layout: modem -> router -> switch -> clients.

- Choose the right Wi-Fi settings for an office vs home.

- Match tools to problems (cable tester for physical, toner probe for tracing, loopback for NIC testing).

Day 13 - Final weak areas (targeted)

Use your missed-question notebook to pick the top 3 weak topics and do:

- 20 focused questions each

- 10 minutes of recall: rewrite your cheat sheet without looking

Day 14 - Full timed set + readiness check

- Do a 90-question timed set.

- Goal benchmarks:

- 80%+ overall

- 75%+ in troubleshooting and networking

- If you are under target, do another 3-day mini-cycle: (1) content refresh, (2) focused questions, (3) mixed timed.

High-yield Core 1 skill drills (do these daily in 10 minutes)

These are small drills that produce big score gains.

Drill 1: “What is the first thing you check?”

Write your answer before looking at choices.

- No power

- No display

- No network

- Slow PC

- Overheating

This trains you to pick the best next step instead of “a step that could work.”

Drill 2: Build a personal ports list (and stop at what matters)

You do not need every port ever created. You do need common ones cold.

- Daily recall: write 10 ports from memory.

- Weekly: add 2 more until you can do the common set without hesitation.

Drill 3: Cable and connector recognition

Create a photo folder (or flashcards) for:

- RJ-45 vs RJ-11

- USB-C vs Thunderbolt

- SATA data vs SATA power

- M.2 SATA vs M.2 NVMe (keying awareness)

The exam loves “identify the correct connector/tool” style questions.

Troubleshooting framework you can use on the exam

When you see a troubleshooting question, run this mental script:

1) Identify the symptom category - Power, POST/boot, performance, network, display, peripheral.

2) Check the simplest constraint first

- Power and cables.

- Correct port and correct connector.

- Basic settings (Wi-Fi off, airplane mode, wrong SSID).

3) Isolate by swapping one variable

- Different cable, different port, different device.

- External monitor.

- Known-good power adapter.

4) Confirm with a tool

- Cable tester/toner.

- ipconfig/ping/nslookup.

- SMART/diagnostics.

5) Fix and verify - Do not stop at “it worked once.” Verify stability.

Exam-day execution tips (Core 1 specific)

• PBQs first or last? If PBQs slow you down, flag them and come back after you secure easy multiple-choice points.

• Read the last line first: Many questions hide the actual task at the end (identify the BEST next step, MOST likely cause, FIRST action).

• Avoid “over-fixing”: CompTIA questions usually reward the least invasive step that proves or eliminates a hypothesis.

FAQ

How many practice questions should I do for 220-1201?

A strong minimum is 600 to 1,000 quality questions with full review. The review is the real work. If you only do questions and never analyze misses, you are just repeating mistakes faster.

What should I memorize vs understand?

Memorize: common ports, common Wi-Fi/security modes, basic cable/connector IDs, tool names. Understand: troubleshooting flow, how DHCP/DNS failures look, why a system overheats, what changes when you move from HDD to SSD to NVMe.

Is hands-on required to pass Core 1?

Not strictly, but hands-on massively reduces “guessing.” Even basic labs like setting up a home router, creating a VM, reseating RAM, or swapping cables will make questions feel obvious.

What are the most common score-killers?

• Weak networking fundamentals (especially DNS vs DHCP symptoms)

• Confusing connectors and cables

• Not having a consistent troubleshooting approach

• Skipping virtualization/cloud because it is “only 11%”

How do I know I am ready to schedule the exam?

When you can:

- Score 80%+ on timed mixed sets

- Explain why each wrong answer is wrong (not just why the right one is right)

- Solve troubleshooting questions by process, not by luck

Turn this into daily momentum

If you want a routine that is easy to maintain, do this every day:

- 20 minutes learning

- 30 minutes targeted questions

- 10 minutes troubleshooting drill

Start practicing today at study.cyberexamprep.com with unlimited questions across all CompTIA exams.