CompTIA A+ 220-1101 Vs. 220-1102 Exam Domains: A Complete Comparison Guide

Missing a printer on a help desk ticket is one thing. Mixing up the CompTIA A+ exam domains and studying the wrong material is how people waste weeks.

This certification comparison breaks down the current CompTIA A+ exams, 220-1101 and 220-1102, so you can study with a clear plan instead of guessing. If you are trying to understand the certification differences, the split between hardware and software topics, and how the two exams map to real IT support work, this guide is for you.

The A+ certifications remain a common starting point for entry-level IT roles because they validate practical skills that matter on the job: device setup, troubleshooting, operating systems, security awareness, and support procedures. CompTIA explains the exam structure and objectives on its official site, and the exam split is intentional: it lets the certification cover a broad help desk skill set without turning one test into an impossible grab bag of topics. For the official blueprint, start with CompTIA A+ and the current exam objectives from CompTIA Exam Objectives.

This article also connects the domain split to the way technicians actually work. The goal is not just to memorize a list of topics. The goal is to understand why 220-1101 leans toward devices, connectivity, and cloud basics, while 220-1102 leans toward operating systems, security, software support, and operational procedures. That framing helps with exam prep strategies and with the real job.

Overview Of The CompTIA A+ Certification Structure

CompTIA A+ is split into two required exams because foundational IT support is too broad to validate in a single test without losing depth. One exam covers the physical and connectivity side of support, while the other covers the software, security, and process side. This structure mirrors entry-level IT work, where a technician may spend the morning replacing RAM, the afternoon resetting a Windows profile, and the end of the day handling a phishing report.

Both exams must be passed to earn the credential. Each test uses a mix of multiple-choice and performance-based questions, which is important because the exam is not only checking whether you know a term. It is also checking whether you can apply that knowledge in a realistic support workflow. CompTIA’s official certification pages and objectives make the format and domains clear, and that matters when you build a study plan. See CompTIA A+ and the exam objectives at CompTIA Exam Objectives.

Why Two Exams Instead Of One

The split lets CompTIA balance hardware, networking, mobile devices, cloud concepts, operating systems, security, software troubleshooting, and professional support behavior. If everything were packed into one exam, the test would either become too shallow or too long. Instead, each exam gets a distinct focus, which makes study planning more efficient.

This is where domain weighting matters. If one exam gives more weight to hardware or operating systems, your preparation time should reflect that. Not every topic deserves the same amount of study time. A candidate who spends all week on low-weight topics and ignores the highest-weight areas is building a weak plan, even if the notes look complete.

What The Exam Format Means In Practice

The presence of performance-based questions changes how you should prepare. You may need to identify a cable issue, recognize a Windows command, or choose the correct troubleshooting step from a simulated scenario. That means memorization alone is not enough.

• Multiple-choice questions test recognition, terminology, and basic judgment.
• Performance-based questions test whether you can do the task or sequence the steps correctly.
• Scenario questions test whether you can pick the right support response for the situation.

That combination is why exam prep strategies should include reading objectives, practicing labs, and working through ticket-style scenarios. ITU Online IT Training’s CompTIA A+ Certification 220-1201 & 220-1202 Training aligns well with that style of preparation because the course content tracks the core support tasks new technicians actually face.

CompTIA A+ is not a trivia exam. If you cannot explain how a fix works in a real support environment, you are not ready for the performance-based questions.

CompTIA A+ 220-1101 Domain Focus

220-1101 centers on the physical and connectivity side of IT support. That includes hardware, networking, mobile devices, virtualization, cloud computing, and troubleshooting. In practical terms, this is the exam that asks whether you can get a device online, identify a bad cable, choose the right port, or understand where a cloud service fits into a user’s workflow.

For many candidates, 220-1101 feels more concrete because the questions often tie to visible equipment and real-world setup tasks. If a user’s laptop will not connect to Wi-Fi, the problem may be a driver, an access point issue, the wrong band, or a physical adapter problem. If a printer will not print, you may need to identify a port, confirm connectivity, or check the device queue. These are the kinds of scenarios the exam is built around.

The U.S. Bureau of Labor Statistics notes that help desk and support roles continue to be a common entry point into IT careers, which is one reason device support and connectivity remain central skills. For labor market context, see the BLS Occupational Outlook Handbook.

