220-1201 — CompTIA A+ Core 1 Exam Blueprint

How to Use This Exam Blueprint

Use this checklist as a practical readiness map for CompTIA A+ Core 1 (220-1201). It is designed to help you turn broad exam topics into review tasks, hands-on checks, and scenario decisions.

For each area, ask:

• Can I explain the concept without looking it up?
• Can I choose the right component, tool, cable, port, or service for a scenario?
• Can I troubleshoot from symptoms instead of jumping to a memorized answer?
• Can I distinguish similar technologies, such as DNS vs. DHCP, SATA vs. NVMe, or WPA2 vs. WPA3?
• Can I recognize what information matters in a diagram, command output, device label, or support ticket?

This page is independent exam-blueprint support for candidates preparing for the real CompTIA A+ Core 1 (220-1201) exam. It is not affiliated with CompTIA.

Exam Identity

Readiness Area Map

Exact exam weighting is not provided here, so use these as topic areas, not weighted percentages.

What “Ready” Means for Core 1

Core Hardware Checklist

Motherboards, CPUs, and Firmware

Check that you can:

• Identify common motherboard form factors at a support level, such as full-size, compact, and small-form-factor boards.
• Explain why CPU socket compatibility matters.
• Recognize the role of CPU cores, threads, cache, integrated graphics, and virtualization support.
• Distinguish firmware setup tasks from operating system tasks.
• Change boot order conceptually without confusing it with disk partitioning.
• Recognize when a firmware update may help and why it should be done carefully.
• Identify expansion slots and know why slot type, physical size, and bandwidth matter.
• Recognize onboard components such as audio, video, network, TPM/security modules, headers, and ports.

RAM

Storage

RAID Readiness

Power, Cooling, and Physical Components

Check that you can:

• Match a no-power symptom to power supply, outlet, battery, adapter, power button, or motherboard possibilities.
• Recognize PSU connectors such as motherboard, CPU, PCIe, SATA power, and legacy peripheral connectors at a practical level.
• Explain why wattage, form factor, efficiency, and required connectors matter when replacing a PSU.
• Identify overheating symptoms: shutdowns, throttling, fan noise, thermal warnings, intermittent crashes.
• Choose basic cooling actions: clean vents, verify fans, reseat heat sink when appropriate, replace thermal material when required.
• Distinguish integrated graphics from discrete graphics.
• Identify common display connections such as HDMI, DisplayPort, DVI, VGA, and USB-C display modes.
• Recognize common peripheral connections, including USB-A, USB-C, Thunderbolt/USB4-style ports, audio, Ethernet, and memory card slots.

Cables, Connectors, and Tools

Mobile Devices and Laptop Checklist

Laptop Hardware

Be ready to support these parts and symptoms:

Mobile Connectivity and Features

Check that you can:

• Distinguish Wi-Fi, Bluetooth, NFC, cellular, GPS, and hotspot/tethering use cases.
• Troubleshoot pairing problems: range, discovery mode, previous pairing, battery, interference.
• Identify airplane mode as a cause of multiple radio-related problems.
• Explain basic SIM/eSIM and cellular service dependency at a support level.
• Recognize mobile sync categories: email, contacts, calendar, photos, files, and app data.
• Distinguish local device storage from cloud-synced storage.
• Identify when docking, port replication, or adapter compatibility matters.

Mobile Troubleshooting Prompts

Networking Fundamentals Checklist

IP Addressing and Core Services

Address Clue Table

Common Ports and Protocols to Recognize

The exam may test whether you can match a service, protocol, and troubleshooting clue. Do not memorize ports in isolation; connect each one to its use.

Network Devices

Wi-Fi Readiness

SOHO Network Configuration Tasks

Can you do these conceptually?

• Place modem/ONT, router, switch, and access point in a sensible order.
• Choose DHCP for typical client addressing.
• Reserve or statically assign addresses for infrastructure devices when appropriate.
• Configure a secure Wi-Fi network name and password.
• Identify when a guest network is appropriate.
• Explain port forwarding at a high level.
• Recognize double NAT symptoms in small networks.
• Distinguish WAN settings from LAN settings.
• Identify ISP outage vs. local Wi-Fi issue vs. local device issue.

Printers and Peripherals Checklist

Printer Technology Readiness

Laser Printing Process

Be ready to place symptoms near the right stage:

Printer Troubleshooting Cues

Virtualization and Cloud Basics Checklist

Virtualization

Check that you can:

• Explain what a virtual machine is.
• Identify the role of a hypervisor.
• Distinguish host resources from guest resources.
• Allocate CPU, RAM, storage, and network access appropriately.
• Recognize that overcommitting resources can affect performance.
• Distinguish snapshots from backups.
• Explain bridged, NAT, and host-only VM networking at a basic level.
• Identify when virtualization support must be enabled in firmware.
• Recognize VM use cases: testing, sandboxing, legacy applications, training labs, isolated environments.

Cloud Concepts

Cloud and Virtualization Scenario Prompts

Hardware and Network Troubleshooting Workflow

Use a consistent method. The exact wording may vary by training source, but the support logic should be stable: identify the problem, form a theory, test it, act carefully, verify, and document.

    flowchart TD
	    A[Identify the problem] --> B[Gather details and reproduce if possible]
	    B --> C[Establish a likely theory]
	    C --> D[Test the theory]
	    D -->|Theory confirmed| E[Plan and implement fix]
	    D -->|Theory not confirmed| F[Escalate or form new theory]
	    E --> G[Verify full functionality]
	    G --> H[Document findings, actions, and outcome]

