Quick Review purpose
This independent Quick Review is for candidates preparing for the real CompTIA A+ Core 2 (220-1202) exam from CompTIA. Use it to refresh the most testable ideas before moving into topic drills, mock exams, and detailed explanations in an IT Mastery question bank.
Core 2 is largely about working safely and professionally with operating systems, users, security settings, software problems, endpoint protection, and support procedures. The exam often rewards practical judgment: choosing the next best step, identifying the most likely cause, and applying a standard troubleshooting or security process without overcorrecting.
Use CompTIA’s current exam objectives as your scope authority. This page is IT Mastery practice support, not an official CompTIA resource.
High-yield Core 2 map
| Area | What to review quickly | What questions often test |
|---|
| Operating systems | Windows features, installation methods, recovery tools, file systems, command-line utilities, macOS/Linux basics | Best tool for a task, correct installation/recovery choice, command output interpretation |
| Security | Authentication, permissions, malware response, endpoint hardening, wireless security, social engineering, data handling | Least privilege, order of response, secure configuration, recognizing attack types |
| Software troubleshooting | Boot issues, OS errors, application crashes, update failures, browser symptoms, mobile OS issues | Most likely cause, next troubleshooting step, safe remediation |
| Operational procedures | Documentation, change management, safety, professionalism, backups, scripting risks, environmental controls | Technician behavior, escalation, rollback planning, evidence preservation |
Exam-day thinking pattern
When a question gives a scenario, slow down and identify what it is really asking:
- Symptom — What is broken or risky?
- Scope — One user, one device, many users, one application, entire network?
- Recent change — Update, driver, policy, installation, permission change, malware event?
- Impact — Data loss risk, security incident, safety issue, business outage?
- Best next step — Verify, contain, document, escalate, remediate, or test?
A common mistake is jumping to a dramatic fix—reimage, replace hardware, reinstall OS—before checking simpler or safer causes such as credentials, permissions, network settings, services, updates, or user profile issues.
Core troubleshooting method
Use the standard troubleshooting flow whenever the question asks for the “next” or “best” action.
| Step | What it means | Candidate trap |
|---|
| Identify the problem | Gather symptoms, question the user, determine changes, duplicate issue if possible | Fixing before understanding scope |
| Establish a theory | Start with probable cause; consider simple causes first | Choosing rare causes without evidence |
| Test the theory | Confirm or rule out the cause | Making irreversible changes as a “test” |
| Establish a plan | Decide remediation and consider effects | No rollback plan or user impact check |
| Implement solution | Apply the fix or escalate | Escalating too late or too early |
| Verify functionality | Confirm the issue is resolved and preventive steps work | Stopping after the first successful reboot |
| Document findings | Record cause, action, outcome, and future prevention | Treating documentation as optional |
Scope decision rules
| If the issue affects… | Think first about… |
|---|
| One user on one device | Profile, local settings, permissions, app config, cached credentials |
| One device for all users | OS corruption, local service, driver, hardware, firewall, disk, malware |
| Many users on one application | Application service, update, certificate, authentication, server-side change |
| Many users on the network | DNS, DHCP, routing, firewall, identity provider, shared service outage |
| Only remote users | VPN, MFA, conditional access, endpoint compliance, split tunnel, DNS |
| Only after an update | Driver rollback, update history, compatibility, known issue, restore point |
Operating systems: must-know review
Windows editions and feature awareness
Know which features are associated with business-oriented Windows environments. Questions may ask why a feature is unavailable or which edition/configuration is appropriate.
| Feature/category | Review point |
|---|
| Domain or enterprise management | Business editions are commonly used where centralized identity and policy management are needed |
| BitLocker-style disk encryption | Commonly associated with protecting data at rest; know recovery-key implications |
| Remote Desktop host capability | Do not confuse being able to connect outward with accepting inbound remote desktop sessions |
| Group Policy | Centralized configuration in managed environments; local policy affects one machine |
| Update controls | Enterprise environments may use staged updates, maintenance windows, and rollback planning |
Installation and deployment choices
| Method | Use when… | Watch for… |
|---|
| Clean installation | Starting fresh, replacing corrupted OS, repurposing device | Data wipe risk; backup first |
| Upgrade installation | Keeping apps/data while moving to a newer supported OS | Compatibility checks matter |
| Repair/in-place repair | OS components are damaged but user environment should be preserved | Not a substitute for backup |
| Image deployment | Standardizing many machines | Drivers, licensing, naming, domain identity, post-deployment updates |
| Recovery/reset | Returning a malfunctioning system to working state | Understand keep-files vs remove-everything style choices |
| Network/PXE deployment | Deploying over the network | Requires network boot support and deployment infrastructure |
File systems and storage concepts
| File system/concept | High-yield point |
|---|
| NTFS | Windows permissions, encryption/compression features, large file support |
| FAT32 | Broad compatibility but file size and feature limitations |
| exFAT | Useful for removable media and cross-platform exchange |
| ext family | Common in Linux environments |
| APFS | Modern macOS file system |
| Partition | Logical division of a physical disk |
| MBR vs GPT | Partitioning schemes; GPT is common on modern UEFI systems |
| Basic vs dynamic-style storage | Know that advanced volume features add complexity and recovery considerations |
Boot and recovery decision table
| Symptom | Consider first | Useful tools/actions |
|---|
| Windows fails after driver update | Bad driver or update | Safe Mode, rollback driver, uninstall update, System Restore/recovery tools |
| Repeated startup repair loop | Boot files, disk, update failure, corruption | Startup Repair, command-line repair, disk diagnostics, restore/reset |
| Blue screen after new hardware | Driver, firmware, incompatible hardware | Remove device, update/rollback driver, check vendor support |
| Slow boot | Startup apps, services, disk health, malware, updates | Task Manager startup tab, Services, Event Viewer, disk checks |
| User cannot sign in | Password, account lockout, profile corruption, domain connectivity | Verify credentials, network, account status, local admin recovery path |
| “Operating system not found” | Boot order, missing bootloader, failed disk | BIOS/UEFI boot order, recovery media, disk diagnostics |
Know the right tool for the task. Many exam questions are essentially tool-selection questions.
| Tool | Best use | Common trap |
|---|
| Task Manager | Processes, performance, startup apps, quick service view | Using it for deep historical logs |
| Event Viewer | System/application/security logs and error patterns | Ignoring timestamps and event source |
| Device Manager | Drivers, disabled devices, hardware conflicts | Reinstalling OS for a driver issue |
| Disk Management | Partitions, volumes, drive letters | Confusing it with file-level permissions |
| Services | Start/stop/configure services | Disabling services without dependency review |
| System Configuration | Startup and boot troubleshooting | Permanent changes without documenting |
| Performance Monitor | Counters and long-term performance analysis | Using it when Task Manager is enough |
| Resource Monitor | Real-time CPU, disk, network, memory detail | Overlooking disk queue or network activity |
| Reliability Monitor | Timeline of crashes, updates, and failures | Forgetting it is useful after “it started yesterday” |
| Registry Editor | Low-level OS/application configuration | Editing without backup or exact instruction |
| Local Users and Groups | Local account/group management | Not available in all environments/editions |
| Local Security Policy | Local password/audit/security settings | Confusing local policy with domain policy |
| Group Policy tools | Managed policy application and troubleshooting | Assuming local settings override domain policy |
| Windows Defender Firewall | Host firewall rules and profiles | Opening broad inbound access unnecessarily |
| Windows Security tools | Antivirus, threat protection, device security | Disabling protection instead of adding controlled exclusions |
| Windows Update | Patch status and update history | Ignoring rollback/uninstall options |
| Backup and recovery tools | Restore files/system state | Backups are useful only if restore works |
Command-line quick review
Memorize what each command is for, not just its name.
| Command | Use | Exam trap |
|---|
ipconfig | View IP configuration; release/renew DHCP; flush DNS cache | DNS cache flush does not fix a bad gateway |
ping | Basic connectivity and name-resolution check | ICMP may be blocked; failure is not always outage |
tracert | Path to destination and where routing may fail | It does not prove application-layer availability |
nslookup | DNS query testing | If DNS works, the app can still fail for other reasons |
netstat | Active connections and listening ports | Requires interpretation; many connections may be normal |
net user | View/create/manage local users from CLI | Local account commands do not manage cloud/domain identities |
net use | Map network drives/resources | Drive mapping failure may be permissions or DNS |
gpupdate | Refresh Group Policy | Policy may not apply if scope/filtering is wrong |
gpresult | Show applied policies | Better for policy troubleshooting than guessing |
chkdsk | File system/disk checks | Not a backup; can take time and may require reboot |
sfc | Verify/repair protected Windows system files | Not designed to fix third-party applications |
DISM | Repair Windows image/component store | Often used before or with SFC in corruption scenarios |
shutdown | Shutdown/restart/logoff from CLI | Useful for remote or scripted administration |
robocopy | Robust file copy/sync | Wrong switches can mirror deletion; test carefully |
xcopy | Legacy extended copy | Know it, but robocopy is often stronger |
diskpart | Disk/partition management | Dangerous if wrong disk is selected |
format | Prepare a volume with a file system | Destroys existing data on target volume |
Linux and macOS command awareness
| Command/tool | Platform | High-yield use |
|---|
ls, cd, pwd | Linux/macOS | Navigate and list files |
cat, less, tail | Linux/macOS | View files/logs |
grep | Linux/macOS | Search text/output |
chmod | Linux/macOS | Change permissions |
chown | Linux/macOS | Change ownership |
ps, top | Linux/macOS | View processes/resource usage |
kill | Linux/macOS | Stop a process |
sudo | Linux/macOS | Run command with elevated privileges |
ifconfig / ip | Linux/macOS/Linux | Network configuration review |
man | Linux/macOS | Command documentation |
apt, dnf, yum | Linux | Package management, depending on distribution |
| Disk Utility | macOS | Disk formatting/repair |
| Activity Monitor | macOS | Process and performance review |
| Keychain Access | macOS | Credentials/certificates |
| Time Machine | macOS | Backup and restore |
Permissions and access control
Core permission principles
| Principle | Meaning | Exam application |
|---|
| Least privilege | Give only the access required | Avoid making users local admins for convenience |
| Need to know | Access should match job role and data sensitivity | Restrict confidential files by group/role |
| Separation of duties | Split sensitive tasks across roles | One person should not control all critical steps |
| Role-based access | Assign rights through groups/roles | Manage groups, not one-off user exceptions |
| Explicit deny | Deny can override allow in many permission models | Use carefully; it can block intended access |
| Inheritance | Permissions flow from parent containers | Check inherited permissions before adding new ones |
NTFS and share permission traps
| Situation | Rule of thumb |
|---|
| Local access to files | NTFS permissions apply |
| Network access to shared folder | Both share and NTFS permissions matter |
| Share allows Full Control, NTFS allows Read | Effective network access is limited by NTFS |
| Share allows Read, NTFS allows Modify | Effective network access is limited by share permission |
| User belongs to multiple groups | Combined allows generally accumulate, but denies can override |
| User suddenly loses access | Check group membership, inheritance, explicit deny, moved folder, token refresh/sign-out |
Candidate mistake: selecting “reinstall the application” when the actual issue is that the user cannot write to a folder, access a share, or inherit the right group membership.
Security quick review
Authentication and account security
| Control | What it protects against | Review point |
|---|
| MFA | Password-only compromise | Stronger when factors are truly different |
| Password manager | Weak/reused passwords | Protect the vault with strong MFA |
| Account lockout | Brute-force attempts | Too strict can cause denial-of-service issues |
| Biometrics | Credential sharing and convenience issues | Usually paired with device or PIN |
| Smart card/security key | Phishing-resistant authentication in some setups | Requires enrollment and recovery process |
| Single sign-on | Reduces password prompts | A compromised primary identity has broad impact |
| Local admin restriction | Malware and accidental system changes | Use standard accounts for daily work |
| Screen lock | Unauthorized local access | Short timeout for shared/public areas |
Endpoint hardening
| Control | Why it matters |
|---|
| Patch OS and applications | Reduces known vulnerabilities |
| Enable host firewall | Limits unsolicited inbound access |
| Use antivirus/EDR protections | Detects and blocks malware behavior |
| Disable unused services | Reduces attack surface |
| Remove unnecessary apps | Fewer vulnerabilities and conflicts |
| Encrypt storage | Protects data if device is lost or stolen |
| Use secure boot/firmware protections | Helps protect startup integrity |
| Configure automatic lock | Reduces walk-up access risk |
| Use standard user accounts | Limits damage from user mistakes and malware |
Wireless and network security
| Topic | High-yield point |
|---|
| WPA2/WPA3 | Prefer modern encryption over obsolete wireless security |
| WPS | Convenient but often discouraged in secure setups |
| Guest network | Isolates visitors from internal resources |
| Strong passphrase | Prevents easy unauthorized access |
| MAC filtering | Weak as a primary security control |
| SSID hiding | Not real security by itself |
| Captive portal | Common in public/guest environments |
| VPN | Protects traffic over untrusted networks and supports remote access |
| DNS filtering | Helps block known malicious domains |
| Firewall profiles | Public networks should be more restrictive than private/domain profiles |
Social engineering recognition
| Attack | Recognition cue |
|---|
| Phishing | Deceptive message asking for credentials/action |
| Spear phishing | Targeted phishing using personal or business context |
| Whaling | Targets executives or high-value users |
| Vishing | Voice-based social engineering |
| Smishing | SMS/text phishing |
| Impersonation | Pretending to be support, vendor, executive, courier |
| Shoulder surfing | Observing screens/keystrokes |
| Tailgating | Following an authorized person into a restricted area |
| Dumpster diving | Searching discarded materials |
| Evil twin | Rogue wireless network posing as legitimate |
| On-path attack | Intercepting/modifying communications between parties |
Data handling and disposal
| Scenario | Best practice |
|---|
| Sensitive file no longer needed | Secure deletion according to policy |
| Disk repurposed internally | Wipe or reimage according to data classification |
| Disk leaving organization | Sanitize, destroy, or follow approved chain-of-custody process |
| Lost encrypted laptop | Verify encryption status and report through incident process |
| Shared printer output | Retrieve promptly; use secure print where appropriate |
| Emailing sensitive data | Use approved encryption and recipients only |
| Ticket notes | Do not expose unnecessary secrets or personal data |
Malware and incident response
Malware types to distinguish
| Type | Core behavior |
|---|
| Virus | Attaches to files/programs and spreads through execution |
| Worm | Self-propagates across systems/networks |
| Trojan | Disguises itself as legitimate software |
| Ransomware | Encrypts or blocks access and demands payment |
| Spyware | Collects information without consent |
| Keylogger | Captures keystrokes |
| Rootkit | Hides privileged malicious activity |
| Botnet agent | Enrolls device into remote-controlled network |
| Cryptominer | Uses system resources to mine cryptocurrency |
| Adware/PUP | Displays ads or unwanted behavior; may be bundled |
Malware response sequence
A practical endpoint malware-removal sequence is:
- Identify symptoms — pop-ups, redirects, disabled security tools, high CPU, unknown processes, file encryption, suspicious network traffic.
- Isolate or quarantine — disconnect from network if needed to prevent spread or data loss.
- Preserve what matters — if it may be an incident, follow policy before wiping evidence.
- Disable persistence where applicable — startup entries, scheduled tasks, malicious services, browser extensions.
- Update tools and scan — use trusted antimalware and offline scanning if appropriate.
- Remediate — remove malware, repair settings, patch exploited software, reset affected credentials.
- Verify — rescan, confirm symptoms are gone, check logs and network behavior.
- Restore protections — firewall, antivirus, updates, restore/recovery features where applicable.
- Educate user and document — record cause, impact, actions, and prevention.
Common trap: immediately deleting or reimaging a system that may require evidence preservation, management approval, or incident escalation.
Software troubleshooting review
Windows symptom table
| Symptom | Likely areas to check | Better first action than reinstalling |
|---|
| App crashes on launch | Updates, dependencies, permissions, profile corruption, event logs | Check Event Viewer/Reliability Monitor |
| App works for admin only | File/registry permissions, elevation requirement | Adjust permissions or app configuration |
| Slow system | Startup apps, disk health, memory pressure, malware, updates | Use Task Manager/Resource Monitor |
| BSOD | Driver, hardware, memory, update, firmware | Check stop information, recent changes, drivers |
| Windows update fails | Disk space, services, network/proxy, corrupted update cache | Review update history and logs; retry after clearing issue |
| Printer unavailable | Spooler, driver, queue, network path, default printer | Check queue/spooler/connectivity |
| No sound | Output device, mute, driver, service, app setting | Verify selected output and driver |
| Cannot access share | DNS, credentials, permissions, offline server, firewall | Test path, credentials, effective permissions |
| Time/date wrong | Time service, time zone, CMOS/firmware, domain sync | Correct sync source and time zone |
| Certificate warning | Wrong date/time, expired cert, interception, wrong hostname | Do not bypass without validation |
Browser troubleshooting
| Symptom | Possible cause |
|---|
| Pop-ups/redirects | Malicious extension, adware, notification permission, DNS issue |
| Certificate errors | Date/time wrong, expired certificate, captive portal, inspection proxy |
| One site fails | DNS cache, browser cache, site issue, security block |
| All sites fail | Network, proxy, DNS, firewall, VPN |
| Slow browser only | Extensions, cache, profile, hardware acceleration |
| Saved passwords missing | Profile sync issue, browser profile, password manager problem |
Quick checks: private/incognito window, alternate browser, disable extensions, clear cache for the affected site, verify proxy/VPN, check DNS, review security warnings.
Mobile OS and app troubleshooting
| Symptom | Review actions |
|---|
| App crashes | Update app/OS, clear cache where supported, reinstall app, check permissions |
| Battery drains quickly | Review battery usage, background activity, radios, location, failing battery |
| Device overheats | Heavy app, charging issue, environment, battery problem |
| Cannot email/sync | Credentials, MFA, server settings, network, account lock, storage |
| Location not working | Permissions, location services, airplane mode, app settings |
| No network | Airplane mode, Wi-Fi/cellular settings, SIM/eSIM, carrier issue, VPN |
| Storage full | Remove unused apps/media, clear cache, cloud sync settings |
| Suspicious behavior | Remove unknown apps/profiles, scan where supported, update OS, reset if needed |
Trap: assuming every mobile issue is hardware. App permissions, account authentication, and OS updates are frequent causes.
Security troubleshooting scenarios
| Scenario | Best first thinking |
|---|
| User reports suspicious email | Do not click links; report/quarantine according to policy |
| Workstation shows ransomware note | Isolate immediately; escalate; preserve evidence; follow incident plan |
| User cannot access encrypted drive | Recovery key, TPM/firmware change, account permissions |
| Browser redirects to unknown search page | Extension/adware/DNS settings; scan and reset browser settings |
| Repeated account lockouts | Mapped drives, saved credentials, mobile email, brute-force attempt |
| Unknown admin account appears | Treat as security incident; investigate and escalate |
| Antivirus disabled | Check policy, tampering, malware, service status |
| Public Wi-Fi use | VPN, firewall public profile, avoid sensitive activity without protection |
Backups and recovery
Backup types
| Type | What it does | Restore implication |
|---|
| Full | Copies all selected data | Simplest restore, more storage/time |
| Incremental | Copies changes since last backup of any type | Restore needs last full plus each incremental |
| Differential | Copies changes since last full backup | Restore needs last full plus latest differential |
| Image | Captures system state/disk image | Useful for bare-metal or standardized recovery |
| File-level | Captures selected files/folders | Good for user data restore |
| Cloud backup/sync | Stores data off-device | Sync is not always the same as versioned backup |
Backup decision rules
- Test restores. A backup is only useful if restoration works.
- Keep offline or immutable copies where ransomware risk matters.
- Match recovery method to the problem: deleted file, corrupted profile, failed disk, or compromised system require different recovery choices.
- Protect backup credentials. Backup systems are high-value targets.
- Document retention according to organizational policy.
Operational procedures
Change management
| Step | Why it matters |
|---|
| Define the change | Prevents unclear or expanding work |
| Identify risk and impact | Avoids surprise outages |
| Get approval | Ensures accountability |
| Schedule maintenance window | Reduces user disruption |
| Communicate | Sets expectations |
| Back up and create rollback plan | Allows recovery if change fails |
| Implement and test | Confirms intended result |
| Document outcome | Supports future troubleshooting |
Trap: making an urgent fix without documenting what changed. In later troubleshooting questions, the undocumented change is often the hidden cause.
Ticketing and documentation
Good ticket notes usually include:
- User/device/application affected
- Symptoms and error messages
- Time started and recent changes
- Scope and business impact
- Troubleshooting steps already tried
- Root cause if known
- Fix applied
- Verification performed
- User communication and follow-up
- Escalation details if applicable
Avoid recording passwords, unnecessary personal data, or unapproved sensitive details in tickets.
Professional communication
| Situation | Strong technician behavior |
|---|
| User is frustrated | Listen, acknowledge, ask focused questions |
| User caused the issue | Avoid blame; educate respectfully |
| You need more time | Set expectations and provide updates |
| Issue is outside your authority | Escalate with clear notes |
| You do not know the answer | Say you will research or escalate; do not guess |
| Working around sensitive data | Maintain privacy and follow policy |
| Remote support session | Get permission before taking control or viewing files |
Safety and environmental procedures
| Topic | Review point |
|---|
| ESD | Use antistatic handling, grounding, proper bags/mats |
| Electrical safety | Disconnect power where appropriate; avoid unsafe equipment |
| Batteries | Handle swollen/damaged batteries carefully; follow disposal rules |
| Lifting | Use proper lifting technique and assistance for heavy equipment |
| Cables | Avoid trip hazards and blocked airflow |
| Toner/chemicals | Follow safety documentation and disposal practices |
| Fire suppression | Use the correct class/type for the environment |
| Ventilation | Prevent overheating and exposure to fumes |
| Personal protective equipment | Match PPE to task and workplace policy |
Scripting and automation basics
The CompTIA A+ Core 2 (220-1202) candidate does not need to be a software engineer, but should understand what scripts do and why they can be risky.
| Concept | Review point |
|---|
| Variables | Store values such as paths, usernames, or counters |
| Environment variables | System/user values like paths and temp locations |
| Conditionals | Run different actions based on true/false tests |
| Loops | Repeat actions; dangerous if logic is wrong |
| Comments | Explain script purpose and assumptions |
| Exit codes | Indicate success/failure for automation |
| Input validation | Prevents bad data from causing damage |
| Permissions | Scripts run with the privileges of the executing context |
| Testing | Run in a safe environment before production |
| Signing/execution policy | Helps control unauthorized scripts |
File extensions to recognize
| Extension | Typical association |
|---|
.bat / .cmd | Windows batch scripts |
.ps1 | PowerShell |
.sh | Shell script |
.py | Python |
.js | JavaScript |
.vbs | VBScript |
Script trap: a script that deletes, moves, formats, changes permissions, or modifies many accounts should be treated as high risk. Review it, test it, back up first, and confirm the target path or scope.
Common candidate traps
“Best next step” traps
- Choosing a final fix before confirming the problem.
- Reimaging before checking logs, drivers, updates, or user profile issues.
- Escalating without collecting basic information.
- Continuing troubleshooting after discovering a security incident that must be isolated/escalated.
- Making a change without rollback or documentation.
- Bypassing certificate or security warnings for convenience.
- Giving admin rights instead of fixing the specific permission problem.
- Assuming wireless signal strength means authentication, DHCP, DNS, and internet access all work.
- Confusing backup, sync, restore point, and full system image.
- Treating user education as optional after malware or phishing events.
| If asked to… | Prefer… | Not usually… |
|---|
| Find why an app crashed yesterday | Reliability Monitor/Event Viewer | Randomly reinstalling drivers |
| See current CPU/memory hogs | Task Manager/Resource Monitor | Registry Editor |
| Troubleshoot policy application | gpresult, gpupdate, policy tools | Changing local settings blindly |
| Check DNS resolution | nslookup, ipconfig /displaydns | Replacing the NIC |
| Repair Windows system files | sfc, DISM | Formatting the disk first |
| Manage partitions | Disk Management/diskpart | File Explorer permissions |
| Investigate malware symptoms | Security tools, isolation, logs | Ignoring network spread risk |
Practice priorities before a mock exam
Use original practice questions to test whether you can apply concepts under exam-style wording. Do not only memorize tables.
Topic drills to run first
| Drill area | What to prove |
|---|
| Windows tools | Choose the correct utility for a scenario |
| Commands | Match command to symptom and interpret basic purpose |
| Permissions | Calculate effective access and identify least-privilege fix |
| Malware response | Put containment, remediation, verification, and education in order |
| Boot troubleshooting | Select Safe Mode, recovery, rollback, repair, or reset appropriately |
| Browser/mobile issues | Identify app, permission, network, certificate, or malware causes |
| Operational procedures | Apply documentation, change control, safety, and professionalism |
| Security hardening | Choose practical endpoint, account, and wireless controls |
How to review explanations
When using a question bank with detailed explanations, review every missed question this way:
- Why was the correct answer best?
- Which clue in the scenario pointed to it?
- Why were the distractors tempting but wrong?
- Was the issue scope, sequence, tool choice, or terminology?
- What similar scenario could appear with a different symptom?
Final rapid checklist
Before your next CompTIA A+ Core 2 (220-1202) practice exam, confirm you can:
- Select the correct Windows administrative tool for a troubleshooting task.
- Distinguish clean install, upgrade, repair, reset, image, and recovery options.
- Use common Windows commands for network, policy, disk, file, and system repair tasks.
- Recognize Linux/macOS commands and support tools at a practical level.
- Apply least privilege, MFA, encryption, firewall, patching, and account-hardening concepts.
- Troubleshoot NTFS/share permission scenarios.
- Identify malware types and follow a safe response sequence.
- Diagnose common application, browser, boot, update, and mobile OS symptoms.
- Choose safe backup and restore approaches.
- Apply change management, documentation, safety, privacy, and professional communication.
- Recognize scripting benefits and risks.
Next step
Use this Quick Review as a checklist, then move directly into IT Mastery practice: start with short topic drills on your weakest Core 2 areas, review the detailed explanations, and then take a timed mixed question bank set before attempting a full mock exam.
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.