CompTIA A+ Core 1 Quick Review
This Quick Review is an IT Mastery study companion for candidates preparing for CompTIA A+ Core 1 (220-1201). Use it to refresh the most testable ideas before moving into topic drills, mock exams, and original practice questions with detailed explanations.
The real exam rewards practical recognition: identify the device, isolate the symptom, choose the safest next step, and know which technology best fits a small-business or support scenario.
How to Use This Review
- Scan the tables first. Ports, connectors, wireless standards, storage types, and troubleshooting symptoms are common scenario anchors.
- Practice decision rules. Many questions ask for the “best,” “first,” or “most likely” answer.
- Use question-bank practice after each section. Do not just memorize terms; practice applying them to support tickets.
- Review missed explanations carefully. A missed A+ Core 1 question often comes from confusing two similar technologies.
Practical target: after reviewing a topic, you should be able to recognize it from symptoms, identify compatible components, and choose the next troubleshooting action.
High-Yield Core 1 Topic Map
| Area | What to Know Fast | Common Exam Angle |
|---|
| Mobile devices | Laptop parts, displays, batteries, docking, wireless, mobile accessories | Replace/upgrade the correct component |
| Networking | Ports, protocols, IPv4/IPv6, wireless, cabling, SOHO devices | Identify service, symptom, or configuration issue |
| Hardware | Motherboards, CPUs, RAM, storage, power, printers, displays | Select compatible hardware or diagnose failure |
| Virtualization/cloud | VM resources, hypervisors, cloud models, cloud characteristics | Match service model or deployment need |
| Troubleshooting | Methodical diagnosis, hardware symptoms, network symptoms | Choose the best next step |
Core Troubleshooting Method
Most scenario questions expect disciplined troubleshooting, not random replacement.
flowchart TD
A[Identify the problem] --> B[Establish a theory]
B --> C[Test the theory]
C -->|Theory confirmed| D[Plan and implement the fix]
C -->|Theory not confirmed| B
D --> E[Verify full functionality]
E --> F[Document findings and actions]
Common Troubleshooting Traps
| Trap | Better Exam Behavior |
|---|
| Replacing hardware before testing | Confirm the likely cause first |
| Ignoring user changes | Ask what changed recently |
| Skipping simple checks | Verify power, cables, links, and settings |
| Choosing the most technical option | Choose the most appropriate support step |
| Fixing one symptom only | Verify full functionality afterward |
| Forgetting documentation | Document after resolution |
Hardware Foundations
Motherboard and Expansion Review
| Component | Key Idea | Watch For |
|---|
| CPU socket | Must match CPU family and board | Physical compatibility matters |
| Chipset | Determines supported features | CPU support, PCIe lanes, RAM type |
| RAM slots | Must support correct RAM generation and speed | DDR generations are not interchangeable |
| PCIe slots | Used for GPUs, NICs, storage adapters, capture cards | Larger slots can often support smaller cards physically, but performance depends on lanes |
| M.2 slot | Used for SSDs and sometimes wireless cards | M.2 keying and protocol matter |
| SATA ports | Connect SATA SSDs, HDDs, optical drives | Slower than modern NVMe |
| Front-panel headers | Power switch, reset, LEDs, USB, audio | Miswiring can cause “dead” front-panel behavior |
| CMOS/UEFI firmware | Hardware initialization and configuration | Boot order, TPM, virtualization support |
CPU Review
| Concept | Quick Review |
|---|
| Cores | Physical processing units |
| Threads | Logical execution paths |
| Clock speed | Cycles per second; not the only performance factor |
| Cache | Fast memory inside/near CPU |
| Integrated GPU | Graphics built into CPU or chipset platform |
| Virtualization support | Required or recommended for many VM use cases |
| Thermal design | CPU requires correct cooling and thermal paste |
RAM Review
| Term | Meaning | Common Mistake |
|---|
| DIMM | Desktop memory module | Confusing with laptop memory |
| SO-DIMM | Laptop/small-form memory module | Installing wrong form factor |
| DDR generations | DDR3, DDR4, DDR5, etc. | Assuming different generations fit |
| ECC | Error-correcting memory | Often used in servers/workstations |
| Dual-channel | Matched memory channels improve performance | Installing mismatched modules poorly |
| Speed/latency | Performance characteristics | Board/CPU may run RAM below rated speed |
Storage Review
| Storage Type | Strengths | Weaknesses / Exam Clues |
|---|
| HDD | Large capacity, lower cost | Mechanical failure, slow access, noise |
| SATA SSD | Faster than HDD, common upgrade | Limited by SATA interface |
| NVMe SSD | Very fast, uses PCIe | Requires compatible M.2/PCIe support |
| Optical drive | Legacy media, recovery discs | Less common in modern systems |
| External USB storage | Portable backup/transfer | Cable, port, or power limitations |
| NAS | Network-based shared storage | Depends on network access and permissions |
HDD vs SSD Symptoms
| Symptom | More Likely Cause |
|---|
| Clicking, grinding, long seek delays | HDD mechanical failure |
| Slow boot on old system | HDD bottleneck or failing drive |
| System no longer detects drive | Cable, port, controller, drive failure, or firmware setting |
| Fast boot improvement after upgrade | HDD replaced with SSD |
| Sudden read/write errors | Drive failure, file system issue, or storage controller problem |
RAID Quick Review
| RAID Level | Minimum Drives | Main Benefit | Main Risk / Note |
|---|
| RAID 0 | 2 | Performance / combined capacity | No fault tolerance |
| RAID 1 | 2 | Mirroring / redundancy | Capacity efficiency is lower |
| RAID 5 | 3 | Striping with parity | Can tolerate one drive failure |
| RAID 10 | 4 | Mirroring + striping | Good performance and redundancy, more drives required |
Decision rule: if the scenario says speed only, think RAID 0. If it says simple redundancy, think RAID 1. If it needs redundancy with better capacity efficiency, consider parity-based RAID. If it needs performance and redundancy, consider RAID 10.
Power and Cooling
Power Supply Concepts
| Concept | What It Means |
|---|
| Wattage | Total power capacity |
| Efficiency rating | How efficiently AC is converted to DC |
| Modular PSU | Detachable cables reduce clutter |
| 24-pin motherboard connector | Main board power |
| CPU power connector | Dedicated CPU power |
| PCIe power | Extra power for graphics cards |
| SATA power | Storage drives and some accessories |
Power Troubleshooting Clues
| Symptom | Likely Area |
|---|
| No power, no fans, no lights | Outlet, power cable, PSU switch, PSU |
| Powers on then shuts off | Overheating, short, PSU, CPU cooling |
| Random shutdowns under load | PSU capacity, heat, failing component |
| Burning smell | Stop and inspect; do not keep powering on |
| New GPU causes instability | Insufficient PSU wattage or missing PCIe power |
Cooling Review
| Cooling Item | Purpose |
|---|
| Heat sink | Transfers heat away from CPU/GPU |
| Thermal paste | Improves contact between chip and heat sink |
| Fan | Moves air over heat sink or through case |
| Liquid cooling | Uses pump/radiator loop |
| Airflow direction | Front/bottom intake, rear/top exhaust is common |
| Dust removal | Restores cooling efficiency |
Common trap: adding more fans does not help if airflow is blocked, the heat sink is loose, or thermal paste is missing.
Displays, Video, and Connectors
| Connector | Common Use | Notes |
|---|
| HDMI | TVs, monitors, projectors | Carries audio and video |
| DisplayPort | Monitors, docking, high refresh | Common on business systems |
| USB-C | Data, power, display, docking | Capabilities vary by device and cable |
| Thunderbolt | High-speed data/display/docking | Uses USB-C connector in newer versions |
| VGA | Legacy analog video | No audio, lower quality |
| DVI | Older digital/analog display | Legacy desktop displays |
Display Symptoms
| Symptom | Check First |
|---|
| No display | Power, input source, cable, brightness, external/internal toggle |
| Dim laptop screen | Brightness, backlight, inverter on older systems |
| Flickering | Cable, refresh rate, GPU driver, panel issue |
| Artifacts | GPU, overheating, cable, display panel |
| External display works but internal does not | Laptop screen, cable, backlight, display settings |
Printers
Printers are heavily scenario-driven. Know the print technology, the imaging process, and which consumable causes which symptom.
Printer Types
| Printer Type | Strengths | Common Issues |
|---|
| Laser | Fast text, office use | Toner, drum, fuser, transfer roller, paper path |
| Inkjet | Photos, color, low initial cost | Ink cartridges, clogged nozzles, alignment |
| Thermal | Receipts, labels | Thermal paper, print head |
| Impact | Multipart forms | Ribbon, tractor feed, print head |
| 3D printer | Physical objects | Filament, bed leveling, nozzle clogs, adhesion |
Laser Printing Process
| Step | Purpose |
|---|
| Processing | Printer receives and prepares job |
| Charging | Drum receives electrical charge |
| Exposing | Laser writes image to drum |
| Developing | Toner attaches to image areas |
| Transferring | Toner moves from drum to paper |
| Fusing | Heat/pressure bond toner to paper |
| Cleaning | Excess toner removed |
Printer Symptom Table
| Symptom | Likely Cause |
|---|
| Streaks or lines | Dirty rollers, toner/drum issue, inkjet clogged nozzle |
| Faded print | Low toner/ink, economy mode, transfer issue |
| Ghosting | Fuser or drum problem |
| Paper jams | Rollers, paper type, tray alignment, debris |
| Creased paper | Rollers, paper path, fuser |
| Blank pages | Empty toner/ink, transfer issue, wrong driver, sealed cartridge |
| Speckling | Toner spill, drum, cleaning issue |
| Incorrect colors | Calibration, cartridge, color profile, driver |
| 3D print not sticking | Bed leveling, bed temperature, surface prep |
| 3D stringing | Temperature/retraction settings |
Common trap: for laser printers, repeated image defects often point to a rotating component such as the drum or fuser.
Mobile Devices
Laptop Hardware
| Component | Review Point |
|---|
| Battery | Swollen or failing batteries require careful replacement |
| Keyboard/touchpad | Often replaceable as assemblies |
| Display panel | Match size, connector, resolution, mounting |
| Wi-Fi/Bluetooth card | May use M.2 or proprietary form factor |
| Storage | M.2 NVMe, SATA M.2, or 2.5-inch SATA depending on model |
| Memory | Often SO-DIMM, but some systems have soldered RAM |
| Webcam/microphone | Privacy settings and drivers can mimic hardware failure |
| Docking station | Can provide power, display, USB, Ethernet, audio |
Mobile Accessories
| Accessory | Exam-Relevant Idea |
|---|
| Port replicator/dock | Expands connectivity |
| Touch pen/stylus | Digitizer support may be required |
| Screen protector | Physical protection |
| Privacy filter | Limits viewing angle |
| External keyboard/mouse | Bluetooth or USB |
| Hotspot | Shares cellular data over Wi-Fi |
| Headset | Audio input/output support |
| NFC devices | Short-range tap-based communication |
Mobile Device Connectivity
| Technology | Use Case |
|---|
| Wi-Fi | Local wireless networking |
| Bluetooth | Short-range peripherals |
| NFC | Tap-to-pair or tap-to-pay style interactions |
| Cellular | Mobile WAN access |
| GPS | Location services |
| USB tethering | Share mobile data over USB |
| Mobile hotspot | Share cellular data over Wi-Fi |
Mobile Troubleshooting Clues
| Symptom | First Checks |
|---|
| Battery drains quickly | Screen brightness, background apps, weak signal, battery health |
| Device will not charge | Cable, charger, port debris, battery, charging settings |
| Overheating | Apps, environment, battery, blocked ventilation |
| No wireless | Airplane mode, Wi-Fi toggle, saved network, signal |
| No Bluetooth pairing | Discoverability, distance, previous pairing, battery |
| Touchscreen unresponsive | Restart, clean screen, case/screen protector, digitizer |
| App crashes | Update app/OS, clear cache, storage space, reinstall |
Networking Essentials
Common Ports and Protocols
| Port | Protocol / Service | Quick Memory Cue |
|---|
| 20/21 | FTP | File transfer |
| 22 | SSH | Secure remote shell |
| 23 | Telnet | Insecure remote shell |
| 25 | SMTP | Send mail |
| 53 | DNS | Name resolution |
| 67/68 | DHCP | Automatic IP addressing |
| 80 | HTTP | Web traffic |
| 110 | POP3 | Receive mail, download-oriented |
| 143 | IMAP | Receive mail, sync-oriented |
| 161/162 | SNMP | Network management |
| 389 | LDAP | Directory services |
| 443 | HTTPS | Secure web traffic |
| 445 | SMB/CIFS | Windows file sharing |
| 3389 | RDP | Remote Desktop |
Common trap: SMTP sends, while POP3/IMAP receive. If the user can receive but not send mail, look at SMTP settings, authentication, firewall, or provider restrictions.
TCP vs UDP
| Protocol | General Behavior | Examples |
|---|
| TCP | Connection-oriented, reliable delivery | HTTP/S, FTP, SSH, SMTP, IMAP, RDP |
| UDP | Connectionless, lower overhead | DNS queries, DHCP, streaming, VoIP, some VPN traffic |
Decision rule: if reliability and ordered delivery are central, TCP is usually involved. If speed, broadcast/discovery, or real-time tolerance is central, UDP may be involved.
IP Addressing Review
IPv4 Basics
| Concept | Review |
|---|
| IPv4 address | 32-bit address, commonly dotted decimal |
| Subnet mask | Separates network and host portions |
| Default gateway | Router used to reach other networks |
| DNS server | Resolves names to IP addresses |
| DHCP | Automatically assigns IP settings |
| Static IP | Manually assigned configuration |
| APIPA | Self-assigned address when DHCP fails, commonly 169.254.x.x |
IPv4 Private Address Ranges
| Range | Common Use |
|---|
| 10.x.x.x | Private networks |
| 172.16.x.x through 172.31.x.x | Private networks |
| 192.168.x.x | Home and small office networks |
IPv6 Basics
| Concept | Review |
|---|
| IPv6 address | 128-bit address written in hexadecimal groups |
| Link-local | Local network segment communication |
| Global unicast | Publicly routable IPv6 address |
| Loopback | ::1 |
| SLAAC | IPv6 automatic address configuration method |
Quick IP Symptom Rules
| Symptom | Likely Issue |
|---|
| 169.254.x.x address | DHCP failure |
| Can ping IP but not name | DNS issue |
| Can reach LAN but not internet | Gateway, routing, ISP, firewall |
| One device offline | Local device config, cable, Wi-Fi, NIC |
| All devices offline | Router, modem, ISP, switch, power |
| Duplicate IP warning | Static conflict or DHCP issue |
Network Devices
| Device | Function |
|---|
| Modem | Connects to ISP access network |
| Router | Routes between networks |
| Switch | Connects devices within a LAN |
| Wireless access point | Provides Wi-Fi access to wired LAN |
| Firewall | Filters traffic based on rules |
| Patch panel | Cable termination/organization |
| PoE switch/injector | Provides power over Ethernet |
| NAS | Shared network storage |
| VoIP phone | Voice over IP endpoint |
| Load balancer | Distributes traffic across servers |
| Proxy | Intermediary for client requests |
SOHO Router Review
Know these configuration areas:
- SSID and wireless security
- Admin password change
- Firmware updates
- DHCP scope
- DNS settings
- Port forwarding
- Guest network
- MAC filtering
- Firewall rules
- QoS
- Static reservations
- Channel selection
- 2.4 GHz vs 5 GHz vs 6 GHz behavior
Common trap: hiding the SSID is not strong security. Use modern encryption and strong credentials.
Wireless Networking
Wi-Fi Frequency Bands
| Band | Strengths | Limitations |
|---|
| 2.4 GHz | Longer range, better wall penetration | More interference, fewer non-overlapping channels |
| 5 GHz | Faster, less crowded than 2.4 GHz | Shorter range |
| 6 GHz | More spectrum, high performance | Shorter range, newer device support required |
Wireless Standards Quick View
| Standard | Common Band | Relative Idea |
|---|
| 802.11a | 5 GHz | Older |
| 802.11b | 2.4 GHz | Older, slow |
| 802.11g | 2.4 GHz | Older |
| 802.11n | 2.4/5 GHz | Wi-Fi 4 generation |
| 802.11ac | 5 GHz | Wi-Fi 5 generation |
| 802.11ax | 2.4/5/6 GHz depending on implementation | Wi-Fi 6 / 6E generation |
| 802.11be | 2.4/5/6 GHz depending on implementation | Wi-Fi 7 generation |
Wireless Troubleshooting
| Symptom | Check |
|---|
| Weak signal | Distance, obstacles, antenna, AP placement |
| Slow Wi-Fi | Interference, band, channel, client capability |
| Drops near microwave/Bluetooth | 2.4 GHz interference |
| Can connect but no internet | Gateway, DNS, DHCP, ISP |
| Only old devices fail | Security mode, band support, standard compatibility |
| Roaming problems | AP placement, signal overlap, client behavior |
Cabling and Connectors
| Cable / Connector | Use |
|---|
| RJ45 | Ethernet twisted pair |
| RJ11 | Telephone/DSL-style connections |
| F-type | Coaxial cable, cable internet/TV |
| LC/SC/ST | Fiber connectors |
| USB-A | Common legacy USB host port |
| USB-C | Reversible connector for data/power/display |
| Lightning | Apple mobile accessory connector on many older devices |
| SATA | Internal storage data connection |
| Molex | Legacy internal power connector |
| IEC power cable | Common desktop/monitor power cable |
Copper Ethernet
| Term | Review |
|---|
| Cat 5e | Common gigabit-capable cabling |
| Cat 6 | Higher performance than Cat 5e |
| Cat 6a | Better for higher-speed/longer supported runs |
| Plenum | Fire-rated jacket for air-handling spaces |
| Shielded twisted pair | Helps reduce interference |
| Unshielded twisted pair | Common general Ethernet cabling |
Fiber Review
| Fiber Type | Review |
|---|
| Single-mode | Longer distances, laser light |
| Multimode | Shorter distances, common inside buildings |
| Fiber advantage | Long distance, high bandwidth, EMI resistance |
| Fiber caution | Fragile, requires correct optics/connectors |
| Tool | Use |
|---|
| Cable tester | Checks cable continuity/wiring |
| Loopback plug | Tests port transmit/receive |
| Toner probe | Traces cable paths |
| Crimper | Attaches connectors |
| Punchdown tool | Terminates wires to patch panels/keystone jacks |
| Wi-Fi analyzer | Reviews channels, signal, interference |
| Multimeter | Tests voltage/continuity |
| Network tap | Captures traffic passively |
| Time-domain reflectometer | Locates cable faults/distance to fault |
| Command | Use |
|---|
| ipconfig / ifconfig / ip | View IP configuration |
| ping | Test basic reachability |
| tracert / traceroute | Show route path |
| nslookup / dig | Test DNS resolution |
| netstat | View connections/listening ports |
| arp | View IP-to-MAC mappings |
| route | View or modify routing table |
| hostname | Display system name |
| net use | Map/use Windows network resources |
Command Decision Rules
| Scenario | Best First Command |
|---|
| “What IP address did DHCP assign?” | ipconfig / ifconfig / ip |
| “Can this host reach the gateway?” | ping |
| “Where does the path fail?” | tracert / traceroute |
| “Is DNS resolving this hostname?” | nslookup / dig |
| “What connections are open?” | netstat |
| “Is the MAC address cached?” | arp |
Virtualization
Virtualization Basics
| Concept | Review |
|---|
| Virtual machine | Software-defined computer running on a host |
| Host | Physical system running the virtualization platform |
| Guest | VM operating system |
| Hypervisor | Software layer that runs VMs |
| Type 1 hypervisor | Runs directly on hardware |
| Type 2 hypervisor | Runs on top of a host OS |
| Virtual switch | Connects VMs to networks |
| Snapshot | Point-in-time VM state |
| Resource allocation | CPU, RAM, storage, and network assigned to VM |
VM Resource Traps
| Trap | Review |
|---|
| Too little RAM | Guest OS runs slowly or fails |
| Too little storage | Install/update failures |
| No virtualization support enabled | VM performance/features may fail |
| Network mode confusion | NAT, bridged, and host-only behave differently |
| Snapshot as backup | Snapshots are not a full backup strategy |
| Overcommitting resources | Host and guests all suffer performance issues |
VM Network Modes
| Mode | Behavior |
|---|
| NAT | VM shares host network access behind translation |
| Bridged | VM appears as a peer on the physical network |
| Host-only | VM communicates with host/private virtual network only |
| Internal/private | VM communicates with selected VMs only |
Cloud Computing
Cloud Service Models
| Model | Provider Manages More? | Candidate Must Recognize |
|---|
| IaaS | Less | Virtual machines, storage, networks |
| PaaS | Medium | App platform/runtime without managing servers directly |
| SaaS | More | Complete application delivered over network |
Decision rule: if the customer manages the OS, think IaaS. If the customer deploys code to a managed platform, think PaaS. If the customer simply uses the application, think SaaS.
Cloud Deployment Models
| Model | Meaning |
|---|
| Public cloud | Shared provider infrastructure |
| Private cloud | Cloud-like environment dedicated to one organization |
| Hybrid cloud | Mix of private and public resources |
| Community cloud | Shared by organizations with common needs |
Cloud Characteristics
| Characteristic | Review |
|---|
| Rapid elasticity | Scale resources up/down quickly |
| Metered utilization | Pay/measure by usage |
| High availability | Designed to reduce downtime |
| File synchronization | Keep files consistent across devices |
| Shared resources | Multi-tenant/provider infrastructure |
| Virtual desktop | Desktop environment delivered remotely |
Common trap: cloud does not automatically mean “more secure,” “always cheaper,” or “no administration.” The correct answer depends on requirements.
Hardware Troubleshooting Review
Startup and Boot Symptoms
| Symptom | Likely Area |
|---|
| No POST | Power, motherboard, CPU, RAM |
| Beep codes/diagnostic lights | Check vendor diagnostics meaning |
| Boot device not found | Drive, boot order, cable, OS boot files |
| Continuous reboot | Power, overheating, OS, driver, RAM |
| Blue screen/kernel panic | Driver, hardware, memory, storage, OS |
| Date/time resets | CMOS battery or firmware settings |
| Slow boot | Startup apps, storage, malware, failing drive, low RAM |
| Symptom | Likely Cause |
|---|
| System slow overall | Low RAM, slow storage, background processes, malware, overheating |
| Slow only on network resources | Network, DNS, server, wireless, bandwidth |
| Freezes under heavy load | Heat, RAM, PSU, driver |
| Loud fans | Heat, dust, fan curve, failing fan |
| App-specific slowness | Application, storage, memory, compatibility |
Hardware Replacement Decision Points
| If the Scenario Says… | Think About… |
|---|
| “After adding RAM, system will not boot” | Compatibility, seating, slot order |
| “After moving PC, no display” | Loose cable/card/RAM |
| “After power outage” | PSU, surge damage, file system corruption |
| “After installing GPU” | PSU wattage, PCIe power, drivers |
| “After BIOS/UEFI change” | Boot order, secure boot, storage mode |
| “Only one USB device fails” | Device/cable/port compatibility |
| “All USB devices fail” | Controller, driver, BIOS/UEFI, power |
Network Troubleshooting Review
Connectivity Scenario Table
| Scenario | Most Likely Direction |
|---|
| One wired device offline | Cable, port, NIC, IP config |
| Multiple wired devices on same switch offline | Switch, uplink, VLAN, power |
| One wireless device offline | Wi-Fi settings, saved profile, adapter, signal |
| All wireless devices offline | AP/router, internet, DHCP, power |
| User has IP but no DNS | DNS setting or DNS server |
| User has APIPA | DHCP not reachable |
| Intermittent connectivity | Cable damage, interference, failing hardware, IP conflict |
| Slow internet for everyone | ISP, router, bandwidth saturation, DNS |
| Slow access to one site | Site, routing, DNS, remote service |
Network Layer Thinking
Use this simplified path when a device cannot reach a resource:
- Physical/link: cable, Wi-Fi signal, link lights.
- IP configuration: IP address, subnet mask, gateway, DNS.
- Local reachability: ping loopback, own IP, gateway.
- Remote reachability: ping external IP.
- Name resolution: test DNS.
- Application/service: port, firewall, credentials, server.
Security-Relevant Core 1 Concepts
Although Core 1 is hardware/network focused, some questions include basic security context.
| Concept | Why It Matters |
|---|
| WPA2/WPA3 | Wireless encryption/security modes |
| Guest network | Separates visitors from internal resources |
| Default admin password | Must be changed on SOHO devices |
| Firmware updates | Fix bugs and security issues |
| Evil twin/rogue AP | Wireless impersonation risk |
| Physical privacy filter | Prevents shoulder surfing |
| Cable locks | Physical device theft deterrent |
| NFC/Bluetooth controls | Reduce unwanted pairing or data exposure |
| Secure disposal | Storage devices may contain sensitive data |
Common trap: do not choose convenience over basic protection when the question asks for the best secure configuration.
High-Yield “Best Answer” Decision Rules
| Question Wording | What to Do |
|---|
| “First” | Choose the earliest safe diagnostic step |
| “Best” | Choose the most complete and appropriate answer |
| “Most likely” | Match the strongest symptom clue |
| “Least expensive” | Avoid unnecessary replacement |
| “Secure” | Prefer stronger encryption/authentication/configuration |
| “Small office/home office” | Think practical router, Wi-Fi, DHCP, NAT, basic firewall |
| “Intermittent” | Consider heat, loose cables, interference, failing components |
| “After upgrade/change” | Focus on the recent change |
| “All users affected” | Look upstream or shared infrastructure |
| “One user affected” | Look at local device/configuration |
Common Candidate Mistakes
Memorization Without Scenario Practice
Knowing that DNS uses port 53 is useful. But the exam may describe a user who can reach 8.8.8.8 but cannot open websites by name. That is a DNS scenario, not a generic “internet down” scenario.
Confusing Similar Technologies
| Confused Pair | Difference |
|---|
| Router vs switch | Router connects networks; switch connects devices within a network |
| Modem vs router | Modem connects ISP medium; router routes/NATs between networks |
| Access point vs router | AP provides wireless access; router routes traffic |
| DNS vs DHCP | DNS resolves names; DHCP assigns IP settings |
| POP3 vs IMAP | POP3 downloads mail; IMAP syncs mail |
| SATA SSD vs NVMe SSD | Both can be SSDs; interface/protocol differs |
| USB-C vs Thunderbolt | Same connector may not mean same capabilities |
| Type 1 vs Type 2 hypervisor | Bare-metal vs hosted |
| SaaS vs PaaS | Complete app vs managed app platform |
| RAID 0 vs RAID 1 | Striping speed vs mirroring redundancy |
Overlooking Compatibility
Core 1 frequently tests whether a part actually fits or works:
- RAM generation and form factor
- CPU socket and chipset
- PSU wattage and connectors
- M.2 keying and NVMe/SATA support
- Laptop display connector and size
- Docking station power/display support
- Wi-Fi standard and band support
- Printer driver and operating system compatibility
Rapid Review Tables
“What Failed?” Symptom Anchors
| Clue | Think |
|---|
| Clicking drive | HDD failure |
| 169.254 address | DHCP failure |
| Can ping IP, not name | DNS failure |
| Ghost images on laser print | Drum/fuser area |
| Laptop shuts off under load | Heat or power |
| New RAM causes no boot | RAM compatibility/seating |
| Wi-Fi weak far from router | Range/interference |
| Only send mail fails | SMTP |
| No boot device | Drive detection or boot order |
| Random reboots after GPU upgrade | PSU or heat |
| VM cannot access LAN like a normal host | Network mode may be NAT/host-only |
| 3D print warping | Bed temperature/adhesion/material |
| Need | Tool |
|---|
| Trace cable in wall | Toner probe |
| Verify Ethernet pinout | Cable tester |
| Terminate patch panel | Punchdown tool |
| Attach RJ45 connector | Crimper |
| Check voltage | Multimeter |
| Analyze Wi-Fi channels | Wi-Fi analyzer |
| Test NIC port | Loopback plug |
| Capture traffic | Network tap |
“Which Network Service?” Anchors
| Need | Service |
|---|
| Assign IP addresses automatically | DHCP |
| Resolve names to IP addresses | DNS |
| Secure remote command-line access | SSH |
| Insecure legacy remote command line | Telnet |
| Secure web access | HTTPS |
| Windows file/printer sharing | SMB |
| Remote Windows GUI session | RDP |
| Send email | SMTP |
| Sync mailbox folders | IMAP |
Practice Plan After This Quick Review
Use this page as a checklist, then move into IT Mastery practice:
- Start with topic drills for ports, protocols, hardware, printers, mobile devices, and networking.
- Review detailed explanations for every missed question, including why the wrong options are wrong.
- Mix topics after drilling. The real exam can combine hardware, networking, and troubleshooting in one scenario.
- Take mock exams only after targeted drilling. Use mock results to find weak areas, not just to predict readiness.
- Redo missed questions later. Repetition after a delay confirms whether you learned the concept.
Final Readiness Checklist
Before sitting for CompTIA A+ Core 1 (220-1201), make sure you can:
- Identify common ports, protocols, and network services from scenarios.
- Troubleshoot DHCP, DNS, gateway, Wi-Fi, and cabling problems.
- Distinguish routers, switches, access points, modems, firewalls, and NAS devices.
- Match storage, RAM, CPU, motherboard, and power components for compatibility.
- Diagnose printer issues by printer type and symptom.
- Recognize laptop and mobile device replacement/connection scenarios.
- Explain basic virtualization and cloud service models.
- Apply a structured troubleshooting process without skipping verification.
- Choose the safest and most practical “first” or “best” action.
For the next step, use original practice questions in a question bank with focused topic drills and detailed explanations so you can convert this Quick Review into exam-ready decision-making.
Continue in IT Mastery
Use this Quick Review as a final concept map, then move into IT Mastery for focused topic drills, mixed practice sets, timed mock exams, and detailed explanations. The practice questions are original IT Mastery practice items; they are not official CompTIA questions, copied live-exam content, or exam dumps.