How 220-1101 Reflects First-Line Support Work

Technicians in field support and help desk roles spend a lot of time on first-response issues. That means identifying whether a problem is a user error, a hardware failure, a cabling fault, or a simple misconfiguration. The exam reflects that workflow by testing physical components and basic diagnostics more than policy or governance.

• Setting up a laptop dock and external monitor
• Replacing faulty RAM or storage
• Checking a wireless adapter after a failed connection
• Verifying a printer’s network status
• Explaining hotspot use on a mobile device

That practical emphasis makes 220-1101 a strong fit for candidates who learn best by doing. If you can explain the part, the port, the cable, and the symptom, you are already thinking in the right direction.

Hardware Domains In 220-1101

Hardware is the foundation of 220-1101. You need to know what major components do, how they connect, and what happens when they fail. That includes CPUs, motherboards, memory, storage, power supplies, expansion cards, and peripheral devices. You are not being asked to design a server platform. You are being asked to recognize what belongs where and how to troubleshoot common issues.

For example, if a desktop fails to boot after a RAM upgrade, you need to think about compatibility, seating, supported memory types, BIOS/UEFI settings, and whether the power supply is adequate. If a laptop shows artifacts on an external monitor but not on the internal display, the problem may point toward the GPU, the cable, or the adapter chain. These are typical support patterns.

Official hardware and port references from vendors are worth reviewing directly. Cisco’s networking and interface documentation is useful for physical port recognition, and Microsoft’s support pages help reinforce device and peripheral behavior. For standards and support basics, see Cisco and Microsoft Learn.

Core Hardware Topics You Must Know

• CPU types, sockets, and cooling basics
• Motherboards, chipsets, and BIOS/UEFI configuration
• Memory types, capacity limits, and installation order
• Storage options such as SATA drives, SSDs, and NVMe
• Power supplies, wattage needs, and connector types
• Expansion cards like network and graphics adapters
• Peripherals including printers, monitors, and docking stations

Know the common cables and connectors too. USB, HDMI, DisplayPort, Ethernet, SATA data, SATA power, and power connectors appear all the time in troubleshooting questions. The exam often tests whether you can match the correct connector to the device or identify why an installation will not work.

Hardware Troubleshooting Patterns

Hardware questions usually follow a symptom-first structure. You may get a scenario like “the system powers on but does not display anything,” then you have to work through likely causes. Start with the simplest checks: power, seating, cable integrity, and device compatibility. Then move to component substitution if the situation warrants it.

1. Check power and obvious physical damage.
2. Verify cables, adapters, and seating.
3. Test with a known-good component.
4. Review compatibility and firmware settings.
5. Replace the faulty part if needed.

Anti-static precautions also matter. Proper handling, ESD awareness, and compatible parts are not optional in real support environments. They are part of what makes a technician reliable.

Networking Domains In 220-1101

Networking is another major part of 220-1101, but the focus is practical rather than deeply theoretical. You need to understand IP addressing, DNS, DHCP, Wi-Fi standards, and common topologies well enough to diagnose user issues. This is the exam domain that often feels like “why can’t this device get online?”

CompTIA’s objectives focus on the common home and small-office equipment technicians see every day: routers, switches, access points, and modems. That matters because many entry-level support problems are really connectivity problems disguised as something else. A user may complain that email is down when the actual issue is DNS resolution or a bad wireless signal.

For technical grounding, vendor docs and standards references help. Cisco’s networking materials and IETF RFCs for core protocols are useful when you want a clearer understanding of how traffic actually moves. A good starting point is Cisco and the protocol references at IETF.

What Networking Skills The Exam Expects

• IP addressing and subnet awareness at a basic level
• DNS as name resolution, not just “internet access”
• DHCP for automatic addressing
• Wi-Fi bands, channels, and signal interference
• Topology recognition such as star and mesh
• Device roles for routers, switches, APs, and modems

It also helps to know troubleshooting tools such as ping, ipconfig, and tracert. If a device has a 169.254.x.x address, you should immediately think about DHCP failure or link problems. If a website fails by name but works by IP, DNS should move to the top of the list.

Wired Versus Wireless Troubleshooting

