What 220-1102 actually tests

The CompTIA A+ Core 2 (220-1102) exam is the part of A+ that proves you can support users, operating systems, security controls, and day-to-day IT operations. If Core 1 is more hardware and infrastructure, Core 2 is where service desk and desktop support work lives.

Expect questions across four domains:

Operating Systems — the biggest chunk
Security
Software Troubleshooting
Operational Procedures

This exam is built for roles like:

Help desk technician
Desktop support specialist
Field service technician
Junior systems support

You will see multiple-choice questions and performance-based questions (PBQs). PBQs usually test whether you can apply procedures, not just recognize terms. That means you need to know things like:

How to configure Windows tools
How to respond to malware symptoms
How to follow change management and incident response
How to troubleshoot boot issues, application crashes, and OS problems

This is not a deep administrator exam. You do not need enterprise architect depth. But you do need broad, practical support knowledge, and CompTIA likes to test whether you can pick the best next step in a realistic support scenario.

Your score comes from Windows, Windows, and more Windows

If you want the shortest path to a pass, start with the Operating Systems domain. It carries the most weight, and it spills into troubleshooting questions too.

Focus first on Windows editions and features. You should know the differences between:

Windows 10 Home, Pro, Pro for Workstations, Enterprise
Basic upgrade paths and feature availability
Local vs Microsoft account use cases
Domain vs workgroup concepts

Then master Windows installation methods:

Clean install vs in-place upgrade
Bootable USB media creation
System requirements awareness
Partitioning basics: MBR vs GPT
File systems: NTFS, exFAT, FAT32

CompTIA also expects you to know the everyday admin tools. Not vaguely. Specifically. You should be comfortable identifying the purpose of:

Task Manager
Device Manager
Disk Management
Microsoft Management Console (MMC)
Services
System Configuration (msconfig)
Event Viewer
Performance Monitor
Resource Monitor
Registry Editor
System Information (msinfo32)
Command Prompt and PowerShell

Memorize the common command-line tools that repeatedly show up in A+ prep:

ipconfig
ping
tracert
netstat
nslookup
hostname
gpupdate
gpresult
sfc
chkdsk
diskpart
robocopy
shutdown
net use
net user

Do not just memorize names. Know what problem each tool helps solve.

For example:

sfc /scannow checks protected system files.
chkdsk targets file system and disk issues.
gpupdate /force refreshes Group Policy.
net use maps network drives.
diskpart is used for advanced disk management tasks.

You also need a working understanding of Windows networking and sharing settings:

Workgroup/domain basics
Shared folders and permissions at a high level
Printer sharing
Remote assistance and remote desktop concepts
Firewall profiles: domain, private, public

Know the Windows recovery environment and startup options. These matter both in OS and troubleshooting questions:

Safe Mode
System Restore
Startup Repair
Recovery partitions
Reset this PC
Command prompt in recovery tools

CompTIA still expects awareness of macOS, Linux, and mobile OS basics, but not at the same depth as Windows. Learn:

macOS tools like Finder, Dock, Mission Control, Spotlight, Time Machine
Linux basics such as file locations, permissions, and commands like ls, pwd, cd, cp, mv, grep, chmod, ps, sudo
Mobile OS features for Android and iOS/iPadOS, especially security, synchronization, network settings, and troubleshooting basics

A practical warning: many candidates underprepare on Windows versions, tool purposes, and recovery utilities because the material looks familiar. That is a mistake. Familiarity is not recall under exam pressure.

Security on Core 2: less theory, more technician decisions

The Security domain on 220-1102 is not a pure cybersecurity exam. CompTIA wants to know whether you can apply security controls as a technician supporting endpoints and users.

Start with physical and logical security basics:

Physical locks, badge readers, biometric devices, privacy screens, cable locks
Least privilege
User permissions
Account policies
Authentication methods
MFA

You need to know common security threats and what they look like in support situations:

