220-1202 — CompTIA A+ Core 2 Exam Blueprint

How to Use This Exam Blueprint

Use this checklist as a practical study map for CompTIA A+ Core 2 (220-1202). It is designed to help you decide whether you can apply the topics, not just recognize terms.

Work through each section in three passes:

1. Identify weak areas: Mark anything you cannot explain or perform without notes.
2. Practice scenario decisions: For each tool, setting, or procedure, ask, “When would I use this instead of another option?”
3. Final review: Revisit traps, troubleshooting flows, and command-line tasks before exam day.

This page is independent exam-prep support and should be used alongside the current CompTIA exam objectives for 220-1202.

Topic-Area Readiness Map

Operating System Fundamentals Checklist

Core Platform Concepts

Be able to compare common operating system roles and support tasks.

Windows Interfaces and Configuration Areas

OS Installation, Upgrade, and Recovery Readiness

Installation and Upgrade Decisions

Recovery and Repair Tools

Installation and Configuration Checklist

• I can identify the information to collect before an OS install: user data, apps, license status, drivers, network settings, and special hardware needs.
• I can explain why backups and restore verification matter before destructive changes.
• I can distinguish upgrade, clean install, repair, reset, and restore scenarios.
• I can configure basic user accounts, local groups, passwords, and sign-in options.
• I can recognize when a driver issue is more likely than an application issue.
• I can troubleshoot missing storage, incorrect drive letters, and partition/formatting problems.
• I can explain why system time, region, language, and accessibility settings may matter in support cases.
• I can choose a recovery option based on severity, data risk, and time available.

Command-Line and Utility Readiness

You do not need to memorize every switch for every command, but you should know what the command is for and when it is the best next step.

Windows Command Checklist

Example command-recognition practice:

ipconfig /all        -> Review detailed adapter configuration
ipconfig /release    -> Release DHCP lease
ipconfig /renew      -> Request new DHCP lease
ipconfig /flushdns   -> Clear local DNS resolver cache

Linux and macOS Command Checklist

Permissions Readiness

Be ready to interpret permissions conceptually.

Security Exam Blueprint

Core Security Concepts

Threat and Attack Recognition

Security Controls and Configuration

Malware Response Workflow

Use a consistent sequence. Exam scenarios often test the safest next step, not just the final fix.

    flowchart TD
	    A[Identify symptoms] --> B[Isolate affected system]
	    B --> C[Preserve data and evidence as required]
	    C --> D[Disable persistence points if appropriate]
	    D --> E[Update anti-malware tools]
	    E --> F[Scan and remove/quarantine]
	    F --> G[Remediate damaged settings]
	    G --> H[Update OS, apps, and signatures]
	    H --> I[Change affected credentials]
	    I --> J[Educate user and document]

Checklist:

• I can identify when to disconnect a system from the network.
• I can avoid deleting evidence when escalation or policy requires preservation.
• I can distinguish quarantine, removal, rebuild, and restore.
• I can check startup items, browser extensions, scheduled tasks, services, and unknown processes.
• I can explain why passwords may need to be changed after cleanup.
• I can document symptoms, actions taken, tools used, and user impact.

Software Troubleshooting Readiness

Troubleshooting Method Discipline

Know the general troubleshooting flow and apply it consistently.

Symptom-to-Cause Practice

Software Troubleshooting Checklist

• I can separate user-profile issues from system-wide issues.
• I can test whether a problem follows the user, device, network, or application.
• I can use logs before guessing.
• I can identify when a reboot is useful and when it is only hiding the problem.
• I can explain the difference between repair, reinstall, reset, and rollback.
• I can troubleshoot services that are stopped, disabled, or failing to start.
• I can investigate startup items and scheduled tasks.
• I can recognize symptoms that suggest malware rather than ordinary software failure.
• I can protect user data before destructive troubleshooting.
• I can document the verified fix.

Operational Procedures Checklist

Safety and Professional Practice

Documentation and Change Management

