CompTIA A+ Core 1 (220-1201) Study Guide: Format, Domains, Cost, and How to Pass

CompTIA A+ Core 1 (220-1201) is the hardware half of the A+ certification — the industry’s standard entry credential for IT support technicians. The exam gives you up to 90 questions in 90 minutes, combines multiple-choice items with interactive performance-based questions (PBQs), and requires a scaled score of 675 out of 900 to pass. It covers five domains: mobile devices, networking, hardware, virtualization and cloud computing, and hardware/network troubleshooting — with troubleshooting alone worth more than a quarter of the exam. To earn the full A+ certification you must pass Core 1 and its sibling exam, Core 2 (220-1202), each with its own voucher.

This guide walks through what the certification is, exactly what the exam looks like, every domain and its weight, what it costs, how to register, a six-week study plan built around practice questions, and the tactical mistakes that cost first-time candidates a pass.

What A+ Core 1 is (and who it’s for)

A+ is where most IT careers begin. It validates that you can physically work on the machines people use every day: open a laptop and swap the RAM, terminate and identify cables, set up a small office network, configure a printer, and — above all — troubleshoot when any of it misbehaves. Core 1 (220-1201) carries the hardware, networking, mobile-device, and cloud-fundamentals material; Core 2 (220-1202) carries operating systems, security, software troubleshooting, and operational procedures.

The certification maps directly to roles like help desk technician, desktop support specialist, field service technician, and technical support associate. Many employers use it as a screening filter for entry-level postings, and U.S. government-adjacent support roles frequently require it outright. It is also the on-ramp to CompTIA’s infrastructure track: Network+ assumes A+-level familiarity with hardware, and Security+ builds on both.

There are no prerequisites. CompTIA recommends 9–12 months of hands-on lab or field experience, but that is a recommendation, not a gate. Plenty of candidates pass Core 1 as their first-ever certification with a used desktop to practice on, a structured plan, and enough practice questions to know their weak spots before exam day.

The 220-1201 objectives launched in 2025, replacing the older 220-1101 series. Make sure everything you study — videos, books, question banks — says 220-1201, because the exam version determines which technologies appear (the current version, for example, expects familiarity with Wi-Fi 6E and USB4-era connectivity that older material predates).

The 220-1201 exam at a glance

Detail	220-1201 (Core 1)
Questions	Maximum of 90
Time limit	90 minutes
Question types	Multiple-choice (single and multiple response) and performance-based questions (PBQs)
Passing score	675 on a scale of 100–900
Voucher price	$274 (CompTIA raised the per-exam price from $265 in May 2026)
Delivery	Pearson VUE — in-person test center or OnVUE online proctoring
Prerequisites	None (9–12 months of experience recommended)
Certification requirement	Pass both Core 1 (220-1201) and Core 2 (220-1202)

Two things in that table deserve emphasis. First, “maximum of 90 questions” means your form may have fewer — do not panic if the counter tops out at 82. Second, PBQs are interactive tasks, not multiple choice: you might drag device names onto a rack diagram, order installation steps, or match connectors to ports. They appear at the start of the exam, they eat time, and they are the single biggest reason candidates who only studied flashcards run out of clock.

The five domains of 220-1201

The exam blueprint assigns each domain a weight — the share of questions drawn from it. Study time should roughly follow the weights, with extra attention on troubleshooting because it also recycles every other domain’s content in scenario form.

Hardware and Network Troubleshooting — 28%

The heaviest domain on the exam, and the one that behaves least like a trivia quiz. Nearly every question is a scenario: a symptom, a context, and four plausible actions. The anchor is CompTIA’s six-step troubleshooting methodology — identify, theorize, test, plan/implement, verify, document — which the exam tests both directly (ordering PBQs) and indirectly (“what should the technician do NEXT?”).

The rest of the domain is symptom fluency. For displays, that means diagnosing a monitor with no signal (input source, cable standard, missing HDMI audio), flickering screens (refresh-rate mismatches and driver rollbacks), overscan and distorted geometry on TVs used as monitors, and dim screens and dead pixels (backlight failures versus power-saving dimming, and when a panel qualifies for replacement). For printers, know what actually causes repeated paper jams — worn feed rollers, misadjusted tray guides, multi-feeds — and what a grinding noise implicates: gear trains, duplexers, finishers, or a foreign object. Input devices show up too; a stylus that stops working (dead battery, broken Bluetooth pairing, Fn-lock quirks) is a classic quick-win question.

Study this domain last-but-continuously: every time you learn a component in the Hardware domain, immediately ask “and how does it fail?”

Hardware — 25%

The identification-and-installation core of the exam. You need to recognize cable and connector types on sight — USB generations, video standards, storage and power connectors down to legacy Molex — because connector-matching is a recurring PBQ format. RAM questions go beyond definitions into practice: installing laptop memory in matched pairs for dual-channel operation with proper electrostatic discharge (ESD) precautions.

