A+ Core 2 220-1202 Final Review

Core 2 moves closer to the operating system, the user, and the process around support work. The difficult questions often put several reasonable actions next to each other and ask which one fits the evidence, privilege level, security state, or support procedure now.

If a section below feels new, return to the Core 2 study guide or the matching Quick Review.

1. How to use this final review

For the final pass, ask what each tool, control, or procedure changes.

• Tool questions: what evidence do you need?
• Security questions: are you authenticating, authorizing, hardening, containing, or recovering?
• Troubleshooting questions: what symptom is present, and what changed?
• Operational questions: what needs approval, documentation, backup, safety control, or escalation?
• Remote-support questions: which method fits the system and security requirement?
• AI questions: is the use allowed, accurate enough, and safe for the data involved?

2. Core 2 exam map

Operating Systems and Security together are more than half the exam, but software troubleshooting and operational procedure determine how those technologies are supported in practice.

3. Operating Systems

Choose the Windows tool from the evidence you need

The Core 2 OS Tools Quick Review goes deeper into commands. For final recall, keep these pairings fast:

• ipconfig: Windows IP configuration
• ping: basic ICMP reachability when allowed
• nslookup: DNS response
• tracert: routed hop path
• pathping: path plus loss evidence
• netstat: connections/listening ports
• whoami: current security identity
• sfc: protected Windows system files
• chkdsk: filesystem/disk-related checking
• diskpart: command-line disk/partition work
• gpupdate: refresh Group Policy
• gpresult: report applied Group Policy

Installation and recovery

• Clean install: fresh OS deployment.
• Upgrade: move to a newer supported OS while preserving supported state.
• Image: apply a prepared system image.
• Remote/network install: deliver installation across the network.
• Zero-touch: reduce manual technician interaction.
• Repair/recovery: restore operation without immediately rebuilding everything.
• Multiboot: keep multiple bootable operating systems.

Think about backup, compatibility, drivers, licensing, application requirements, support lifecycle, and rollback before the change.

macOS and Linux

macOS: Finder, Spotlight, Keychain, Time Machine, Disk Utility, FileVault, Force Quit, Terminal, Mission Control, iCloud/Continuity.

Linux: file navigation and management, permissions/ownership, process tools, storage/filesystem tools, package management, networking, configuration files, and sudo for approved elevated work.

Know the job of the command family. Do not assume one Linux distribution's package tool is universal.

4. Security

Authentication, authorization, and privilege

• Authentication verifies identity.
• Authorization/permissions decide what the identity may do.
• Multifactor authentication strengthens authentication using more than one factor category.
• Standard-user operation reduces everyday privilege.
• Controlled elevation is stronger than permanent administrator rights for one approved task.

Wireless and centralized authentication

Keep these roles distinct:

• WPA2/WPA3: wireless-security protocols.
• RADIUS: common centralized network-access authentication/AAA role.
• TACACS+: commonly associated with network-device administration.
• Kerberos: ticket-based authentication in supported domain environments.

Malware sequence

For the current basic SOHO malware-removal procedure:

1. Investigate and verify malware symptoms.
2. Quarantine the infected system.
3. Disable System Restore in Windows Home.
4. Remediate: update anti-malware, scan/remove using the appropriate environment, or reimage/reinstall when trust cannot be restored.
5. Schedule scans and run updates.
6. Enable System Restore and create a clean restore point in Windows Home.
7. Educate the end user.

Containment comes before cleanup when active malware may spread.

Hardening

Useful controls include encryption, strong password policy, screen/session lock, account lockout/expiration where appropriate, disabling unnecessary/default accounts, disabling unnecessary services, current patches, endpoint protection, firmware security, and least privilege.

Mobile controls can add device encryption, MDM, locator, remote lock/wipe, controlled application sources, and current OS/app updates.

Data destruction

Deletion and ordinary formatting are not the same as approved sanitization. Match wipe/erase, physical destruction, or an approved outsourced method to media reuse, policy, sensitivity, and chain-of-custody requirements.

5. Software Troubleshooting

Windows symptom map

Mobile troubleshooting

For mobile app/update/connectivity problems, check storage, network, account/store state, operating-system/app compatibility, permissions, and device-management policy before factory reset.

Suspicious ads, unexpected network use, untrusted application sources, root/jailbreak state, or data leakage are security clues rather than ordinary performance problems.

Narrow safe action first

Reset, reinstall, and factory reset are strong tools, but they are not automatically the best first action when the evidence points to a narrower cause.

6. Operational Procedures

Ticket and documentation

Capture enough information for another technician or future you to understand:

• User/business impact
• Symptoms and relevant evidence
• Actions taken
• Changes made
• Result and verification
• Escalation or follow-up

Do not put secrets or unnecessary sensitive data into a ticket just because the system accepts text.