Wired issues usually come down to cabling, ports, NICs, and switch-side problems. Wireless issues can involve signal strength, channel overlap, SSID selection, security mismatch, or outdated drivers. The exam may ask you to choose the most likely cause based on symptoms, so you need to think carefully and not jump too quickly.

Issue	Likely Focus
No link light on Ethernet	Cable, port, NIC, or switch problem
Wi-Fi connects but internet is slow	Interference, band choice, signal strength, or congestion

This is where real troubleshooting discipline matters. Do not assume “Wi-Fi problem” means one thing. Compare the symptom, the environment, and the connection path before choosing an answer.

Mobile Devices And Portability Topics In 220-1101

Mobile support is part of 220-1101 because technicians are expected to support laptops, tablets, smartphones, and wearable devices. That includes batteries, chargers, display assemblies, touchscreens, accessories, and basic syncing behavior. The exam is not asking you to become a mobile device engineer. It is asking whether you can support everyday portable equipment in a workplace environment.

This is especially relevant for hybrid work. Users move between office, home, and travel environments, which means battery wear, docking issues, Bluetooth problems, and hotspot questions are common. Support teams often get tickets about charging failures, devices that overheat, or phones that will not sync calendars and contacts properly.

For mobile operating system support and device guidance, official vendor documentation is the best place to verify behavior. Microsoft Learn and Apple support pages are useful for device administration basics, while Android support resources help with wireless and account sync issues. For broad support concepts, start with Microsoft Learn.

Common Mobile Topics On The Exam

• Laptop hardware such as batteries, docks, and replacement parts
• Tablet and smartphone setup and accessory support
• Bluetooth pairing and basic connectivity
• Hotspot usage for alternate internet access
• Display and touch issues including digitizers and screens
• Data transfer and sync considerations

A common support scenario is a user whose laptop will charge only at a certain angle. That could point to a damaged port, a bad adapter, or a failing cable. Another common one is a phone that charges slowly because of a weak charger or a noncompliant cable. These are the kinds of practical details that show up in exam questions.

Mobile Troubleshooting Priorities

Start with power, then move to connectivity. Check the charger, cable, port, battery health, and OS settings before assuming a deeper hardware fault. For Bluetooth and hotspot issues, verify pairing, permission settings, and compatibility. The best answers usually follow the simplest logical path first.

Virtualization And Cloud Computing In 220-1101

Virtualization and cloud computing appear in 220-1101 because modern support teams work in environments where users rely on hosted services and virtual desktops. The exam only expects practical recognition. You should know what a virtual machine is, what a cloud service is, and when each is being used.

A local virtual machine runs on a host system with software like a hypervisor. A cloud service runs in a provider-managed environment and is accessed over the network. That distinction matters because support issues look different. A local VM problem may involve host resources, while a cloud service issue may point to access, permissions, or provider availability.

For cloud fundamentals, the official AWS and Microsoft documentation are strong references. Use AWS and Microsoft Learn to reinforce service-model definitions and supported use cases.

Cloud Service Models You Need To Recognize

• SaaS for software delivered over the internet
• PaaS for application development platforms
• IaaS for virtualized compute, storage, and networking resources

Hosted email, online file storage, and virtual desktops are common examples. If a user accesses the same files from multiple locations, that is often a cloud workflow. If the application is installed locally but depends on a cloud backend, you may be dealing with a hybrid model.

These topics matter because support technicians increasingly handle devices that are only one part of the user’s workflow. The real service may live in the cloud, even if the problem starts on the endpoint.

Troubleshooting Emphasis In 220-1101

Troubleshooting is woven through the entire 220-1101 exam. You are not just asked what a component is. You are asked what to do when that component fails. That is why the CompTIA troubleshooting methodology is worth memorizing and applying the same way every time.

The standard approach is simple: identify the problem, establish a theory, test the theory, plan and implement the fix, verify full functionality, and document the results. That sequence keeps you from jumping to conclusions. It also keeps you aligned with how real support teams work under ticketing systems and service expectations.

The official CompTIA objectives reinforce this mindset. For more context, review the CompTIA A+ certification page and the current objectives on CompTIA Exam Objectives.

Common Failure Categories On The Exam