Displays are technically “hardware” here, not troubleshooting: know the trade-offs between IPS, VA, TN, and OLED panel types, how to read monitor specifications — resolution, native resolution, refresh rate, pixels per inch, aspect ratio — and when a customer needs sRGB versus Adobe RGB color coverage for print and photo work.

Printers get heavy coverage: the seven-step laser imaging process is one of the most reliably tested sequences on the exam, and deployment questions cover print servers, queues, quotas, and driver languages. On the server side of hardware, know why racks use redundant hot-swap power supplies and how N+1 sizing works.

Networking — 23%

Core 1’s networking domain is the technician’s view, not the network engineer’s: what the boxes are, how to plug them together, and how to stand up a small office. Start with device roles — the router versus switch versus access point distinction anchors both multiple-choice comparisons and rack-diagram PBQs. Then go hands-on: a full SOHO wireless router setup — SSIDs, guest networks, channel selection, the 6 GHz band, and the security steps that belong to first boot — covers a dense cluster of objectives in one sitting. Round it out with the wide-area side: WWAN cellular connectivity, laptop WWAN cards, and hotspot options for users who work beyond Wi-Fi.

Expect port-number and protocol questions here too (the classic well-known ports), plus TCP versus UDP, common connection types, and basic IP addressing concepts like DHCP versus static assignment.

Mobile Devices — 13%

Almost entirely laptop surgery plus portable-device features. The repair-focused objectives are tested with surprising specificity: replacing a laptop Wi-Fi card means knowing M.2 form factors and the tiny U.FL/MHF4 antenna connectors with their MAIN and AUX leads, and diagnosing weak wireless after a screen repair means knowing that laptop antennas route through the hinge into the lid. Battery objectives cover calibration, cold-weather behavior, and safe disposal. Beyond repair, review docking stations versus port replicators, laptop display technologies, and mobile connection methods.

Virtualization and Cloud Computing — 11%

The smallest domain, and the most memorization-friendly. The centerpiece is the service-model ladder — IaaS, PaaS, and SaaS, and who patches what at each level — alongside deployment models (public, private, hybrid, community), cloud characteristics (elasticity, metered usage, shared resources), and client-side virtualization basics: hypervisor types, VM resource requirements, and why virtualization needs CPU support enabled in firmware. Eleven percent of 90 questions is roughly nine or ten items; this domain is the cheapest score on the exam per hour of study.

How scoring works

The 675/900 passing score is scaled, not a percentage — CompTIA weights questions and normalizes across exam forms, so “675 out of 900” does not mean “75%.” Practical implications: unanswered questions score zero, so never leave a blank; there is no penalty for guessing. PBQs are worth more than single multiple-choice items and can earn partial credit, which is why the right PBQ strategy is to attempt every part rather than skip the item. You get your pass/fail result at the test center (or on screen with OnVUE) immediately after finishing.

Mistakes that cost first-timers a pass

The Core 1 fail stories repeat themselves. These are the patterns worth engineering out of your preparation:

Studying to recognize instead of to recall. Re-reading notes and re-watching videos produces a warm feeling of familiarity that collapses the moment a question asks you to produce the fact — which imaging step follows developing, which connector feeds a SATA drive. The fix is retrieval practice: closed-book questions, self-quizzing, and writing sequences out from memory. If you can’t reconstruct the seven laser-printing steps on a blank page, you don’t know them yet, no matter how familiar the diagram looks.

Treating PBQs as a surprise. Candidates who have only ever clicked A/B/C/D lose ten minutes to shock on the first screen. Practice interactive formats before exam day — ordering tasks, matching exercises, diagram labeling — so the mechanics are boring by the time they count.

Ignoring the low-weight domains. It’s tempting to skip an 11% domain, but nine or ten cloud questions is a bigger swing than most people’s pass margin. The small domains are also the most predictable — memorizable models and definitions — so skipping them abandons the easiest points on the exam.

Memorizing answers instead of concepts. Running the same practice bank until you score 95% proves you’ve memorized that bank. Rotate question sets, and when you miss, read the explanation until you could defend the right answer to someone else. The real exam paraphrases; only concepts transfer.

Confusing Core 1 scope with Core 2 scope. Windows administration, malware removal, and security configuration live on 220-1202. Time spent drilling those for this exam is time taken from connectors, printers, and troubleshooting scenarios that will actually appear.

Booking the exam “when I feel ready.” Readiness feelings arrive well after actual readiness. Timed practice scores are the honest signal — schedule off the data, and use the open calendar date as the forcing function it is.

Registering for the exam

Registration runs through Pearson VUE, CompTIA’s exclusive delivery partner:

1. Create a CompTIA/Pearson VUE account and buy a 220-1201 voucher — $274 directly from CompTIA’s store (bundles with retake insurance or training cost more). Watch for student discounts through CompTIA’s academic store if you’re enrolled anywhere.
2. Choose a delivery mode. In-person test centers offer fewer variables — you show up with two IDs and they handle the rest. OnVUE online proctoring lets you test from home but requires a webcam, a reliable connection, a room you can clear of papers and second monitors, and a system-check run beforehand. If your home setup is questionable, book the test center.
3. Schedule the appointment. Same-week slots are usually available. Booking a date two or three weeks out is a commitment device — a real deadline does more for study discipline than any app.
4. Remember the second exam. Core 1 alone confers no certification. Budget for the Core 2 voucher and plan the second exam while Core 1’s shared concepts are fresh — most successful candidates take Core 2 within four to six weeks of Core 1.

A six-week study plan

This plan assumes 8–10 hours per week and leans on practice questions as the primary learning tool — not because reading is useless, but because Core 1 rewards recognition and recall under time pressure, and questions train exactly that.

Week 1 — Hardware foundations. Cables, connectors, RAM types, storage, motherboards, power. Get physical if possible: open a desktop, identify every connector, reseat the RAM. Finish the week with a set of Hardware-domain practice questions and log every miss.

Week 2 — Displays and printers. Panel types, monitor specs, color gamuts; then the laser imaging process until you can recite the seven steps cold, plus inkjet/thermal/impact basics and print-server deployment. These two clusters are dense with orderable, matchable facts — prime PBQ material.

Week 3 — Networking. Device roles, ports and protocols, SOHO setup, wireless standards, WWAN. Draw the rack: modem → router/firewall → switch → patch panel → devices and APs. If you have a home router, log in and actually change the SSID, the channel, and the admin password.

Week 4 — Mobile devices, virtualization, and cloud. Laptop teardown topics (Wi-Fi cards, antennas, batteries, keyboards), then the entire cloud domain in two or three sittings. Take a half-length timed quiz mixing all domains covered so far.

Week 5 — Troubleshooting. Learn the six-step methodology, then run symptom drills across every hardware category: display faults, printer faults, power faults, connectivity faults. For each practice miss, identify which step of the methodology the question was really testing.

Week 6 — Full timed practice exams. At least two 90-question, 90-minute runs under real conditions. Score by domain, then spend remaining hours only on your two weakest domains. If you’re scoring comfortably above passing on honest (not memorized) practice exams, you’re ready; if not, move the appointment rather than burning the voucher — CompTIA vouchers allow rescheduling up to 24 hours before the appointment at no charge.

Throughout all six weeks: keep a miss log. The list of questions you got wrong, reviewed weekly, is worth more than any pre-made study sheet because it is a map of your gaps, not the average candidate’s.

Exam-day tips

• Triage PBQs first, but on a timer. PBQs front-load the exam. Give each a fair attempt — partial credit is real — but if one is consuming you, flag it, guess what you can, and return after the multiple choice. A reasonable budget: no more than 25 minutes total on PBQs before your first pass through the rest.
• One minute per multiple-choice question is plenty. Most stems are answerable in 30 seconds. The time crunch candidates report almost always traces back to PBQ overruns, not the multiple choice.
• Read for the qualifier. “BEST,” “FIRST,” “MOST likely,” and “NEXT” change the answer. Two options are often both true; only one satisfies the qualifier — usually the cheapest, least invasive, or methodology-correct action.
• Answer everything. Blanks score zero, guesses might not. Before submitting, sweep for flagged and unanswered items.
• Test-center logistics: arrive 30 minutes early with two forms of ID, one government-issued with photo and signature. Lockers hold your phone. OnVUE logistics: run the system test the day before, clear the desk completely, and expect the proctor to pan your webcam around the room.
• Bring scratch strategy, not scratch paper. You’ll get an erasable board or digital notepad. First thing after the tutorial screen, jot the six troubleshooting steps and any port numbers you tend to scramble — a legal, private cheat sheet written from memory.

Quick reference

• 220-1201 (Core 1): up to 90 questions, 90 minutes, multiple-choice + PBQs, pass at 675/900.
• Voucher: $274 via Pearson VUE (test center or OnVUE online); no prerequisites.
• Domain weights: Hardware and Network Troubleshooting 28%, Hardware 25%, Networking 23%, Mobile Devices 13%, Virtualization and Cloud Computing 11%.
• A+ certification requires passing both Core 1 (220-1201) and Core 2 (220-1202).
• PBQs come first, carry partial credit, and are the main time risk — cap them and return later.
• Study weights ≈ time budget, but troubleshooting deserves extra because it recycles every other domain.
• Never leave a question blank; there is no guessing penalty.
• Keep a personal miss log and let it drive your final two weeks.