Everything on the exam, in one place: the five domains and their weights, a four-week study plan, a readiness checklist you can tick off, and ports / RAID / cloud cheat sheets — with explained, sourced sample questions throughout.
CompTIA A+ Core 1 (220-1201) validates that you can install, configure, and troubleshoot PC hardware, mobile devices, networking, and basic cloud and virtualization. Here are the numbers that shape how you should study.
A+ is two separate exams — Core 1 (220-1201) and Core 2 (220-1202); you need both to certify. This guide covers Core 1. With up to 90 questions in 90 minutes, that's about a minute per item, and the performance-based questions (drag-and-drop and simulations) take longer — so pace yourself. The exam spans five domains, and Hardware (25%) and Hardware & Network Troubleshooting (28%) together make up over half the exam, so they deserve the most study time.
What each domain covers, plus one explained, sourced sample question so you can see the depth the exam expects. Expand a domain to dig in.
A user needs a single laptop port that carries data, video to an external display, and power delivery over one reversible cable. Which interface fits?
Which TCP port does HTTPS use to serve TLS-encrypted web traffic?
Which RAID level writes an identical copy of all data to two drives, giving redundancy but no capacity gain?
A company uses a web-based email suite it neither installs nor patches — the provider manages everything. Which cloud service model is this?
Using CompTIA's best-practice methodology, what is the step immediately after establishing a theory of probable cause?
A realistic schedule at roughly 10 hours per week. Adjust to your experience — but keep the heaviest weeks on Hardware and Troubleshooting, since they're the biggest slices of the exam.
Components, RAM and storage types, RAID levels, connectors and cables, and laptop/mobile hardware. Read every answer explanation — even on questions you get right.
Common ports and protocols, TCP vs UDP, IPv4/IPv6 basics, Wi-Fi standards, and SOHO router/firewall setup. Memorize the ports table cold.
Hypervisor types, VMs, and the IaaS/PaaS/SaaS models; then begin the 6-step methodology and common hardware symptoms.
Take full timed mock exams, use the per-domain breakdown to find weak areas, and re-drill them. Keep the last days light.
Tick off each topic as it clicks. Your progress is saved in this browser, so you can come back to it.
Saved only in your browser — nothing leaves this device.
The reference tables worth memorizing cold — common ports, RAID levels, cloud models, and the troubleshooting methodology. Bookmark this.
| Port | Protocol | Purpose |
|---|---|---|
| 20 / 21 | FTP | File transfer (data / control) |
| 22 | SSH / SFTP | Encrypted remote shell & file transfer |
| 23 | Telnet | Remote shell — cleartext, insecure |
| 25 | SMTP | Sending email |
| 53 | DNS | Name resolution (TCP & UDP) |
| 67 / 68 | DHCP | Automatic IP configuration |
| 80 | HTTP | Web (unencrypted) |
| 110 | POP3 | Retrieving email (download) |
| 143 | IMAP | Retrieving email (server-side) |
| 161 / 162 | SNMP | Device monitoring & traps |
| 389 | LDAP | Directory services |
| 443 | HTTPS | Web (TLS-encrypted) |
| 445 | SMB / CIFS | Windows file sharing |
| 3389 | RDP | Remote desktop (Windows) |
| RAID | Technique | Min disks | Redundancy |
|---|---|---|---|
| 0 | Striping | 2 | None — speed/capacity only |
| 1 | Mirroring | 2 | Survives one drive failure |
| 5 | Striping + distributed parity | 3 | Survives one drive failure |
| 10 | Stripe of mirrors (1+0) | 4 | Survives one per mirror set |
| Model | You manage | Example |
|---|---|---|
| IaaS | OS, apps, data (provider gives VMs/storage/network) | Cloud VMs & block storage |
| PaaS | Apps & data (provider gives the runtime/platform) | Managed app/runtime platform |
| SaaS | Just your data & settings (provider runs the app) | Web email / office suite |
| Deployment: public · private · hybrid · community | ||
| # | Step |
|---|---|
| 1 | Identify the problem |
| 2 | Establish a theory of probable cause (question the obvious) |
| 3 | Test the theory to determine cause |
| 4 | Establish a plan of action and implement the solution |
| 5 | Verify full system functionality and apply preventive measures |
| 6 | Document findings, actions, and outcomes |
Take a free, explained practice test and see exactly which domains need more work.
Start a practice test