CompTIA A+ Core 2 220-1202 is the current V15 exam covering operating systems, security, software troubleshooting, and operational procedures. Candidates must pass both Core 1 220-1201 and Core 2 220-1202 to earn the A+ certification. The current Core 2 exam allows a maximum of 90 multiple-choice and performance-based questions in 90 minutes, recommends about 12 months of hands-on IT support experience, and requires a passing score of 700 on the 100\u2013900 scale.<\/p>\n
The current 220-1202<\/a> blueprint has four domains: Operating Systems at 28%, Security at 28%, Software Troubleshooting at 23%, and Operational Procedures at 21%. The weighting is unusually balanced, which means candidates cannot treat security or operating systems as the \u201cmain\u201d topic and neglect professional support practices.<\/p>\n The first domain covers Windows, Linux, macOS, Chrome OS, iOS\/iPadOS, and Android at the level an IT support specialist needs. It also includes filesystems such as NTFS, ReFS, FAT32, ext4, XFS, APFS, and exFAT, along with end-of-life\/update limitations and compatibility concerns.<\/p>\n The objective is not deep administration of every platform. It is recognizing what each operating system supports, where common settings live, and how platform differences affect installation, applications, networking, security, and troubleshooting.<\/p>\n The blueprint includes USB\/network\/flash\/internet installation methods, clean installs, upgrades, imaging, zero-touch, recovery and repair installs, GPT\/MBR, driver\/application compatibility, Windows edition differences, TPM\/UEFI, and upgrade paths.<\/p>\n Windows administrative tools include Task Manager, Event Viewer, Disk Management, Task Scheduler, Device Manager, Certificate Manager, Local Users and Groups, Performance Monitor, Group Policy Editor, System Information, Resource Monitor, System Configuration, Disk Cleanup, Defragment, and Registry Editor.<\/p>\n Windows commands include navigation, networking, disk, file, user, policy, system integrity, and informational tools such as ipconfig, ping, netstat, nslookup, tracert, pathping, chkdsk, diskpart, robocopy, whoami, gpupdate, gpresult, and sfc.<\/p>\n Linux objectives include ls, pwd, mv, cp, rm, chmod, chown, grep, find, fsck, mount, sudo, apt\/dnf, ip, curl, dig, traceroute, top, ps, df\/du, common configuration files, systemd, kernel and bootloader. A Linux command-line foundation<\/a> is useful as long as it stays at support depth.<\/p>\n Core 2 includes macOS application packages, system folders, Apple ID restrictions, updates\/patches, Rapid Security Response, Time Machine, Keychain, Spotlight, iCloud, FileVault, Terminal and Force Quit. It also includes installing\/configuring cloud email, storage\/synchronization, collaboration tools, identity synchronization and licensing.<\/p>\n This reflects the modern help-desk reality: technicians support devices and services across several operating-system ecosystems.<\/p>\n The security domain begins with physical and logical controls: locks, surveillance, badges, biometrics, least privilege, Zero Trust, ACLs, MFA, SAML, SSO, just-in-time access, PAM, MDM, DLP, IAM and directory services.<\/p>\n A general cybersecurity foundation<\/a> helps because Core 2 expects technicians to implement basic protection and recognize when an issue should be escalated.<\/p>\n Candidates should know Defender Antivirus, Windows Firewall, local\/Microsoft accounts, user roles, Windows Hello, NTFS\/share permissions, UAC, BitLocker\/BitLocker To Go, EFS, Active Directory basics, Group Policy and folder redirection.<\/p>\n Wireless security includes WPA2\/WPA3, TKIP\/AES, RADIUS, TACACS+, Kerberos and multifactor authentication. The role is support-oriented: configure secure settings and troubleshoot access without needing enterprise security-architecture depth.<\/p>\n Malware types include Trojans, rootkits, viruses, spyware, ransomware, keyloggers, boot-sector viruses, cryptominers, stalkerware, fileless malware, adware and PUPs. Detection\/removal tools include EDR, MDR, XDR, antivirus, anti-malware, email security gateways, firewalls, user education and OS reinstallation.<\/p>\n Social engineering\/threat objectives include phishing variants, shoulder surfing, tailgating, impersonation, dumpster diving, DoS\/DDoS, evil twin, zero-day, spoofing, on-path, brute force, insider threat, SQL injection, XSS, BEC, supply-chain attacks, unpatched\/EOL systems and BYOD exposure.<\/p>\n Windows symptoms include blue screens, degraded performance, boot problems, shutdowns, failing services, crashing applications, low memory, instability, missing OS and time drift. Mobile issues include application failures, update\/install problems, battery life, reboots, connectivity and screen rotation.<\/p>\n The domain also covers security-related symptoms such as fake alerts, malicious apps, pop-ups, browser redirection, certificate warnings, altered files and unusual network activity.<\/p>\n This domain covers ticketing, asset management\/CMDB, procurement\/warranty\/licensing, SOPs, onboarding\/offboarding, SLAs, knowledge bases, change management, backup\/recovery, safety, environmental controls, privacy\/licensing\/policy, professionalism, scripting, remote access, and basic AI concepts.<\/p>\n The current A+ 1200-series update<\/a> reflects this broader role: the technician is expected to resolve technical issues while documenting, communicating, protecting data, following process and using modern automation\/AI responsibly.<\/p>\n The domains connect around one ticket: understand the platform, secure it, diagnose the symptom, communicate with the customer, follow change or incident procedure, apply the fix, verify recovery, document the outcome, and escalate when the issue exceeds support scope.<\/p>\n The Windows portion also includes client networking because operating-system support does not stop at the desktop. Candidates should know domain versus workgroup behavior, shared files\/printers, mapped drives, IP configuration, DNS, gateway, static versus dynamic addressing, VPN, wired\/wireless\/cellular connections, proxies, public versus private network profiles, and metered-connection limitations.<\/p>\n Windows 10 and Windows 11 remain in scope according to CompTIA’s current note, provided the Windows versions are still within Microsoft’s mainstream-support intent for the job role. Candidates should focus on common administration and security features instead of memorizing differences that are irrelevant to practical support.<\/p>\n Application installation objectives connect hardware, OS and business requirements. A package can fail because of 32\/64-bit compatibility, GPU\/VRAM, CPU\/RAM\/storage requirements, unsupported OS version, driver dependency, network impact or business policy. Technicians should validate requirements before blaming the installer.<\/p>\n Cloud productivity support includes licensing and identity synchronization because \u201cthe app is installed\u201d does not mean the user can work. Email, storage, collaboration, videoconferencing, spreadsheets and messaging may depend on account entitlement, synchronized identity, network access and correct client configuration.<\/p>\n Physical security appears in Core 2 because technicians often work in offices, data rooms, retail or field environments where device theft and unauthorized access are real risks. Badges, locks, surveillance, guards, lighting, fencing and secure equipment placement protect systems before logical controls are even involved.<\/p>\n Zero Trust, least privilege, MFA, SSO, SAML, JIT\/PAM, IAM and directory services are presented at a support level. The technician should understand why users should receive only necessary access, how identity can be verified, and where to look when legitimate access fails. Deep identity-architecture design belongs to later certifications.<\/p>\n Windows permissions are a common source of confusion. NTFS permissions and share permissions can both affect access to a network file, while inheritance, user\/group membership and UAC influence what a user can do locally. Good troubleshooting identifies the effective permission path before granting broader rights.<\/p>\n The malware-removal objective is unusually procedural. CompTIA expects candidates to investigate symptoms, quarantine the system, perform remediation, update protection, scan with appropriate techniques, reimage\/reinstall when necessary, restore protection settings, and educate the user afterward. This reflects real support discipline rather than one-command cleanup.<\/p>\n Workstation hardening includes data-at-rest encryption, password practices, firmware passwords, screen locks, protected PII, password managers, account restrictions, disabling unnecessary services, and reducing default administrative exposure. A password-manager<\/a> discussion fits here because credential practices are one layer of endpoint hardening.<\/p>\n Mobile-device security extends many of the same principles to phones and tablets: encryption, screen locks, OS\/app updates, endpoint security, locator tools, remote wipe, backups, MDM, failed-login restrictions and corporate-versus-BYOD policy. Ownership matters because support authority and privacy differ between personal and corporate devices.<\/p>\n Data destruction and disposal objectives remind candidates that deleting a file is not always enough. Erasing\/wiping, formatting, degaussing, drilling, shredding, incineration, third-party destruction certificates, recycling and regulatory\/environmental requirements all depend on media type, sensitivity and organizational policy.<\/p>\n SOHO security and browser security are practical extensions of basic networking. Router passwords, firmware, content filtering, guest access, secure management, port forwarding, SSID\/encryption settings, safe browser extensions, certificate validation, private browsing, cache\/data clearing, secure DNS and proxy settings can all affect user security without enterprise infrastructure.<\/p>\n Software Troubleshooting is deliberately symptom-oriented. CompTIA can describe \u201cfrequent shutdowns,\u201d \u201cno OS found,\u201d \u201cslow profile load,\u201d \u201capplication fails to update,\u201d \u201chigh network traffic,\u201d or \u201cbrowser redirection\u201d and expect the candidate to infer the most likely layer and next action. Studying only tool names leaves this domain weak.<\/p>\n Operational Procedures also tests backup methods in a support context: full, incremental, differential and synthetic full; recovery to the original or alternate location; backup testing; onsite\/offsite rotation; GFS; and the 3-2-1 rule. The important support habit is verifying that data can actually be restored, not merely confirming a scheduled job completed.<\/p>\n Change management includes purpose, scope, type, timing, freeze\/maintenance windows, impact, risk analysis, approvals, implementation, peer review and user acceptance. This matters because even a technically correct fix can cause an outage if introduced without backup, rollback or coordination.<\/p>\n Operational safety and environmental controls are also current objectives: ESD, grounding, power disconnection, component handling, cable management, batteries\/toner disposal, temperature\/humidity, ventilation, dust, UPS, surge suppression and response to brownouts\/blackouts. Technicians need to protect people, equipment and the environment while resolving the ticket.<\/p>\n Core 2 now explicitly includes basic AI concepts in Operational Procedures. Candidates should understand application integration, appropriate-use policy, plagiarism concerns, public versus private AI, data-source\/privacy\/security issues, and limitations such as bias, hallucinations and accuracy. The objective is responsible support use, not model engineering.<\/p>\n Professional communication remains testable because support outcomes depend on trust. Active listening, avoiding unnecessary jargon, cultural sensitivity, expectation setting, difficult-customer handling, confidentiality, status updates, repair options and follow-up are operational skills, not soft extras.<\/p>\n For final scope review, treat the current 220-1201\/220-1202 generation<\/a> as a complete entry-level support role. Core 1 emphasizes hardware\/networking and Core 2 emphasizes OS\/security\/process, but the same technician is expected to connect them during performance-based and scenario questions.<\/p>\nOperating Systems is 28% and spans several platforms<\/h3>\n
Windows deployment and tooling remain a major Core 2 foundation<\/h3>\n
Command-line fluency is practical rather than developer-level<\/h3>\n
macOS and cloud productivity are part of the same support role<\/h3>\n
Security is another 28%<\/h3>\n
Windows and wireless security are explicit hands-on objectives<\/h3>\n
Malware and social engineering are central support risks<\/h3>\n
Software Troubleshooting is 23%<\/h3>\n
Operational Procedures makes up the final 21%<\/h3>\n
Core 2 is ultimately a support workflow exam<\/h3>\n