CompTIA A+ Core 1 (220-1201) FAQ — Deep-Dive Answers

What does Core 1 (220-1201) actually cover?

Core 1 emphasizes endpoint hardware, mobile devices, networking fundamentals, virtualization & client cloud, and troubleshooting. Expect practical knowledge of components, connectors, ports, Wi-Fi standards/security, storage (SATA/NVMe), RAID basics, printer workflows (laser), and methodical problem-solving.

How is Core 1 different from Core 2?

• Core 1 (220-1201): hardware, networking, mobile, printers, client virtualization, troubleshooting.
• Core 2 (220-1202): operating systems, security, software troubleshooting, operational procedures.

You must pass both to earn CompTIA A+. Order doesn’t matter.

Do PBQs appear on Core 1?

Yes. In addition to multiple-choice items, Core 1 usually includes performance-based questions (PBQs)—drag-and-drop wiring, port matching, printer flows, or simple triage tasks. If a PBQ is slow, skip and return. Don’t let one item burn your clock.

How many questions and how long is the exam?

CompTIA can vary item count and timing by form. Budget time for check-in and keep a 5–10 minute buffer to review flagged items.

Which hardware topics should I master first?

• Core components: motherboard form factors, CPU sockets, RAM types (DDR generations), PSU wattage/rails, cooling/airflow.
• Storage: HDD vs SSD, SATA vs NVMe (M.2 PCIe), form factor vs interface vs protocol.
• Peripherals: USB generations and connectors (A/C), display standards (HDMI/DP/DVI/VGA), Thunderbolt 3/4.
• BIOS/UEFI basics: boot order, secure boot, firmware updates—when and why.

What storage and RAID knowledge is most testable?

• RAID 0/1/5/10 concepts (performance vs redundancy; disk counts; one-disk fault tolerance for RAID 5).
• SMART monitoring and symptoms of failing drives.
• File systems: NTFS vs exFAT vs FAT32 (use cases).

Ports & protocols—what do I really need to memorize?

Know the common set cold: HTTP/HTTPS (80/443), SSH (22), FTP/FTPS/SFTP (21/990/22), SMTP/Submission (25/587), POP3/IMAP (+TLS 995/993), RDP (3389), DNS (53), DHCP (67/68), SNMP (161/162), LDAP/LDAPS (389/636). Practice with flashcards until instant.

Ethernet cabling—how deep does it go?

• Standards: 100BASE-TX, 1000BASE-T, 10GBASE-T and their Cat requirements/distances.
• Cables/connectors: Straight-through vs crossover (legacy), crimping pinouts (awareness), PoE basics.
• Fiber: MMF vs SMF (range), LC/SC connectors, handling/cleaning best practices.

Wi-Fi & SOHO networking—what’s expected?

• Standards: 802.11n/ac/ax; bands (2.4/5/6E), channel width basics, MIMO/MU-MIMO (awareness).
• Security order: WPA3 → WPA2 (AES/CCMP) → WPA (TKIP) → WEP (avoid).
• SOHO hardening: change defaults, set WPA2/3-Personal, strong passphrase, firmware updates, disable WPS.
• Troubleshooting tells: APIPA → DHCP issue; names fail but pings by IP work → DNS issue.

Printers: which details matter most?

• Laser process order: Processing → Charging → Exposing → Developing → Transferring → Fusing → Cleaning (memorize in order).
• Common defects & first steps: streaks/lines → drum/fuser; ghosting → fuser/drum discharge; jams → rollers/path/humidity; faint output → toner/transfer roller.
• Maintenance items: toner, drum, fuser, transfer roller, rollers—know roles and symptoms.

Mobile devices—what depth does the exam expect?

• Phone/tablet hardware basics (batteries, displays, ports) and accessories (NFC, Bluetooth profiles).
• Tethering vs hotspot, Wi-Fi calling; basic triage: Safe Mode (Android), DFU/Recovery (iOS), cache/data clear, battery health.

Virtualization & cloud on Core 1—how far do I go?

• Type 1 vs Type 2 hypervisors; VM resources (vCPU, RAM, NICs).
• Snapshots ≠ backups; short-term checkpoints only.
• Client cloud use cases: storage sync (OneDrive/Drive), thin clients, VDI awareness.

What command-line tools should I know for Core 1?

• Networking: ipconfig /all, ping, tracert, nslookup.
• Shares: net use.
• Disk/system health: chkdsk, diskpart, defrag (HDD), sfc, DISM (awareness).
• Logs: Event Viewer (System/Application) to correlate symptoms.

How should I approach troubleshooting questions?

