CompTIA A+ Exam Objectives (220-1201 and 220-1202): Domains and Weights

The nine A+ domains at official V15 weight

A+ splits across two exams. CompTIA fixes the domain weighting for each. Core 1 (220-1201) has five domains and Core 2 (220-1202) has four, for nine domains in total. The weights below are the official V15 percentages, and the question-count column shows roughly how many of a 90-item exam fall into each domain when you apply that weighting per core.

Core 1 Domain 1.0: Mobile Devices (13%)

Where many support calls start. It covers laptop and mobile hardware, display components, accessories, mobile connectivity including eSIM, and application support. The items lean practical: configuring connectivity, installing components, and recognizing which accessory or setting a device needs.

At 13% of Core 1 it is a mid-weight domain, trimmed slightly under V15. Lock the concrete details, the connectors, the connectivity types, and the common configuration steps, because the exam tests specifics rather than definitions.

• 1.1 Given a scenario, monitor mobile device hardware and use appropriate replacement techniques
• 1.2 Compare and contrast accessories and connectivity options for mobile devices
• 1.3 Given a scenario, configure basic mobile device network connectivity and provide application support
• Core 1 domain 1.0 in our bank: 62 practice questions across 3 objectives.

Core 1 Domain 2.0: Networking (23%)

Concrete ports, connectors, and settings. It covers ports and protocols, network hardware, wireless standards including Wi-Fi 6E on the 6 GHz band, Software-Defined Networking basics, SOHO router configuration, and network services. This is a recall-and-apply domain: you need to know specific TCP and UDP ports, cable and connector types, and which single setting achieves a stated networking outcome.

At 23% of Core 1 it grew under V15 and is now a large slice of the exam. Memorize the common ports cold, learn the Wi-Fi 6E band and channel implications, and practice reading a SOHO scenario and picking the exact setting change that meets the requirement.

• 2.1 Compare and contrast TCP and UDP ports, protocols, and their purposes
• 2.2 Explain wireless networking technologies
• 2.3 Summarize services provided by networked hosts
• 2.4 Explain common network configuration concepts
• 2.5 Compare and contrast common networking hardware devices
• 2.6 Given a scenario, configure basic wired and wireless SOHO networks
• 2.7 Compare and contrast internet connection types, network types, and their characteristics
• 2.8 Explain networking tools and their purposes
• Core 1 domain 2.0 in our bank: 103 practice questions across 8 objectives.

Core 1 Domain 3.0: Hardware (25%)

The heaviest Core 1 knowledge domain. It covers cables and connectors, RAM and storage types including DDR5 memory and M.2 NVMe drives, motherboards and CPUs, power supplies, and installing peripherals. This is where raw recall pays off: you need to recognize components, match connectors to ports, and know the right part for a stated need.

At 25% it is a quarter of Core 1. Build a mental catalog of connectors, RAID levels, RAM types including DDR5, M.2 keying, and expansion interfaces, and drill it until recognition is automatic.

• 3.1 Compare and contrast display components and attributes
• 3.2 Summarize basic cable types and their connectors, features, and purposes
• 3.3 Compare and contrast RAM characteristics
• 3.4 Compare and contrast storage devices
• 3.5 Given a scenario, install and configure motherboards, CPUs, and add-on cards
• 3.6 Given a scenario, install the appropriate power supply
• 3.7 Given a scenario, deploy and configure multifunction devices, printers, and settings
• 3.8 Given a scenario, perform appropriate printer maintenance
• Core 1 domain 3.0 in our bank: 113 practice questions across 8 objectives.

Core 1 Domain 4.0: Virtualization and Cloud Computing (11%)

The lightest Core 1 domain by count. It covers cloud models and characteristics, client-side virtualization, and container concepts: what a hypervisor needs, how containers differ from virtual machines, and the difference between the common cloud service and deployment models.

At 11% it is the smallest slice of Core 1, so do not over-invest, but it is a reliable source of easy points. Learn the cloud model vocabulary, the containers-versus-VMs distinction, and the client-side virtualization requirements and bank those questions.

• 4.1 Explain virtualization concepts
• 4.2 Summarize cloud computing concepts
• Core 1 domain 4.0 in our bank: 52 practice questions across 2 objectives.

Core 1 Domain 5.0: Hardware and Network Troubleshooting (28%)

The largest single Core 1 domain. It covers diagnosing hardware, storage, display, mobile, and network problems using the correct troubleshooting methodology. The questions reward the correct ORDER of steps and choosing the best NEXT step among several valid-sounding actions.

At 28% it is more than a quarter of Core 1. Know the troubleshooting method cold, identify the problem, establish a theory, test, plan, verify, document, and practice picking the earliest, least-invasive correct action rather than the eventual fix.

• 5.1 Given a scenario, troubleshoot motherboards, RAM, CPUs, and power
• 5.2 Given a scenario, troubleshoot drive and RAID issues
• 5.3 Given a scenario, troubleshoot video, projector, and display issues
• 5.4 Given a scenario, troubleshoot common mobile device issues
• 5.5 Given a scenario, troubleshoot network issues
• 5.6 Given a scenario, troubleshoot printer issues
• Core 1 domain 5.0 in our bank: 133 practice questions across 6 objectives.

Core 2 Domain 1.0: Operating Systems (28%)

A leading domain across both cores, tied with Security in Core 2. It covers Windows 11 and Windows 10 features and tools, command-line utilities, installation and configuration, and deeper macOS and Linux coverage. The items are heavily applied: which utility, which command, which setting achieves the stated result.