Phishing and spear phishing
Malware: ransomware, trojans, rootkits, spyware, keyloggers
Social engineering: impersonation, tailgating, shoulder surfing
Brute force and credential attacks
Spoofing and suspicious wireless behavior

This exam often asks for the best remediation step. That means you should know the right order of operations when malware is suspected:

Identify symptoms
Quarantine or isolate the system
Disable System Restore if needed by procedure
Remediate using antimalware tools
Schedule scans and updates
Re-enable protections and restore settings
Educate the user

You should also be solid on wireless and network security basics:

WPA2 vs WPA3
Strong passphrases
Avoiding open and insecure networks
VPN purpose and use
Default credential removal
Firmware and OS patching

For workstation hardening, know how these show up in real support:

Windows Defender / Microsoft Defender features
Firewall configuration
BitLocker basics
FileVault basics on macOS
Screen locks and timeout policies
Patching and updates
Browser security settings
Application permissions

Be ready for SOHO security too. CompTIA likes practical home-office scenarios:

Change default admin credentials on routers
Update firmware
Use strong encryption
Disable unnecessary services
Set guest networks when appropriate
Place devices correctly and secure access physically

You also need to understand data disposal and handling:

Shredding, degaussing, wiping, drive destruction
Secure handling of PII and sensitive company data
Proper disposal procedures for storage media and paper records

One area people rush through is password policy and access control. Don’t. You should be able to spot the best control for a given situation:

Need better login security? MFA
Need to protect data at rest on a laptop? BitLocker/FileVault
Need to reduce unauthorized software installation? Least privilege
Need to stop walk-up viewing in public? Privacy screen and lock policies

That is the style of thinking the exam rewards.

Troubleshooting software the way the exam expects

The Software Troubleshooting domain is where CompTIA tests whether you can separate symptoms from causes. This domain is smaller than OS and Security, but it overlaps heavily with both.

For Windows troubleshooting, know the common symptoms and likely fixes for:

Boot failures
Slow performance
Application crashes
Blue screens / stop errors
Missing DLL or service issues
Print spooler problems
No network connectivity caused by software settings
Profile corruption
Failed updates

You should be able to choose among tools such as:

Task Manager for startup impact and process review
Event Viewer for logs
System Restore after a bad driver or update
Device Manager for driver issues
Safe Mode for isolation
Recovery tools for startup failures
Uninstall/reinstall for broken apps
Repair install / reset options when damage is broader

Malware troubleshooting deserves its own drill set. Expect symptoms like:

Pop-ups
Browser redirects
Unauthorized toolbars
Slow performance
Fake alerts
Disabled security tools
Encrypted files in ransomware scenarios

Know the likely response, not just the label.

CompTIA also expects cross-platform troubleshooting awareness:

On mobile devices, review:

App crashes and forced restarts
Battery drain causes
No connectivity due to airplane mode, bad Wi-Fi settings, or mobile data settings
OS update failures
Storage saturation
Screen lock and biometric issues
Malware or rogue apps on mobile platforms

On macOS and Linux, you do not need admin-level depth, but you should know basic troubleshooting paths:

Reboot and safe/recovery options where applicable
Permission issues
Application compatibility problems
Disk space and resource exhaustion
Service/process review

CompTIA loves the troubleshooting methodology. Learn it exactly and use it mentally on every scenario:

Identify the problem
Establish a theory of probable cause
Test the theory
Establish a plan of action and implement the solution
Verify full system functionality and implement preventive measures
Document findings, actions, and outcomes

That last step matters. On this exam, technical skill and process discipline are both tested.

Operational procedures: the domain people disrespect and then miss questions on

The Operational Procedures domain looks easy because the topics feel familiar. In practice, this section costs people points because CompTIA asks about the most correct professional action, not merely what works technically.

Start with professional communication:

Use clear, non-technical language with users when appropriate
Avoid judgmental wording
Set expectations on timelines and next steps
Document actions and outcomes
Know when to escalate

Expect scenario questions involving difficult users, VIPs, or remote support. The right answer usually balances:

Professionalism
Security
Documentation
Least business disruption

You also need to know change management and incident procedures at a technician level:

Submit change requests where required
Identify risk and rollback plans
Get approvals before significant changes
Communicate outages and maintenance windows
Document exactly what changed

For backup and recovery, know the practical distinctions:

Full, incremental, differential backups
Restore testing
Retention awareness
Local vs cloud backup concepts
Business impact of poor backup practices

Safety and environmental topics are classic A+ material and still fair game:

ESD precautions
MSDS/SDS awareness
Proper disposal of batteries and toner
Lifting safety
Electrical safety
Working around trip hazards and hot components

Remote support and ticketing are also central here. Know the logic of:

Creating and updating tickets clearly
Recording symptoms, environment, user impact, and actions taken
Using remote tools securely
Verifying user identity before account actions
Closing loops with users after resolution

CompTIA may also test scripting basics in an operational context. You do not need to become a developer, but you should recognize common script types and use cases:

PowerShell
Batch files
Shell scripts
Basic automation for repetitive tasks

Finally, cloud and virtualization awareness appears in Core 2 at a support level. Make sure you understand:

What a virtual machine is
Why snapshots are useful
Basic SaaS examples like Microsoft 365 or Google Workspace
Sync issues, account issues, and access issues in cloud-backed apps

If a question sounds like “What should the technician do first?” in a workplace scenario, this domain is probably in play.

A study order that matches the exam, not wishful thinking

Here is the order I recommend for 220-1102 because it matches both the weighting and the way topics overlap:

Operating Systems
Software Troubleshooting
Security
Operational Procedures
Final mixed review with PBQs and weak-topic drilling

Why this order works:

Operating Systems gives you the base language of the exam.
Software Troubleshooting makes more sense once you know the OS tools.
Security becomes easier when you already understand Windows features, users, permissions, and recovery tools.
Operational Procedures is best studied after technical content because many questions are judgment calls built on a technical scenario.

A realistic timeline depends on your background.

If you are new to IT: plan 8 to 10 weeks

Weeks 1-3: Windows editions, installation, tools, file systems, command line, recovery
Weeks 4-5: Software troubleshooting, malware symptoms, mobile OS basics, macOS/Linux basics
Weeks 6-7: Security controls, access management, encryption, wireless security, SOHO hardening
Week 8: Operational procedures, documentation, change management, backup concepts
Weeks 9-10: Practice exams, PBQs, targeted review

If you already work in help desk or desktop support: plan 4 to 6 weeks

Week 1: Exam objectives review and OS gap analysis
Week 2: Windows tools and troubleshooting drills
Week 3: Security and malware remediation sequence
Week 4: Operational procedures and mixed practice
Weeks 5-6: Full review, PBQs, weak-area correction

If you recently passed Core 1 and your endpoint support skills are current: plan 3 to 4 weeks

Week 1: Operating Systems intensive review
Week 2: Security + software troubleshooting
Week 3: Operational procedures + practice exams
Week 4: Final cleanup and PBQs

Use the 689 practice questions on Truekia as reinforcement, not as your primary teacher. Practice questions are best for:

Finding weak objectives fast
Learning CompTIA wording patterns
Building speed
Exposing false confidence

They are not enough by themselves unless you already do this work every day.

Resources worth your time for Core 2

Use a short resource stack and go deep. Too many candidates collect resources and never finish any.

Official starting point

CompTIA A+ 220-1102 Exam Objectives — this is non-negotiable. Print it or keep it open while studying. Every topic you study should map back to an objective.
CompTIA CertMaster Learn / CertMaster Practice — useful if you like vendor-aligned coverage and structured quizzes.

Books