Use the six-step method and choose the least intrusive, safest, reversible next step:

1. Identify the problem (gather, duplicate, ask what changed).
2. Establish a theory of probable cause.
3. Test the theory to confirm the root cause.
4. Plan and implement the fix.
5. Verify full functionality; implement prevention.
6. Document findings/actions/outcomes.

What are classic Core 1 “gotchas”?

• APIPA (169.254.x.x) → DHCP scope/reachability/relay or VLAN path.
• Duplicate IP → intermittent disconnects.
• Count vs for-each doesn’t apply here (Terraform topic)—don’t overthink cloud.
• NVMe not detected → seating, PCIe lanes/BIOS; boot order/UEFI vs Legacy.
• Display issues → cable/port, driver, correct input, power/backlight.
• Printer ghosting vs streaks—know which component to suspect first.

What’s a smart lab plan for Core 1?

• SOHO router lab: change admin defaults, WPA2/3-Personal, DHCP reservations, test 2.4 vs 5/6 GHz, channel selection.
• Storage drills: add a SATA SSD; initialize/partition/format; read SMART; compare NTFS vs exFAT.
• Cable sanity: identify Cat5e/6/6a, crimp a practice cable (if gear available), use a cable tester.
• Printer maintenance: replace toner/drum and fix a staged jam (with vendor guides).
• CLI reps: run ipconfig, ping, tracert, nslookup, net use, chkdsk, sfc.

What safety/ESD practices do I need to remember?

• ESD: wrist strap to ground, antistatic mat, handle boards by edges, store in ESD bags.
• Power: unplug and discharge before servicing; use surge protectors/UPS for critical devices.
• Toner cleanup: cold water; ESD-safe vacuum.
• Ergonomics: proper lifting, cable management, avoid trip hazards.

How much do I need to know about BIOS/UEFI settings?

Basics only: boot order, Secure Boot, enabling/disabling devices, XMP/DOCP memory profiles (awareness), and firmware updates when necessary for stability or compatibility (perform with caution).

What are the best ways to memorize ports/cables/Wi-Fi?

• Daily micro-drills (10–15 flashcards).
• Group by theme (web/mail/remote/infra).
• Compare/contrast tables (Cat6 vs 6a; 802.11ac vs 802.11ax).
• Teach aloud—if you can explain it clearly, you’ve learned it.

Any guidance on time management and PBQs?

• First pass fast (~60–70 seconds per MC item).
• Skip and flag PBQs if they’re time sinks; finish MC, then return.
• Keep a 5–10 minute buffer for flagged items and PBQs at the end.

How long should I study—and how should I structure it?

From some experience: 3–4 weeks. From near-zero: 5–6 weeks with labs. Suggested cadence:

• Week 1: Hardware + storage/RAID; 20-question drills daily.
• Week 2: Networking/Wi-Fi + ports; mixed sets midweek.
• Week 3: Printers + mobile + virtualization; first PBQ practice.
• Week 4: Two full mocks; convert misses into 2-bullet rules and re-drill.

What are “2-bullet rules,” and why use them?

They’re short, sticky heuristics made from your misses:

• APIPA → DHCP path before cables.
• Ghosting → fuser/drum; streaks → drum/toner.
• 5/6 GHz for throughput; disable WPS. Use them right before practice sets and on exam day for quick recall.

Should I memorize exact throughput numbers (Wi-Fi/Ethernet)?

Know orders of magnitude (e.g., 1 Gbps for 1000BASE-T; 10 Gbps for 10GBASE-T) and relative differences (ac vs ax, Cat6 vs 6a). Perfect PHY maxima matter less than picking the right standard/security for the scenario.

What do I do when a symptom has multiple plausible causes?

Apply the six-step method and pick the least intrusive reversible step that best tests your theory. For example, name resolution fails: check DNS settings before replacing cables.

Any final exam-day tips?

• Sleep, hydrate, and arrive early.
• Read the stem’s final question if the preface is long—aim your reading.
• Eliminate answers that violate safety, least-privilege/least-intrusion, or basic networking logic.
• Keep calm; use your 2-bullet rules and revisit flagged items with fresh eyes.

Quick readiness checklist

• I can match ports ↔ protocols instantly.
• I can choose the correct cable/connector (Cat6 vs 6a, LC vs SC, HDMI vs DP).
• I know 802.11 generations and WPA2/WPA3 setup basics.
• I can recite the laser printing process and map symptoms → components.
• I can explain RAID 0/1/5/10 in one sentence each.
• I can run ipconfig/ping/tracert/nslookup and interpret outputs.
• I follow a six-step troubleshooting method and pick the least intrusive next step.