← CertOwl Blog

CompTIA A+ Core 1 (220-1201): what's actually on the exam

By the founder of CertOwl • July 2026 • 3 min read

Core 1 is the first half of the CompTIA A+ certification and for most people it's their first proctored IT exam ever. This is what you're walking into.

The basics

• Exam code: 220-1201 (this is the current version, launched in March 2025; the older 220-1101 retired in September 2025, so make sure your study materials match)
• Questions: up to 90
• Time: 90 minutes
• Passing score: 675 on a scale of 100 to 900
• Question types: multiple choice, multiple response, drag and drop, and performance-based questions (PBQs)

That 675 sounds like 75%. It isn't. CompTIA uses scaled scoring, which means harder questions are worth more and the math happens behind the scenes. Don't try to calculate your score during the exam. It's a waste of the 90 minutes.

The five domains

Core 1 covers five areas. CompTIA publishes the exact breakdown in the official exam objectives, which are free to download and should be the backbone of your studying.

Mobile devices. Laptops, tablets, phones. Replacing laptop components, display types, connector types, syncing and mobile device management basics. If you've ever swapped RAM in a laptop you're ahead here.

Networking. The domain that scares beginners the most. Ports and protocols (yes, you memorize them: 80 for HTTP, 443 for HTTPS, 22 for SSH and a couple dozen more), TCP vs UDP, common hardware like switches, routers and access points, Wi-Fi standards, and small office network setup.

Hardware. The classic A+ material. RAM types, storage drives, CPUs, power supplies, cables, connectors, printers. Expect to know the difference between SATA and NVMe and what to check when a machine won't POST.

Virtualization and cloud computing. The smallest domain. Virtual machines, hypervisors, cloud models (IaaS, PaaS, SaaS), public vs private cloud. Surface level, but you need the vocabulary.

Hardware and network troubleshooting. The biggest slice of the exam. Given a scenario, figure out what's broken and what to do first. This domain rewards people who actually understand the material and punishes people who memorized flashcard answers without context.

About those PBQs

Performance-based questions are little simulations. You might get a network diagram and have to configure something, or drag components into the right order. They usually show up at the start of the exam and they eat time.

Two things matter here. First, PBQs are scored, so don't skip them entirely. Second, you can flag them and come back later. A common strategy is to look at each PBQ, and if it doesn't click within a minute, flag it, clear the multiple choice questions, then come back with the time you have left. The worst outcome is spending 25 minutes on two PBQs and rushing 70 multiple choice questions.

Where people lose points

After enough conversations with people who failed Core 1 by a hair, the same three culprits keep coming up:

1. Ports and protocols. There's no way around memorization here, and spaced repetition (short daily reviews over weeks) beats cramming the night before.
2. Troubleshooting scenarios. The exam loves "what should the technician do FIRST" questions. The answer is almost never the dramatic option. Check the cable before you replace the motherboard.
3. Time management. 90 questions in 90 minutes is one per minute. PBQs break that budget, so the multiple choice pace needs to be faster than you think.

How to prepare

Download the official 220-1201 objectives from CompTIA's site and treat them as a checklist. Watch or read a full course if you're new to the material. Then spend most of your time on practice questions, because recognizing material in a video and retrieving it under time pressure are completely different skills.

When you consistently score above roughly 80% on practice questions you haven't seen before, you're ready to book. And book the exam before you feel fully ready. A date on the calendar does more for your study schedule than any app streak ever will.

Then it's on to Core 2, which is a different beast: operating systems, security and procedures.