CompTIA A+ Certification All-in-One Exam Guide, Exam 220-1101 & 220-1102 by Mike Meyers
CompTIA A+ Complete Study Guide: Exams 220-1101 and 220-1102 by Quentin Docter and Jon Buhagiar

Mike Meyers is strong for approachable explanations. Docter/Buhagiar tends to align well with exam-style breadth.

Video courses

Professor Messer’s CompTIA A+ 220-1102 video course — free and tightly objective-focused
Jason Dion’s A+ Core 2 course and practice exams on Udemy — useful for exam-style review and testing discipline
Mike Meyers’ Total Seminars A+ course — good if you want a more conversational teaching style

Hands-on labs you can build yourself

You do not need expensive enterprise gear. Build a simple lab with:

A Windows 10 or 11 PC or VM
A second VM if possible
A Linux VM such as Ubuntu
A phone or tablet for mobile settings review

Practice these tasks repeatedly:

Create and manage local users
Change NTFS permissions in a test folder
Use msconfig, Task Manager, Event Viewer, Services, Device Manager
Run sfc, chkdsk, ipconfig, ping, netstat, gpupdate
Enable/disable startup items
Create restore points and use recovery options
Turn firewall rules on/off in a lab
Configure BitLocker if hardware supports it, or at least study the workflow
Install and remove software cleanly
Break a VM on purpose, then recover it

Documentation and reference material

Microsoft Learn for Windows administration basics, recovery options, Defender, BitLocker, and command-line tools
Apple Support documentation for macOS and iOS settings, security, and backup basics
Ubuntu Documentation or official Linux command references for basic shell commands and permissions

Practice testing

Use practice exams in stages:

First pass: open-book, objective-linked
Second pass: timed and closed-book
Final pass: review only missed and guessed questions

Do not memorize answer letters. Write down why the right answer is right and why the distractors are wrong.

How to use practice questions without fooling yourself

For comptia-220-1102, practice questions are valuable only if you use them diagnostically.

A good review loop looks like this:

Take a 25- to 50-question set by domain
Mark every guessed question as incorrect, even if you guessed right
Map misses back to the official objective list
Re-study the exact tool, term, or workflow you missed
Do a smaller retest on that same objective

Use the 689 Truekia questions in three phases:

Phase 1: Domain checks — after finishing each domain
Phase 2: Mixed sets — once all content is covered
Phase 3: Final exam simulation — timed, no notes, full focus

Watch for these false-confidence traps:

Recognizing terms without knowing when to use them
Memorizing malware names without knowing remediation order
Knowing Windows tool names without knowing what each one actually does
Scoring well on repeated questions because you remember wording, not content

If your scores are strong but you still hesitate on PBQs or scenario questions, your issue is usually application, not recall. Go back to the lab.

Exam-day tactics for CompTIA’s style of questioning

CompTIA questions often include extra detail that is there to distract you. Read for the actual problem, not the story.

A few exam-day rules help a lot:

Skip PBQs first if they slow you down. Come back after the multiple-choice questions.
Watch for words like first, best, most secure, least disruptive, and next. Those words decide the answer.
If two answers are both technically possible, choose the one that matches process, security, and documentation best.
Eliminate answers that are too advanced, too destructive, or unrealistic for a support technician.

For PBQs, expect tasks around:

Matching security controls to scenarios
Troubleshooting boot or malware symptoms
Using support logic for ticketing or procedures
Identifying the right Windows tools or settings

Manage your time aggressively. Do not spend several minutes wrestling with one item early.

Last 48 hours before the exam, review:

Windows administrative tools
Command-line utilities and use cases
Malware removal steps
Security controls and authentication concepts
Troubleshooting methodology
Change management, backup types, and documentation practices

On the day itself, bring a calm, procedural mindset. This exam rewards technicians who think in order:

identify
isolate
remediate
verify
document

That is the Core 2 mindset. If your study reflects that, you will be ready.