CompTIA A+ Core 2 (220-1202) Overview — Format, What’s Tested & How to Prepare

Everything to know before CompTIA A+ Core 2 (220-1202): exam format and pacing, who it’s for, skills measured by domain, deep readiness checklist, high-yield workflows (malware, recovery, permissions), a 3–5 week study plan, and exam-day tactics.

Exam snapshot

  • Certification: CompTIA A+ — Core 2 (220-1202)
  • Audience: Help desk/desktop support, field techs, career-switchers, students finishing A+
  • Experience target: ~6–12 months hands-on or equivalent labs/projects
  • Format: Multiple choice (single/multiple) + PBQs (performance-based questions)
  • Timing / count: Varies by form; plan a buffer to review flagged items
  • Credential requirement: Pass Core 1 (220-1201) and Core 2 (220-1202)

Study funnel: Read this Overview → work the Syllabus objective-by-objective → keep the Cheatsheet open for last-mile recall → validate with Practice.


What Core 2 measures (by theme)

1) Operating systems (Windows, macOS, Linux, ChromeOS)

  • Editions/features (e.g., Windows Home/Pro/Enterprise), updates, servicing
  • Core tools & MMCs: Device Manager, Services, Disk Management, Event Viewer, Task Manager
  • Filesystems, partitions, drivers, logs, startup items, processes

2) Security fundamentals

  • Hardening: patching, Defender/AV/EDR, firewall profiles (Domain/Private/Public)
  • Access control & authentication: accounts, UAC, least privilege, MFA/biometrics
  • Encryption basics: BitLocker/FileVault; key/recovery handling

3) Malware response workflow

  • Identification → Quarantine → Disable restore → Remediate (update, scan, remove/reimage)
  • Re-enable restore → Schedule scans/updates → Create restore point → User education

4) Software troubleshooting

  • App/driver instability, startup/services, performance bottlenecks
  • Boot failures and recovery tools (Safe Mode, WinRE, System Restore, Reset this PC)
  • Browser/profile remediation (extensions, cache/profile reset, DNS/hosts)

5) Operational procedures

  • Documentation, tickets/diagrams, asset tracking
  • Change/incident lifecycles, SLAs/OLAs, communication & professionalism
  • Safety, privacy, data handling, disposal (PII/PHI/PCI), licensing basics

6) Mobile & MDM (awareness level)

  • Enrollment, passcode policy, remote lock/wipe, Wi-Fi/VPN profiles, app allow/deny

Readiness checklist (be honest)

  • I can navigate Device Manager, Services, Disk Management, Event Viewer confidently.
  • I know when to use Safe Mode, System Restore, WinRE tools, and Reset this PC.
  • I can compute effective permissions (Share NTFS) and resolve Access Denied.
  • I can recite and justify the malware response order.
  • I can harden a workstation quickly (updates, Defender/Firewall, least privilege, BitLocker/FileVault).
  • I can run ipconfig, ping, tracert, nslookup, sfc, DISM, bootrec, bcdedit and explain outputs.
  • I understand macOS/Linux basics: where logs live, package managers, service control.
  • I can articulate change/incident steps and write a clear ticket note.

If you checked fewer than 6, slow down and spend two extra days on the Cheatsheet flows + small labs.


Compact 3–5 week study plan

Week 1 — OS Foundations

  • Windows editions/features, updates/servicing
  • Core MMCs & Settings paths; disks/partitions/filesystems; drivers/logs
  • Daily: 20-question drill (OS tools)

Week 2 — Security & Malware

  • Hardening (Firewall profiles, Defender/AV/EDR, UAC, least privilege, BitLocker/FileVault)
  • Malware workflow lab: practice the order and the “why”
  • Mixed set (OS + security)

Week 3 — Troubleshooting & Recovery

  • Startup/services, performance triage, app/driver rollbacks
  • Safe Mode vs WinRE vs Restore vs Reset (decision practice)
  • PBQ-style practice (permissions, logs, recovery)

Week 4 — Operational Procedures & MDM

  • Change/incident, tickets/diagrams, professionalism, safety/privacy/disposal
  • MDM basics (enrollment, policies)
  • Full mock #1; convert misses into 2-bullet rules; re-drill

Week 5 (optional) — Polish

  • Full mock #2; refine weak objectives; quick labs (permissions share/NTFS, malware cleanup)

High-yield workflows to memorize

Malware (must-know order)
Identify → Quarantine → Disable restore → Remediate (update, scan, remove/reimage) → Enable restore → Schedule scans/updates → Create restore pointEducate.

Recovery chooser (quick logic)

  • Driver/app broke? → Safe Mode → rollback/disable startup → test
  • System corruption? → sfcDISMSystem RestoreReset (keep/remove)
  • Boot issues? → WinRE Startup Repairbootrec / bcdedit as needed

Permissions (effective access)
Over network: Effective = most restrictive of Share & NTFS (denies override). Locally: NTFS only. Fix via group membership, inheritance, ownership.

Hardening quick-start
Updates on → Defender/Firewall on (right profile) → least privilege + UAC → encrypt disk (BitLocker/FileVault) → RDP limited (NLA, groups, firewall) → remove cruft & risky extensions.


PBQ expectations & practice ideas

  • Permissions PBQ: calculate effective access; fix with the smallest change.
  • Malware PBQ: order steps correctly; justify quarantine before cleanup.
  • Recovery PBQ: choose Safe Mode/WinRE/Restore/Reset given symptoms.
  • Logs PBQ: find the relevant error in Event Viewer and pick the next step.

Build tiny labs: a folder tree with varied NTFS/share rights; a throwaway VM to run Safe Mode/Restore/Reset; a mock malware workflow without real malware (use dummy files).


Exam-day tactics

  • First pass fast (~60–70 seconds/item); flag PBQs & long stems for the end.
  • Skim long scenarios, then read the final question to target your reading.
  • Eliminate options that violate least privilege, policy/safety, or order of operations.
  • Preserve a 5–10 minute buffer to revisit flagged items.

  • Syllabus: domain objectives & quick links → Open
  • Cheatsheet: commands, flows, pickers → Open
  • Practice: timed drills, mixed sets, full mocks → Start