At 28% of Core 2 it is more than a quarter of that exam on its own. Prioritize Windows 11 tools and command-line utilities, learn the Linux commands and permissions V15 leans on, and practice matching a task to the exact utility or command that performs it.

• 1.1 Explain common operating system types and their purposes
• 1.2 Given a scenario, perform OS installations and upgrades in a diverse environment
• 1.3 Compare and contrast basic features of Microsoft Windows editions
• 1.4 Given a scenario, use Microsoft Windows operating system features and tools
• 1.5 Given a scenario, use the appropriate Microsoft command-line tools
• 1.6 Given a scenario, configure Microsoft Windows settings
• 1.7 Given a scenario, configure Microsoft Windows networking features on a client or desktop
• 1.8 Explain common features and tools of the macOS desktop operating system
• 1.9 Identify common features and tools of the Linux client or desktop operating system
• 1.10 Given a scenario, install applications according to requirements
• 1.11 Given a scenario, install and configure cloud-based productivity tools
• Core 2 domain 1.0 in our bank: 133 practice questions across 11 objectives.

Core 2 Domain 2.0: Security (28%)

Where support meets protection, and now tied for the heaviest Core 2 domain under V15. It covers physical and logical security, Zero Trust concepts, Endpoint Detection and Response, malware detection and removal, social engineering, wireless security, and workstation and mobile-device hardening. Many items hinge on the documented, safe procedure rather than the fastest technical fix.

At 28% it is more than a quarter of Core 2 and gained weight under V15. Learn the malware-removal process in order, understand what EDR and Zero Trust add beyond traditional antivirus and network trust, and know the hardening steps for workstations and mobile devices, because the exam rewards the correct procedure, not the quick hack.

• 2.1 Summarize various security measures and their purposes
• 2.2 Given a scenario, configure and apply basic Microsoft Windows OS security settings
• 2.3 Compare and contrast wireless security protocols and authentication methods
• 2.4 Summarize types of malware and tools and methods for detection, removal, and prevention
• 2.5 Compare and contrast common social engineering attacks, threats, and vulnerabilities
• 2.6 Given a scenario, implement procedures for basic SOHO malware removal
• 2.7 Given a scenario, apply workstation security options and hardening techniques
• 2.8 Given a scenario, apply common methods for securing mobile devices
• 2.9 Compare and contrast common data destruction and disposal methods
• 2.10 Given a scenario, apply security settings on SOHO wireless and wired networks
• 2.11 Given a scenario, configure relevant security settings in a browser
• Core 2 domain 2.0 in our bank: 134 practice questions across 11 objectives.

Core 2 Domain 3.0: Software Troubleshooting (23%)

The Core 2 counterpart to Core 1 troubleshooting. It covers diagnosing operating-system, application, and malware problems and mobile-device software issues, in the correct order. Like its Core 1 sibling, it rewards the best NEXT step, not the eventual outcome.

At 23% it is close to a quarter of Core 2. Practice reading a software-symptom scenario and choosing the correct next diagnostic or remediation step, especially for malware and Windows boot issues.

• 3.1 Given a scenario, troubleshoot common Windows OS issues
• 3.2 Given a scenario, troubleshoot common mobile OS and application issues
• 3.3 Given a scenario, troubleshoot common mobile OS and application security issues
• 3.4 Given a scenario, troubleshoot common personal computer security issues
• Core 2 domain 3.0 in our bank: 104 practice questions across 4 objectives.

Core 2 Domain 4.0: Operational Procedures (21%)

The policy-and-procedure domain that trips up hands-on candidates. It covers documentation, change management, safety and PPE, environmental controls, incident response, the appropriate use of AI-assisted tooling, and professional communication. The best answer is often the documented, compliant action rather than the fastest one.

At 21% it is roughly a fifth of Core 2. Technically strong candidates underestimate it because it is about process and judgment. Learn the change-management steps, the safety and disposal procedures, the responsible use of AI-assisted tools, and the professional-communication expectations the same way you learned the hardware catalog.

• 4.1 Given a scenario, implement best practices associated with documentation and support systems information management
• 4.2 Given a scenario, apply change management procedures
• 4.3 Given a scenario, implement workstation backup and recovery methods
• 4.4 Given a scenario, use common safety procedures
• 4.5 Summarize environmental impacts and local environment controls
• 4.6 Explain the importance of prohibited content or activity and privacy, licensing, and policy concepts
• 4.7 Given a scenario, use proper communication techniques and professionalism
• 4.8 Explain the basics of scripting
• 4.9 Given a scenario, use remote access technologies
• 4.10 Explain basic concepts related to artificial intelligence (AI)
• Core 2 domain 4.0 in our bank: 91 practice questions across 10 objectives.

How the weighting should shape your study plan

Study in weight order within each core. In Core 1, Hardware and Network Troubleshooting and Hardware together account for more than half the exam, so they earn the most points per hour. In Core 2, Operating Systems and Security are tied at the top. Virtualization and Cloud Computing is the lightest Core 1 domain but is a quick source of easy points, so lock it early rather than skipping it.

Each core is scored on its own 100 to 900 scale, Core 1 at 675 to pass and Core 2 at 700, with no minimum you must hit in any single domain. That means the smart move is to protect your points in the two heavy domains of whichever core you are sitting rather than chasing perfection in a light one.

Because A+ is two exams, plan your prep core by core, and do not let a strong Core 1 lull you into neglecting Core 2. The fastest way to see where you actually stand across both cores is a timed diagnostic that reports your score by domain. That turns this weighting map into a personal priority list instead of a generic one.