• No power or intermittent power
• No display or distorted display output
• Limited connectivity on wired or wireless networks
• Peripheral failure such as printers and docks
• Basic device setup problems involving drivers or ports

The trick is to avoid overcomplicating the issue. If a laptop will not boot after a battery replacement, start with the battery seating, power adapter, and DC jack before assuming motherboard failure. If a printer shows offline, confirm power, cable, network status, and queue settings before replacing hardware.

Good troubleshooting is a sequence, not a guess. The exam rewards candidates who think methodically and eliminate likely causes in order.

CompTIA A+ 220-1102 Domain Focus

220-1102 shifts away from the hardware-heavy focus of 220-1101 and concentrates on operating systems, security, software troubleshooting, and operational procedures. This is the exam that reflects the software and support side of IT administration. It asks whether you can maintain systems, secure endpoints, and work cleanly inside support processes.

Many candidates find 220-1102 more process-oriented because the questions often involve policy, remediation, permissions, or user support workflow. You are not just picking a device part. You are deciding how to handle a malware alert, a failed login, a permissions issue, or a backup concern. That is a different kind of thinking, but it is just as important to real IT support work.

For broader security and workforce context, the NIST guidance on basic cybersecurity practices and the CISA security resources are useful references. They reinforce the habits that appear in support roles every day.

Why 220-1102 Completes The A+ Skill Set

220-1101 proves you can support physical devices and connectivity. 220-1102 proves you can support software, secure user environments, and work according to procedure. Together, they create a balanced foundation for help desk, desktop support, and junior systems roles.

If you only study hardware, you will be weak in user account management and security. If you only study software, you will struggle when a user’s issue is actually a bad cable or dead storage drive. The certification difference is not just topic choice; it is the type of support judgment you are being asked to demonstrate.

Operating Systems Domains In 220-1102

Operating systems are a major part of 220-1102, especially Windows. You should know installation concepts, utilities, command-line tools, account management, and system configuration at a support level. The exam also expects you to recognize basic Linux and macOS support tasks, even if Windows dominates the detail.

Common Windows support areas include Safe Mode, restore points, updates, boot options, task management, and built-in troubleshooting utilities. You are expected to understand how to recover from boot failures, profile issues, and application compatibility problems. A technician who can work through these basics saves time and reduces escalation.

Microsoft’s official documentation is the best source for Windows support behavior. Use Microsoft Learn Windows documentation to verify commands, recovery options, and administrative features.

What You Should Know For OS Support

• Windows installation and recovery concepts
• Command-line tools and common administrative tasks
• File systems and folder structures
• User accounts and permission basics
• System utilities for monitoring and recovery
• Boot and startup troubleshooting steps

Typical scenarios include a profile that will not load, an application that crashes after an update, or a system that boots to a black screen. The right answer usually depends on whether the issue is tied to a user profile, a startup service, a driver, or a system file problem.

Linux And macOS Recognition

You do not need deep administration skills in Linux or macOS for this exam, but you do need to recognize basic support actions and interoperability issues. That includes file access differences, permissions basics, and knowing that different platforms use different utilities and recovery methods.

If a user shares files between platforms, you should understand that format compatibility, network shares, and account permissions can all affect access. This is simple on the surface, but it comes up often in mixed-device workplaces.

Security Domains In 220-1102

Security is one of the biggest distinctions in 220-1102 and often the section candidates worry about most. The exam covers malware, phishing, social engineering, physical security controls, authentication methods, encryption basics, least privilege, access control, and endpoint protection. That is a wide range, but the core idea is simple: can you protect a workstation and recognize when something is wrong?

For authoritative guidance, the NIST Cybersecurity Framework and the CISA cyber threat resources are practical references. They reinforce the same habits CompTIA expects: basic hardening, awareness of threats, and proper escalation.

Security Topics That Appear Often

• Malware types such as viruses, ransomware, and spyware
• Phishing and social engineering signs
• Authentication methods and MFA basics
• Least privilege and access control principles
• Endpoint protection and firewall basics
• Patching and update hygiene

Technicians are often the first people to notice suspicious behavior: a browser redirect, a ransom note, unusual pop-ups, or a user reporting that files disappeared. The exam expects you to choose basic remediation steps, such as disconnecting a machine from the network, scanning for malware, or escalating appropriately.