Scenario Decision Table

Command and Output Readiness

You do not need to become a network engineer for Core 1, but you should recognize what common diagnostic outputs are telling you.

Windows-style Network Checks

ipconfig /all
ping 127.0.0.1
ping <default-gateway>
ping <known-public-IP>
ping <hostname>
nslookup <hostname>
tracert <hostname>

Linux/macOS-style Network Checks

ip addr
ifconfig
ping <host>
traceroute <host>
dig <hostname>

Readiness focus:

• Can you identify the local IP address?
• Can you spot an APIPA/link-local-style clue?
• Can you tell whether DNS is likely involved?
• Can you distinguish “local network works” from “internet works”?
• Can you decide the next test instead of running commands randomly?

“Can You Do This?” Core 1 Skills Checklist

Hardware Selection and Identification

• Given a motherboard, identify likely CPU, RAM, expansion, storage, and power compatibility concerns.
• Choose SSD vs. HDD based on speed, capacity, cost, shock resistance, and use case.
• Explain why M.2 does not automatically mean NVMe.
• Choose a PSU based on connectors, physical fit, and system load.
• Identify likely causes of overheating.
• Match display cables and adapters to monitor/projector scenarios.
• Distinguish a failed drive from a missing boot configuration clue.
• Identify safe ESD handling before replacing RAM, storage, or expansion cards.

Networking

• Match DHCP, DNS, NAT, gateway, and firewall to their roles.
• Identify common ports by service and use case.
• Choose the correct cable/tool for a network cabling problem.
• Explain 2.4 GHz vs. 5 GHz vs. 6 GHz tradeoffs.
• Select secure wireless settings for a small network.
• Troubleshoot “connected, no internet” using IP, gateway, and DNS checks.
• Recognize when a device has self-assigned addressing.
• Identify when interference, distance, or placement affects Wi-Fi.

Mobile and Laptop Support

• Replace or reseat common laptop components conceptually.
• Diagnose battery, adapter, screen, keyboard, and dock symptoms.
• Troubleshoot Bluetooth pairing.
• Explain cloud sync vs. local storage.
• Identify when a mobile issue is radio, account, app, accessory, or hardware related.

Printers

• Put the laser printing process in order.
• Match print-quality symptoms to likely components.
• Distinguish driver, queue, network, and hardware printer issues.
• Choose maintenance actions for inkjet, laser, thermal, impact, and 3D printer scenarios.
• Identify when paper type, tray settings, or application settings cause print problems.

Virtualization and Cloud

• Explain VM host vs. guest resource use.
• Choose NAT, bridged, or isolated-style VM networking conceptually.
• Distinguish snapshot from backup.
• Match SaaS, PaaS, and IaaS to examples.
• Identify cloud service dependency on internet, identity, permissions, and provider availability.

Common Weak Areas and Exam Traps

Scenario Cues to Practice

Use these as quick oral drills. For each one, state the likely cause, the next test, and the least-invasive action.

Hands-On Review Tasks

If you have access to equipment or a safe lab environment, do these before final review:

• Open a desktop case and identify motherboard, RAM, storage, PSU connectors, fans, and expansion slots.
• Identify ports on a laptop, desktop, monitor, dock, and router.
• Run basic network checks and explain the output.
• Log into a SOHO router interface in a lab or simulator and identify WAN, LAN, DHCP, Wi-Fi, and guest network settings.
• Pair and unpair a Bluetooth device.
• Connect an external display and change display mode.
• Add or inspect a printer queue and identify driver/port/queue settings.
• Create or inspect a virtual machine and identify CPU, RAM, storage, and network settings.
• Practice reading device labels: wattage, voltage, model number, serial number, MAC address, SSID, and port labels.

Final-Week Checklist

Seven to Five Days Out

• Review every topic area in this checklist and mark each as green, yellow, or red.
• Drill ports and protocols daily in short sessions.
• Rework weak hardware comparison topics: RAM, storage, RAID, display, USB, power, and cooling.
• Practice network scenarios involving DHCP, DNS, gateway, Wi-Fi, and cabling.
• Review printer symptoms and the laser printing process.
• Complete scenario-based practice, not just definition recall.

Four to Two Days Out

• Create a one-page quick sheet for ports, IP clues, Wi-Fi tradeoffs, printer symptoms, and RAID concepts.
• Practice explaining answers out loud: “I choose this because…”
• Review missed questions by topic, not just by answer.
• Focus on confusing pairs: DNS/DHCP, SATA/NVMe, M.2/PCIe, router/switch/AP, POP3/IMAP, snapshot/backup.
• Do at least one mixed review set under timed conditions if available.

Day Before

• Stop trying to learn large new topics.
• Review your quick sheet.
• Revisit only high-value weak areas.
• Confirm exam logistics, identification, time, and testing environment requirements through the appropriate official exam channels.
• Sleep instead of cramming late.

Exam-Day Mindset

• Read the full scenario before choosing.
• Look for the task word: identify, choose, troubleshoot, configure, or explain.
• Prefer the least-invasive reasonable step when troubleshooting.
• Use elimination for distractors that solve a different problem.
• Watch for clues: recent change, one user vs. many users, local vs. network, wired vs. wireless, IP vs. DNS.
• If a question feels broad, anchor it to the symptom and the environment described.

Practical Next Step

Choose your weakest two readiness areas from this checklist and do targeted practice before moving on. For CompTIA A+ Core 1 (220-1201), the highest-value review usually combines hardware identification, network troubleshooting, ports/protocols, printer symptoms, and scenario-based decision practice.