Change management

A controlled change typically includes scope, risk/impact, approval, scheduling, testing, backup/rollback, implementation, documentation, and review.

An emergency can accelerate the process. It does not eliminate accountability.

Backup and recovery

Keep backup copies, locations, and recovery testing distinct.

The 3-2-1 principle is a useful baseline: three copies of important data, on two media/storage types, with one copy kept off-site or otherwise separated from the primary failure domain.

A backup that has never been tested is an assumption, not proven recovery.

Safety and environment

Know Electrostatic Discharge (ESD) controls, lifting safety, electrical hazards, cable trip hazards, proper component handling, ventilation, dust, temperature/humidity concerns, surge protection, Uninterruptible Power Supply (UPS) use, disposal, and fire-safety context.

Safety can make a technically possible action the wrong answer.

Privacy, policy, licensing, and prohibited activity

Follow Acceptable Use Policy (AUP), Non-Disclosure Agreement (NDA), licensing, retention, privacy, and regulated-data requirements. Preserve evidence and escalate suspected prohibited or illegal activity according to policy rather than investigating beyond your authority.

Professional communication

Set expectations, avoid unnecessary jargon, respect privacy, document delays, confirm the user's understanding, and do not blame the user for the problem.

Scripts and remote support

Recognize script types and the benefits/risks of automation. A script can repeat a mistake quickly, so validate scope, permissions, input, and testing.

Remote-support choices can include Remote Desktop Protocol (RDP), Virtual Network Computing (VNC), Secure Shell (SSH), Remote Monitoring and Management (RMM), SPICE, Windows Remote Management (WinRM), and approved third-party support tools. Use the method appropriate to the target system and security requirements.

Artificial intelligence

The current Core 2 objectives include AI basics. Keep these issues visible:

• Appropriate-use policy
• Accuracy and hallucination risk
• Bias
• Plagiarism and attribution concerns
• Privacy and data-security risk
• Human verification before acting on generated output

Do not paste sensitive organizational or customer information into an AI service unless policy and the service arrangement permit it.

7. Sequences and decision rules

Evidence before repair

Task Manager answers current state. Event Viewer answers logged history. Device Manager answers device/driver state. Choose evidence that distinguishes likely causes before changing several settings.

Contain before malware cleanup

If the infected system can spread harm, quarantine it before normal remediation.

Least privilege before convenience

Do not make a user a permanent administrator because one task needs elevation.

Backup before risky change

When a change could destroy or make data inaccessible, protect recoverability first.

Safety before uptime

A swollen battery, electrical hazard, overheating hardware, or unsafe physical condition changes the priority.

Policy before improvisation

For privacy, security incidents, prohibited activity, licensing, and remote support, follow authorized policy and scope rather than taking an action merely because the tool allows it.

8. Final readiness checklist

You are ready for another Core 2 practice set when you can explain these without relying on recognition alone:

• [ ] Clean install, upgrade, image, remote/network, zero-touch, repair, and multiboot distinctions
• [ ] Task Manager versus Event Viewer versus Device Manager versus Disk Management
• [ ] ipconfig, ping, nslookup, tracert, pathping, netstat, sfc, chkdsk, diskpart, gpupdate, and gpresult by purpose
• [ ] Common macOS support/security tools
• [ ] Common Linux file, permission, process, storage, package, network, and privilege tools
• [ ] Authentication versus authorization versus privilege elevation
• [ ] WPA2/WPA3, RADIUS, TACACS+, Kerberos, and MFA roles at A+ depth
• [ ] Current SOHO malware-removal order
• [ ] Workstation and mobile hardening
• [ ] Data wiping/destruction versus normal deletion/formatting
• [ ] Windows performance, boot, app, browser, certificate, and security symptom clues
• [ ] Mobile app, update, connectivity, and malicious-app troubleshooting
• [ ] Ticketing, asset/knowledge documentation, and SLA context
• [ ] Change scope, approval, test, rollback, implementation, and review
• [ ] 3-2-1 backup principle and recovery testing
• [ ] ESD, electrical, lifting, cable, temperature, ventilation, UPS, and disposal safety
• [ ] Privacy, licensing, AUP, NDA, retention, and evidence-handling limits
• [ ] Professional communication and escalation
• [ ] Scripting benefits and risks
• [ ] RDP, VNC, SSH, RMM, SPICE, WinRM, and approved third-party remote support by purpose
• [ ] AI policy, hallucination, bias, plagiarism, accuracy, privacy, and data-security concerns
• [ ] Why each wrong answer acts at the wrong stage, changes the wrong layer, or grants too much privilege

If several items are still slow, use the matching A+ Quick Reviews before taking another Core 2 practice session.

9. Official references

• CompTIA A+ certification page