Software Troubleshooting In 220-1102

Software troubleshooting on 220-1102 is about diagnosing application, OS, driver, and user-profile issues without overreacting. Symptoms can include crashes, slow performance, startup errors, login failures, or missing functionality after a patch. The right response depends on whether the problem is local, user-specific, or system-wide.

This domain is where support mindset matters. Hardware troubleshooting asks, “What part failed?” Software troubleshooting asks, “What changed?” That might be a recent update, a bad driver, a permission issue, or a corrupted profile. The question is often less about replacing something and more about restoring normal behavior.

For vendor-backed diagnostic details, Microsoft Learn is useful for Windows behavior and utilities. Where applicable, official OS documentation is better than a generic checklist because it tells you how the platform is supposed to behave.

Common Software Trouble Spots

• Application crashes after updates or launch
• Slow performance due to startup items or resource limits
• Startup errors linked to boot configuration or drivers
• Login failures from password, profile, or permission issues
• Compatibility problems with older software
• Update failures and rollback requirements

Software support often begins with isolation: test with another user, another profile, or another machine. If the issue disappears, you have narrowed the cause. If it follows the user, profile or permission issues rise to the top. If it follows the machine, look at the OS or installed software stack.

How Software Troubleshooting Differs From Hardware Troubleshooting

Software Support	Hardware Support
Focuses on configuration, permissions, updates, and compatibility	Focuses on parts, connections, power, and physical failures

That difference matters because the wrong mindset leads to wasted time. A technician who starts replacing parts for a permissions issue is guessing. A technician who assumes a software issue when the drive is failing is also guessing. The exam checks whether you can tell the difference.

Operational Procedures In 220-1102

Operational procedures are the professional habits that keep IT support organized, secure, and repeatable. This domain includes documentation, change management, ticketing, communication, safety, disposal procedures, incident reporting, backup strategy, disaster recovery concepts, and data handling. It is the section that proves you can work in a team and follow policy.

These questions are often scenario-based because they test judgment. If a user reports a possible breach, you should know when to escalate. If equipment is being retired, you should know disposal and data sanitization rules. If a fix affects production systems, you should understand change control and documentation expectations.

For broader procedural and governance references, useful sources include NIST and ISACA. NIST supports cybersecurity and recovery concepts; ISACA provides governance and control perspectives that match real workplace procedure.

What Procedures The Exam May Test

• Ticketing and documentation habits
• Communication and customer service
• Escalation when issues exceed your authority
• Change management and approval workflow
• Backup and recovery basics
• Physical safety and environmental handling

Professionalism is not a soft skill in this exam. It is a technical skill. If a technician documents poorly, skips escalation, or mishandles data, the result can be a bigger outage or a compliance problem.

Operational procedure is what separates a technician from a technician who can be trusted with production systems.

Key Differences Between 220-1101 And 220-1102 Domains

The cleanest way to understand the certification differences is to compare the dominant focus of each exam. 220-1101 is about devices, connectivity, and physical support. 220-1102 is about operating systems, security, software, and procedures. Both include troubleshooting, but the context changes.

This matters because the job tasks are different. 220-1101 aligns more closely with field support, hands-on device setup, and first-line hardware or network troubleshooting. 220-1102 aligns more with desktop support, account issues, endpoint security, and workflow discipline. Together, they show broad entry-level competency.

220-1101	220-1102
Hardware, networking, mobile, cloud, and troubleshooting	Operating systems, security, software, and procedures

How The Exams Differ In Cognitive Demand

220-1101 often rewards recognition of components, ports, standards, and practical cause-and-effect. You need to know what a part does and how it fits into a device. 220-1102 requires more process thinking. You need to decide what changed, what to secure, what to document, and when to escalate.

That is why candidates sometimes feel one exam is “harder” than the other. It is usually not about absolute difficulty. It is about which type of thinking comes more naturally to you.

How They Combine Into One Support Skill Set

When you pass both exams, you are showing that you can work across the physical and logical layers of IT support. You can replace hardware, restore software, secure a device, and follow procedure. That combination is why the A+ remains useful as a baseline credential.

For labor-market context, the BLS support role outlook is a good reminder that employers continue to value broad support skills more than narrow specialization at the entry level.