Privacy, Licensing, and Ethics

• I can identify personally identifiable information and sensitive business data.
• I can avoid viewing or copying user data unnecessarily.
• I can follow acceptable-use and data-handling policies.
• I can explain why software licensing compliance matters.
• I can distinguish authorized remote access from unauthorized monitoring.
• I can escalate suspected illegal, unsafe, or policy-violating activity.
• I can maintain chain-of-custody-style documentation when required by policy.
• I can communicate clearly without blaming the user.

Scenario and Decision-Point Checks

Use these prompts to practice exam judgment.

High-Value “Can You Do This?” Checklist

Operating Systems

• Navigate Windows Settings and Control Panel to find network, account, update, privacy, and device settings.
• Use Device Manager to identify driver problems and choose update, rollback, disable, or uninstall.
• Use Event Viewer or logs to support a troubleshooting theory.
• Explain the difference between local, domain/organizational, administrator, and standard user accounts.
• Manage basic file and folder permissions.
• Recognize when the issue is profile-specific versus system-wide.
• Choose a safe recovery option for boot failure or OS corruption.
• Perform basic macOS and Linux navigation and support tasks conceptually.

Security

• Identify phishing, social engineering, malware, ransomware, and browser hijacking indicators.
• Apply least privilege to users, groups, shares, and applications.
• Choose appropriate authentication and MFA controls.
• Secure a mobile device with lock, encryption, updates, and remote wipe concepts.
• Configure or reason about firewall profiles and app access.
• Explain when to quarantine, remove, rebuild, restore, or escalate.
• Protect sensitive data during troubleshooting.
• Recognize insecure user behavior and provide concise education.

Troubleshooting

• Start with symptoms, scope, and recent changes.
• Test one theory at a time.
• Choose the least disruptive fix that is likely to work.
• Verify functionality after the fix.
• Document root cause and resolution.
• Know when to escalate instead of continuing alone.
• Avoid destructive changes until backups and approvals are handled.
• Use commands and logs to confirm, not guess.

Operational Procedures

• Follow ESD and electrical safety practices.
• Document tickets clearly enough that another technician can continue the work.
• Communicate downtime, risk, and next steps to users.
• Follow change management for production-impacting work.
• Handle licensed software and sensitive data properly.
• Dispose of batteries, toner, storage media, and electronics appropriately.
• Maintain professionalism under pressure.
• Respect privacy and authorization boundaries.

Common Weak Areas and Exam Traps

Final-Week Review Plan

Seven to Four Days Out

• Re-read the current CompTIA objectives for CompTIA A+ Core 2 (220-1202) and mark each item green, yellow, or red.
• Build a one-page command table from memory, then check gaps.
• Practice mixed troubleshooting scenarios, not only definition questions.
• Review Windows administrative tools and what each one is best used for.
• Review malware removal order and incident escalation cues.
• Review permissions, local users/groups, and least privilege.
• Review safety, documentation, and change-management steps.

Three to Two Days Out

• Drill weak topics only; do not reread everything passively.
• Explain five scenarios out loud: malware infection, failed update, app crash, permission denial, and browser redirect.
• Practice choosing the “best next step” rather than the most advanced fix.
• Review mobile security and backup/sync concepts.
• Review macOS/Linux basic commands and support areas.
• Review privacy and data-handling expectations.

Day Before

• Stop deep new-topic study.
• Review your personal trap list.
• Review command purposes and administrative tools.
• Review the troubleshooting process and malware workflow.
• Prepare exam logistics, identification, timing, and testing environment requirements.
• Get rest.

Practical Next Step

Pick your lowest-confidence readiness area from this checklist and do focused practice on that topic. For each missed question or lab task, write down:

• the symptom,
• the correct tool or concept,
• why the tempting answer was wrong,
• the safest next step,
• and what you will recognize next time.

That habit turns the 220-1202 topic list into exam-ready judgment for CompTIA A+ Core 2 (220-1202).