A+ (Core 2) (220-1102)

Domain 1: Operating Systems — 31%

Operating Systems is the largest Core 2 domain, so you need more than surface-level familiarity with menus and settings.

You’ll need to understand Windows editions, installation methods, file systems, command-line tools, administrative utilities, upgrade paths, recovery options, and common configuration tasks. You should also know the basics of macOS, Linux, ChromeOS, Android, and iOS. Focus on what each tool is designed to do and when it should be used. The exam often presents several utilities that look plausible, but only one fits the required scope, permissions, or recovery stage. Practice following a user’s goal from configuration through diagnosis, repair, and validation.

Domain 2: Security — 25%

Security in Core 2 covers endpoint protection, user access, data handling, wireless safeguards, physical security, and incident response.

You’ll need to understand authentication, authorization, multifactor methods, permissions, least privilege, encryption, password policies, firewalls, malware prevention, secure disposal, and account management. Don’t treat every security problem as a malware issue. Social engineering, stolen devices, weak configuration, excessive permissions, and poor physical controls require different responses. Match each threat to the control that directly reduces the risk. Study both prevention and recovery, including quarantine, backups, evidence preservation, and post-incident actions. The best answer usually protects the system without unnecessarily disrupting legitimate business activity.

Domain 3: Software Troubleshooting — 22%

Software troubleshooting is about isolating the failed layer before making broad or destructive changes.

You’ll encounter slow systems, application crashes, boot failures, browser problems, malware symptoms, mobile issues, and operating-system errors. Start by documenting the symptom, checking recent changes, narrowing the scope, and testing one theory at a time. A pop-up may suggest adware, while an untrusted certificate can point to time settings, trust configuration, or interception. High resource usage may be caused by startup applications, limited memory, storage problems, malware, or a failing process. Use logs, safe mode, task-management tools, repair utilities, and known-good configurations before jumping to a full reset or reinstallation.

Domain 4: Operational Procedures — 22%

Operational Procedures is where technical skill meets safe, professional, and repeatable support.

You’ll need to understand documentation, ticket handling, change control, backups, disaster recovery, safety, privacy, licensing, scripting basics, remote support, and professional communication. Study electrostatic discharge precautions, hazardous-material handling, power safety, equipment disposal, and acceptable-use requirements. A technically correct fix can still be the wrong answer if it violates policy, skips approval, risks data loss, or leaves no usable record. Good technicians protect people, preserve evidence, communicate clearly, and document what changed. The goal isn’t just to solve today’s problem. It’s to prevent the same issue from becoming harder to diagnose tomorrow.