How To Prioritize Study Based On Domain Weighting

The smartest exam prep strategies start with weighting. CompTIA publishes domain percentages for each exam, and those percentages should shape your calendar. If one topic has a heavier weight, it deserves more of your study time. That does not mean you ignore the lower-weight sections. It means you prioritize correctly.

One common mistake is to study all domains equally because they feel equally unfamiliar. That sounds fair, but it is inefficient. A better plan is to study the highest-weight topics first, then fill the gaps in the smaller domains. Use practice tests to identify where your accuracy drops, then spend more time there.

Practical Study Planning Tips

1. Read the official exam objectives for each exam separately.
2. Mark the highest-weight domains in each objective list.
3. Create two study tracks: one for 220-1101 and one for 220-1102.
4. Use labs and practice questions to confirm understanding.
5. Adjust time based on missed questions, not just comfort level.

Experience also changes the plan. If you already have hardware repair experience, 220-1101 may need less time than 220-1102. If you have strong Windows troubleshooting skills, you may need more time on networking and mobile support. Build around your actual background, not an idealized one.

Recommended Study Resources And Tools

The best study plan starts with the official exam objectives, because they define what CompTIA can test. After that, add hands-on practice and a few targeted tools that reinforce recall. This is where exam prep gets real. Reading alone will not prepare you for performance-based questions.

Use physical hardware if you have it. Open a desktop case, identify components, trace cables, and practice safe installation habits. Use virtual machines to practice OS tasks, user profiles, snapshots, and recovery. Use command-line utilities and system tools until the steps feel familiar. If you can do it once under no pressure, you are much more likely to handle it during the exam.

For official learning references, lean on vendor documentation and standards-based sources. For Windows tasks, use Microsoft Learn. For cloud concepts, use AWS. For security framing, use NIST and CISA.

Tools That Help You Retain More

• Flashcards for ports, commands, and security terms
• Cheat sheets for troubleshooting steps and acronym recall
• Spaced repetition for long-term memory
• Lab practice for Windows tools, users, and permissions
• Ticket scenarios for support workflow thinking

Lab simulators and ticket-based practice scenarios are especially useful because they force you to think in context. A list of facts is not the same as knowing how to use them when a device fails, a user calls in, and the clock is running.

Common Mistakes Candidates Make When Comparing The Two Exams

One of the most common mistakes is assuming both exams cover the same subjects with the same depth. They do not. They overlap in troubleshooting mindset, but they differ sharply in what they emphasize. That misunderstanding leads to poor time allocation and shallow review.

Another mistake is mixing hardware topics from 220-1101 with security and procedures from 220-1102 during study sessions without separating them. If you do that, you may feel productive, but your recall gets muddy. The exams reward clear mental separation. Build two outlines, two review cycles, and two sets of practice notes.

Other Mistakes That Hurt Scores

• Overmemorizing without understanding practical use
• Ignoring performance-based questions
• Skipping domain percentages
• Studying only familiar topics
• Failing to practice scenario thinking

Memorization is useful for ports, protocols, and commands. It is not enough for real problem-solving. If you cannot explain why an answer is correct, you are vulnerable to distractors that look similar on the exam.

Industry research from firms like SANS Institute consistently shows that practical skill and repetition matter more than surface familiarity. That aligns perfectly with CompTIA’s exam style.

Conclusion

The main distinction is simple. 220-1101 focuses on hardware, networking, mobile devices, virtualization, cloud basics, and troubleshooting. 220-1102 focuses on operating systems, security, software troubleshooting, and operational procedures. Each exam covers a different side of the same IT support job.

Taken together, they validate broad entry-level competence. That is why this certification comparison matters: it helps you build a study plan that matches the actual exam structure instead of guessing which topics deserve your attention. If you understand the split, you can study with more focus, answer scenario questions more confidently, and avoid wasting time on the wrong material.

Use the official CompTIA objectives, build separate study tracks, practice hands-on tasks, and keep the exam domains in view as you prepare. If you are working through ITU Online IT Training’s CompTIA A+ Certification 220-1201 & 220-1202 Training, this domain-by-domain view should help you connect the lessons to the exam faster. That is the real advantage: better focus, better recall, and better results.

CompTIA® and A+™ are trademarks of CompTIA, Inc.