RoleMath Study Track · free study companion
A free study companion keyed to the officially published exam domains of CompTIA A+ (220-1201 & 220-1202): what each domain covers in plain language, clearly labeled free resources, a guided lab outline for every domain, and interactive self-checks from our own question bank. CompTIA A+ (Core 1 & 2 V15) objectives
A free, source-cited study companion built on CompTIA's published exam objectives — not official training, not a pass guarantee. Verify the current objectives on the official page before your exam.
Not sure which domain to start with? Take the readiness check on the cert page →
Program blueprint under review
A free two-exam A+ program blueprint that starts from CompTIA's official V15 scope, uses vetted instruction, and turns every domain into a risk-controlled hands-on artifact without claiming instructional completeness or an exam outcome.
This draft exposes RoleMath’s authored sequence and evidence plan. The current labs are guided outlines, not yet a fully fixture-backed course, and objective-leaf coverage has not passed the gold-standard gate. Completion does not predict an exam result.
Choose an outcome
Choose provisionally. Change routes when the work tells you something new about fit, time, or readiness.
Learners who have decided to pursue A+ and need a complete sequence across both current exams.
Completion emphasis: Complete all nine modules and labs, both official sample sets, the integrated capstone, and a final objective-by-objective gap review.
Career changers who want demonstrable support skills and artifacts before deciding when to schedule either exam.
Completion emphasis: Prioritize device, networking, operating-system, security, troubleshooting, and documentation labs; retain anonymized artifacts for interview discussion.
Learners who are still deciding whether hands-on IT support work fits their interests and working style.
Completion emphasis: Complete the diagnostic plus one device, one networking, one operating-system, and one operational-procedures lab; record what felt energizing or frustrating before continuing.
Start safely
Route learners to safe alternatives before they begin; this is a readiness check for the labs, not an eligibility gate or exam prediction.
Ready when: Yes, on personal devices or a disposable virtual machine.
If not yet: Use the observation-only screenshots and written simulation variants until you have an owned or disposable environment.
Ready when: Yes, with written steps available.
If not yet: Start with the operating-system navigation warm-up and practice pwd/cd/dir/ipconfig before networking labs.
Ready when: Yes, with a current host backup plus a guest snapshot before optional VM changes.
If not yet: Use read-only lab variants and complete the host-backup, VM-isolation, change-management, rollback, and cleanup checklist before any configuration exercise.
Ready when: Yes, or you are using the career-fit path without scheduling an exam yet.
If not yet: Review the official A+ page and RoleMath cost page before setting an exam date or buying a voucher.
Ready when: Yes, even if each short block is only 30 to 45 minutes.
If not yet: Choose the steady pace, split each lab across sessions, and defer exam scheduling until the routine is stable.
Plan, then adapt
12 weeks 6-8 hours/week
A flexible planning estimate for learners balancing work or caregiving; spend roughly one week per domain and reserve the final weeks for integration and gaps.
8 weeks 8-12 hours/week
A planning estimate that pairs related domains each week while keeping a separate lab block; slow down when an exit gate is not met.
5 weeks 14-18 hours/week
For learners with prior support experience and a disposable lab environment; this pace is not a recommendation to schedule an exam before gaps are closed.
Evidence-gated sequence
Understand the two-exam structure, choose a goal and pace, establish a safe lab workspace, and record the starting diagnostic.
Build the vocabulary and observation skills that later troubleshooting modules assume.
Modules: Mobile devices, Networking, Hardware, Virtualization and cloud computing
Apply a repeatable symptom-to-hypothesis-to-test process across hardware and connectivity incidents.
Modules: Hardware and network troubleshooting
Practice administering common operating-system controls and explaining how endpoint protections reduce risk.
Modules: Operating systems, Security
Join safe software diagnosis with professional documentation, communication, change control, and evidence handling.
Modules: Software troubleshooting, Operational procedures
Demonstrate a complete support workflow spanning inventory, networking, endpoint security, troubleshooting, documentation, and handoff.
Modules: Mobile devices, Networking, Hardware, Virtualization and cloud computing, Hardware and network troubleshooting, Operating systems, Security, Software troubleshooting, Operational procedures
Before a lab
Show your work
Completing this policy shows coverage and practice inside RoleMath; it does not predict a passing score or replace the vendor's current exam guidance.
Integrated practice
Run a safe, end-to-end support simulation for two personal or fictional endpoints and leave behind the artifacts another technician would need to continue the work.
Safety boundary: Use fictional incidents and read-only evidence from owned devices. Never create an outage, run malware, expose credentials, scan networks without permission, or alter a work-managed endpoint for this capstone.
Finish honestly
Describe the problem-solving process and artifacts as self-directed lab work. Do not call the packet professional experience, an official CompTIA lab, or a RoleMath credential.
Objective source checked 2026-07-09. Recheck objectives every 30 days and resources every 90 days.
The official objective domains and their exam weight — titles & weights only, straight from the vendor’s exam objectives. CompTIA A+ (Core 1 & 2 V15) objectives
This certification is earned through more than one exam, so the domains span all required exams — their percentages add up across exams, not to 100%.
A+ is two separate exams, so the honest sequencing advice is: pick one exam, finish it, then do the other — do not try to study all nine domains at once. Which exam first is genuinely up to you; many people take Core 1 (220-1201) first because it opens with tangible hardware, but Core 2 (220-1202) is just as reasonable if software and security are closer to your current work. Inside each exam, our default is heaviest-weighted domain first, because the published weights tell you where the exam spends its questions. For Core 1 that means Hardware and network troubleshooting (28%), then Hardware (25%), Networking (23%), Mobile devices (13%), and Virtualization and cloud computing (11%) — with the honest caveat that troubleshooting leans on the hardware and networking vocabulary, so if the troubleshooting domain feels like a foreign language, drop back to Hardware and Networking first and return to it. For Core 2 the weights are Operating systems (28%), Security (28%), Software troubleshooting (23%), and Operational procedures (21%) — close enough that order barely matters, though Operating systems is the natural anchor the others build on. This is sequencing advice based on the published weights and how the topics depend on each other, not a claim about the science of learning — if a different order fits how you think, use it.
Module 1 of 9 · 220-1201 domain 5 · 28% of the exam
Core 1 (220-1201), 28%. The heaviest domain on Core 1. Study it after Hardware and Networking, because it applies both — it is where the exam checks that you can diagnose, not just identify.
Plain-language explanation in our own words — paraphrased from, and checked against, the official objectives. CompTIA A+ Core 1 (220-1201) objectives — Hardware and network troubleshooting
This is the heaviest Core 1 domain at 28%, and it is different in kind from the others: it does not add new components, it tests whether you can reason about the ones you already know when they fail. This is the domain that turns a parts-identifier into a technician. It expects you to take a symptom — a machine that will not power on, a display that flickers, a network that drops — and work toward a cause methodically rather than by guessing.
The spine of the domain is the troubleshooting method itself, a repeatable sequence the exam expects you to apply to any problem. In our own words, its steps are: pin down exactly what is wrong and gather information (including asking what changed); form a reasonable theory of the cause; test that theory to confirm or reject it; once confirmed, plan the fix and consider side effects; carry out the fix and verify the whole system works again; and finally document what you found and did. The discipline is resisting the urge to jump to a fix before you understand the problem. On the exam and on the job, 'what would you do first?' almost always rewards the early, methodical steps over the dramatic replacement.
The first applied area is component and system failures. You should be able to connect symptoms to likely hardware causes: no power or no display, unexpected shutdowns and overheating, noises and burning smells, storage that clicks or reports errors, memory faults that cause random crashes, and the visual and audible signals a machine gives during startup when something is wrong. The skill is probabilistic reasoning — a symptom rarely proves one cause, but it makes some causes far more likely than others, and a good technician checks the cheap, likely, reversible things first.
The second applied area is displays. Because so many devices are laptops and all-in-ones, the domain treats screen problems as their own topic: dimness and flicker, distorted or missing images, dead pixels and artifacts, and the difference between a display problem and a graphics or cabling problem behind it. Knowing whether to suspect the panel, the cable, the connection, or the settings is exactly the kind of narrowing this domain rewards.
The third applied area is networking failures, which is why this domain sits after the Networking domain in our suggested order. Here you apply addressing, name resolution, and connectivity knowledge to real breakage: intermittent or no connectivity, slow speeds, wireless that will not associate, and the physical-layer causes (a bad cable, a dead port, a loose connector) that people skip past while blaming software. The domain's throughline is that many 'network problems' are physical, and checking the simple physical causes first is both faster and more professional than reimaging or replacing.
The best way to study this domain is to practice the method on faults rather than memorizing symptom lists, which is what the lab does with a structured, simulated scenario. Take any breakage — real or described — and force yourself through the six method steps out loud, writing a theory before you touch anything. Narrate what you would check first and why, always favoring the cheap, reversible, likely check. That habit is the entire skill this domain measures, and it transfers directly to the Core 2 software-troubleshooting domain. Read the official A+ objectives page for this domain's exact topic list; our explanation paraphrases the method and scope in our own words rather than reproducing CompTIA's wording.
Practice CompTIA's troubleshooting methodology as a repeatable habit by working a written, simulated fault all the way through the six steps — theory before action — so the method becomes automatic before you face a real one.
Two written fault worksheets that each walk cleanly through identify, theory, test, plan, implement/verify, and document — with a theory written before any action. You should be able to feel the method slowing you down in a good way, steering you toward cheap, likely, reversible checks first.
This lab practices the best-practice troubleshooting methodology and the applied hardware/display/network diagnosis that the Hardware and network troubleshooting domain of the official A+ Core 1 (220-1201) objectives covers — see the official objectives page for the exam's own wording.
Stay safe & legal: This is primarily a paper exercise on fictional scenarios. Any physical verification you choose to do should be on a machine you own, powered off and unplugged before touching internal parts, with basic anti-static care (see the Operational procedures domain). Do not experiment on production or work machines.
2RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Module 2 of 9 · 220-1201 domain 3 · 25% of the exam
Core 1 (220-1201), 25%. The second-largest Core 1 domain and the tangible heart of A+ — the physical parts every later troubleshooting question assumes you can name.
Plain-language explanation in our own words — paraphrased from, and checked against, the official objectives. CompTIA A+ Core 1 (220-1201) objectives — Hardware
This is the domain most people picture when they hear 'A+': the physical guts of computers. At 25% it is the second-heaviest Core 1 domain, and it is the one that most rewards hands-on familiarity. It covers the components inside desktops and laptops, the peripherals that plug into them, printers, and — crucially for a support technician — how to tell whether two parts will actually work together. If you have never opened a computer, this domain is where the abstractions of computing finally become objects you can hold.
Begin with the connectors and cables, because they are the vocabulary everything else uses. The domain expects you to recognize the common ports and the cables that mate with them — the video connectors, the several generations and shapes of USB, storage and power connectors inside the case — and to know what each carries. This sounds like rote memorization, but it is really pattern recognition: a technician glances at a cable and knows its job. Flashcards help, but handling real cables helps more.
The core components are the domain's center of gravity. You should be able to explain, in plain terms, what each major part does and how to choose a compatible one: the motherboard and its form factor, the CPU and the socket it must match, memory in its various types and speeds, storage in its spinning and solid-state forms and their interfaces, the power supply and why its wattage and connectors must fit the build, expansion cards, and cooling. The recurring skill — the one the exam probes hardest — is compatibility. A CPU must fit its socket; memory must match the type the board accepts; the power supply must deliver enough clean wattage with the right connectors. Getting one of these gates wrong is how real builds fail to boot, and recognizing the gate before you buy is the professional habit this domain builds.
Peripherals and expansion round out the non-printer hardware: input and output devices, external storage, docking and port replication, and the add-in cards that extend a system. The theme is the same — identify the device, know its interface, and reason about whether it fits the machine in front of you.
Printers earn a large, distinct place in this domain, and career changers often underestimate them. You are expected to understand the major print technologies — laser, inkjet, thermal, impact, and 3D — well enough to describe how each forms an image, what consumables each needs, and the outline of how each is maintained. Laser printing in particular has a multi-step imaging process the exam expects you to understand conceptually. Configuration matters too: connecting printers over USB and the network, sharing them, and managing drivers. Printers generate a disproportionate share of real help-desk tickets, so this material is unusually job-relevant.
The most effective way to study hardware is to make purchasing decisions you never execute, which is exactly what the lab does: spec a complete, compatible build with a free parts picker and let the tool flag the compatibility gates for you. Reading that a CPU must match its socket is forgettable; watching a configurator refuse an incompatible pairing is not. Supplement that by opening any computer you are allowed to open (a personal or retired machine, powered off and unplugged, with basic anti-static care) and naming each part out loud against this domain's list. Read the official A+ objectives page for this domain's exact topic list — our explanation paraphrases the scope rather than reproducing CompTIA's component wording.
Use a free online parts picker to assemble a complete desktop on paper, deliberately trip its compatibility warnings, and learn to see the gates that make or break a real build: CPU socket, RAM type, and power-supply wattage. Nothing is purchased.
A complete, conflict-free parts list plus a written record of the exact moments the tool warned you: a mismatched socket, a wrong RAM type, and an undersized power supply. You have experienced the compatibility gates as refusals from a real tool, which is far stickier than reading about them.
This lab practices the component-identification and compatibility-selection skills (CPU/socket, memory type, storage interface, power supply) that the Hardware domain of the official A+ Core 1 (220-1201) objectives covers — see the official objectives page for the exam's own wording.
Stay safe & legal: This is a paper/planning exercise — you are using a picker's free build feature and buying nothing. If you later open a physical machine to identify parts, power it off, unplug it, and use basic anti-static precautions (an ESD strap or at least touching bare metal to discharge), covered in the Operational procedures domain.
2RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Module 3 of 9 · 220-1201 domain 2 · 23% of the exam
Core 1 (220-1201), 23%. The second-heaviest Core 1 domain, and the vocabulary the Hardware-and-network-troubleshooting domain assumes you already speak — study it before that troubleshooting domain.
Plain-language explanation in our own words — paraphrased from, and checked against, the official objectives. CompTIA A+ Core 1 (220-1201) objectives — Networking
This Core 1 domain teaches how computers find and talk to each other. At 23% it is one of the heavier Core 1 domains, and it is the one career changers most often fear, because it introduces a stack of acronyms all at once. The reassuring truth is that A+ networking is support-technician networking, not network-engineer networking: you are learning enough to connect a device, recognize why it cannot reach the network, and speak the vocabulary confidently — not to design a data center.
The foundation is addressing. Every device on a network needs an identity, and the domain expects you to understand IP addresses in both their common forms, the difference between a private address used inside a home or office and a public one used on the internet, the role of the subnet mask in deciding what counts as 'local,' and the default gateway as the doorway out. A crucial practical thread is how devices normally get addresses automatically through DHCP — and what it means when that fails and a machine falls back to a self-assigned address that cannot reach anything. Recognizing that specific symptom is one of the most useful things this domain teaches.
Next comes name resolution. Humans use names like a website address; machines need numbers. DNS is the translator, and a huge share of everyday 'the internet is down' tickets are really DNS problems in disguise. The tell you should internalize: if a device can reach a server by its number but not by its name, suspect name resolution, not connectivity. That single distinction separates confident troubleshooters from people who reimage machines that were never broken.
Then the physical and logical plumbing. The domain covers the cabling and connectors that carry signals — the common twisted-pair categories, fiber, and the connectors on each — plus the devices that move traffic around: switches that connect a local network, routers that join networks together, access points that add wireless, and the roles of firewalls at the boundary. You should be able to tell these devices apart by job, and understand ports and protocols at the level of 'which well-known port does web or email or remote-desktop traffic use,' because blocked or misconfigured ports are a recurring support cause.
Wireless gets real attention, because most support happens over Wi-Fi now. The domain expects familiarity with the common wireless standards and frequency bands, the trade-off between range and speed, and — importantly — wireless security: the encryption standards that protect a network and why an open or weakly secured network is a problem. Small-office and home-office setup rounds this out: configuring a consumer router, its wireless settings, and basic protections is a genuinely common first-job task.
The way to make this domain stick is to stop reading and start looking at your own network, which is exactly what the lab does. Run the address-inspection commands on your own machine, read what your IP, mask, and gateway actually are, and trace the path your traffic takes to a public site. Every acronym becomes concrete the moment you see it describing your own connection. Pair that with narrating tickets: when someone's device 'has no internet,' practice asking in order — does it have a valid address, can it reach the gateway, can it resolve names, can it reach the destination — because that ordered questioning is both the exam's logic and the job's. Read this domain's section on the official A+ objectives page for the authoritative topic list; our explanation paraphrases that scope rather than copying CompTIA's wording.
Turn networking acronyms into things you have seen on your own connection: read your machine's IP address, subnet mask, and default gateway; confirm you can reach your gateway and the internet; and trace the hops your traffic takes to a public site.
Concrete values for your own IP, subnet mask, and gateway; successful pings to your gateway and to a public address by number; a working (or tellingly failing) ping by name; and a numbered hop list from tracert that starts at your router and walks outward with rising latency. The acronyms are now things you have measured.
This lab practices the IP addressing, DNS/name-resolution, gateway, and connectivity-verification skills that the Networking domain of the official A+ Core 1 (220-1201) objectives covers — see the official objectives page for the exam's own wording.
Stay safe & legal: Run these commands only against your own network, your own gateway, and well-known public services as shown. ping and tracert are read-only diagnostics; do not aim scanning or flooding tools at networks or hosts you do not own or have permission to test.
2RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Module 4 of 9 · 220-1201 domain 1 · 13% of the exam
Core 1 (220-1201). The lightest-weighted Core 1 domain at 13%, and a gentle place to start Core 1 because almost everyone already owns and uses the hardware it describes.
Plain-language explanation in our own words — paraphrased from, and checked against, the official objectives. CompTIA A+ Core 1 (220-1201) objectives — Mobile devices
This Core 1 domain is about the small computers most people carry all day: laptops, tablets, and phones. It asks you to treat them as real systems a technician installs, configures, connects, and repairs — not as sealed appliances. Because it carries the smallest Core 1 weight (13%), it is a comfortable on-ramp, but do not mistake light weight for trivial: mobile support is a large share of real help-desk tickets, so the skills here pay off on day one of an actual support job.
Start with the physical side of laptops. Unlike a desktop where parts are roomy and standardized, laptop components are miniaturized, keyed to a specific chassis, and often shared across a hinge or a ribbon cable. The domain expects you to recognize and reason about the parts you can service — memory modules in their small-outline form, storage in its several shapes, batteries, keyboards, wireless cards, and displays — and to understand that a replacement part must match the specific model, not merely the general category. The recurring skill is compatibility judgment: will this part physically fit and electrically work in this exact machine?
Then the features built into portable hardware. Laptops and tablets pack in capabilities a desktop rarely needs: multiple display and docking arrangements, physical or function-key toggles for wireless radios and screen brightness, fingerprint and facial readers, and rotation or touch sensors. You should be able to explain what each feature does and, more usefully, how to fix it when it misbehaves — a screen that will not auto-rotate, a laptop that will not output to an external monitor, a wireless radio that a function key has quietly switched off.
Connectivity is the domain's busy center. Mobile devices reach the world through cellular data, Wi-Fi, Bluetooth, NFC, and increasingly hotspots and tethering, and each has its own setup story and failure modes. A large slice of this domain is email and account configuration — getting a device to talk to a mail service with the right server settings and security, which is exactly the kind of ticket new technicians face constantly. Bluetooth pairing, its own small ritual of discoverability and confirmation, shows up here too.
The final strand is mobile security and management, and it is where this domain quietly connects to the whole certification. Phones and tablets carry corporate data out of the building, so organizations enforce controls on them: screen locks and biometrics, remote-wipe and remote-locate capability, encryption, and centralized policy pushed through mobile device management. The exam expects you to see why a company would require these controls before a device touches company data, and to configure the device-side settings that satisfy them. Notice that this previews the Core 2 Security domain from the mobile angle — the same protect-the-data logic, applied to hardware that lives in a pocket.
A practical way to study this domain is to treat your own phone and laptop as the lab bench, which is exactly what the lab below does. Walk the settings menus deliberately: find where backup and sync live, where the screen-lock and biometric controls are, where email accounts are added, where the wireless radios toggle. Say out loud what each setting protects or enables. When a friend or family member has a mobile problem, resist the urge to just fix it — narrate which of this domain's areas the symptom falls into first (hardware, connectivity, configuration, or security), because naming the category is the exam skill. For the authoritative topic list, read this domain's section on the official A+ objectives page; this explanation deliberately paraphrases that scope rather than reproducing CompTIA's wording.
Treat your own phone as a device a technician has to secure and support: locate and document its backup/sync, lock-screen, biometric, encryption, and find-my-device settings, and reason about which corporate control each one satisfies. No apps to install, no purchases.
A short written audit of your own device showing which protections are active (lock, biometric, encryption, remote wipe, backup) and which account and radio settings widen its exposure. The point is not to change your phone but to be able to look at any mobile device and name its security and support posture out loud.
This lab practices the mobile configuration, connectivity, and mobile-security/management skills that the Mobile devices domain of the official A+ Core 1 (220-1201) objectives covers — see the official objectives page for the exam's own wording.
Stay safe & legal: Only inspect a device you own. This lab is read-only — record settings, do not change security controls on a device you did not set up (especially a work-managed phone), and never disable a remote-wipe or lock feature to 'test' it.
2RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Module 5 of 9 · 220-1201 domain 4 · 11% of the exam
Core 1 (220-1201), 11%. The lightest domain on either exam, but its ideas — VMs and shared responsibility — recur throughout modern IT support, so learn it well even though it is small.
Plain-language explanation in our own words — paraphrased from, and checked against, the official objectives. CompTIA A+ Core 1 (220-1201) objectives — Virtualization and cloud computing
This Core 1 domain is the smallest on either A+ exam at 11%, but it introduces two ideas that increasingly define the whole industry: running computers inside other computers (virtualization) and renting computing from someone else over the internet (cloud). For a support technician, the value is not deep architecture; it is understanding the vocabulary and the practical responsibilities well enough to support users who live in these environments every day.
Start with virtualization, because it is the more hands-on half and the one you can practice immediately. A virtual machine is a guest computer that exists as software on top of a host, managed by a hypervisor. The domain expects you to understand what problems this solves: running several separated guest systems on one physical box, creating a disposable environment for controlled testing, or running an operating system your hardware would not otherwise host. That separation reduces risk but is not an absolute security boundary. Crucially, a VM still needs real resources allocated to it — processor time, memory, storage, and a network connection — carved from the host. That resource-budgeting reality is a favorite exam theme, and it is why a laptop bogs down when a VM is given too much.
The most important practical concept in the virtualization half is the snapshot: a saved point-in-time state of a VM you can return to. Snapshots make virtual machines useful learning and testing environments because harmless guest changes can be rolled back, but a snapshot is not a host backup and virtualization is not an absolute security boundary. The lab below has you feel the rollback behavior directly, because reading about a snapshot and using one are very different levels of understanding.
The cloud half asks you to reason about renting instead of owning. The domain expects familiarity with the common service models — where the provider hands you infrastructure to build on, or a platform to develop on, or finished software you just use — and the deployment models, from public shared environments to private and hybrid arrangements. Around these sit the properties that make cloud distinctive: resources you can scale up or down on demand, capacity that is measured and often paid for by use, and access from anywhere over the network.
The single most important cloud idea for a support technician is shared responsibility. When an organization uses a cloud service, the provider secures and maintains part of the stack, but the customer remains responsible for the rest — most often their own data, their user accounts, and their configuration choices. This is why 'we moved to the cloud so security is handled' is a dangerous half-truth: misconfiguration and account mismanagement remain the customer's job, and therefore the support technician's job. This idea connects straight to the Core 2 Security domain and to real incidents you will read about for the rest of your career.
The best way to study this domain is to build a VM and use a snapshot yourself, which is exactly what the lab does with free, open-source software. Once you have created a virtual machine, taken a snapshot, deliberately changed something, and rolled it back, the entire virtualization half stops being abstract. For the cloud half, practice explaining shared responsibility in one sentence for a specific example ('the provider keeps the servers patched, but our team still has to configure who can see the files'). Read this domain's section on the official A+ objectives page for the authoritative topic list; our explanation paraphrases that scope rather than reproducing CompTIA's wording.
Create a real virtual machine with free, open-source software, take a snapshot, make a harmless guest change, and roll back to demonstrate a reversible practice environment — useful for controlled learning, but not a host-safety guarantee.
A running Linux guest, a saved snapshot, and — after restore — guest state that has returned to the earlier point with the harmless test changes erased. This demonstrates guest rollback; it does not prove that a VM cannot affect its host or replace a separate host backup.
This lab practices the client-side virtualization concepts — hypervisors, resource allocation, and VM use for testing/sandboxing — that the Virtualization and cloud computing domain of the official A+ Core 1 (220-1201) objectives covers — see the official objectives page for the exam's own wording.
Stay safe & legal: A VM reduces risk but does not guarantee host isolation. Use a supported patched hypervisor on a machine you own, keep a current host backup, verify the official ISO checksum, use NAT rather than bridged networking, disable shared folders/clipboard/drag-and-drop/device passthrough by default, keep real secrets out of the guest, snapshot before changes, and remove unneeded VM files and attachments afterward. Never attach an unknown or unverified image.
2RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Module 6 of 9 · 220-1202 domain 1 · 28% of the exam
Core 2 (220-1202), 28%. Tied for the heaviest Core 2 domain and the natural anchor for the exam — the other Core 2 domains all assume this operating-system fluency.
Plain-language explanation in our own words — paraphrased from, and checked against, the official objectives. CompTIA A+ Core 2 (220-1202) objectives — Operating systems
This is the largest Core 2 domain at 28%, and it is where A+ shifts from hardware to the software that makes hardware usable. It is heavily weighted toward Windows because Windows dominates the business desktops a support technician manages, but it also expects awareness of macOS, Linux, and the mobile operating systems. If Core 1 taught you the body of a computer, this domain teaches its operating mind — how to install it, configure it, keep it healthy, and drive it from both the graphical interface and the command line.
Windows is the center of gravity. The domain expects working familiarity with the everyday administration a technician performs: the settings and control-panel areas that configure a system, user and account management, networking configuration from the OS side, and the built-in tools for managing disks, tasks, services, performance, and devices. You should know these not as trivia but as a toolbox — given a problem, which utility do you open? Installation and setup matter too: the methods of installing or reinstalling Windows, the concepts of clean versus in-place approaches, partitioning and file-system choices, and what it means to prepare a machine for a user.
The command line is a distinct and important strand, and it is one career changers can turn into an advantage. The domain expects comfort with basic commands for navigating and managing files, working with disks and networking, and running tasks with appropriate privileges — on Windows and, at a basic level, on Unix-like systems. The value is not memorizing dozens of flags; it is losing the fear of a text prompt and understanding that the command line often does precisely and repeatably what clicking does slowly. A technician who can navigate directories, inspect a network setting, and manage a file from the command line is measurably more capable.
Cross-platform awareness rounds the domain out. You are expected to recognize the major features and tools of macOS and Linux — how software is installed, where system settings live, the idea of a package manager, and the basic file and permission model — plus the fundamentals of the mobile operating systems from Core 1's mobile domain. The goal is not mastery of every OS; it is not being lost when a ticket involves something other than Windows.
Two practical threads run throughout: file and permission management, and system maintenance. Permissions — who can read, change, or run what — are both an operating-system topic here and a security topic in the next domain, and understanding how users, groups, and access rights combine is one of the most transferable skills on the exam. Maintenance covers the unglamorous habits that keep systems healthy: updates, disk housekeeping, backups, and the built-in tools that support them.
The most effective way to study this domain is at a real prompt, which is what the lab does — safely, inside the VM you built in the virtualization domain, plus your own Windows machine. Practice the same small tasks on both Windows and Linux: create a folder, create a file, list contents, move and copy, view a permission, and create or inspect a user. Doing a task both graphically and from the command line, on two operating systems, cements the concept beneath the syntax. Narrate which built-in Windows tool you would open for a given problem, because that 'which utility?' reflex is exactly what the exam checks. Read this domain's section on the official A+ objectives page for the authoritative topic list; our explanation paraphrases that scope rather than reproducing CompTIA's wording.
Build command-line confidence by performing the same small file, directory, and user tasks two ways — on your own Windows machine and inside your Linux VM — so you understand the concepts beneath the different syntaxes.
The same set of tasks — make a directory, create a file, list, copy, move, view a permission, and identify the current user — completed on both Windows and Linux, with the two permission views (icacls and ls -l) sitting side by side. The syntax differs; the operating-system concepts do not.
This lab practices the Windows and cross-platform command-line, file-management, and permission concepts that the Operating systems domain of the official A+ Core 2 (220-1202) objectives covers — see the official objectives page for the exam's own wording.
Stay safe & legal: Do the exploratory and account-listing steps on your own Windows machine but do NOT create or delete real user accounts there. Do any experimentation with creating or removing users inside the disposable Linux VM, where a snapshot can undo mistakes. Never run commands you do not understand from untrusted sources with administrator/root privileges.
2RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Module 7 of 9 · 220-1202 domain 2 · 28% of the exam
Core 2 (220-1202), 28%. Tied for the heaviest Core 2 domain. If you plan to continue toward Security+, this domain is your on-ramp — study it thoroughly.
Plain-language explanation in our own words — paraphrased from, and checked against, the official objectives. CompTIA A+ Core 2 (220-1202) objectives — Security
This Core 2 domain is tied for the heaviest on the exam at 28%, a signal that CompTIA treats security as core to entry-level support, not a specialty. It is also the natural bridge to the Security+ certification many A+ holders pursue next. The framing here is practical and defensive: how a support technician recognizes threats, applies everyday protections, hardens the systems they manage, and helps users behave safely — not deep security engineering, but the security literacy every technician now needs.
The domain opens with the threat landscape at a support-technician's altitude. You should recognize the common categories of malware by their behavior — software that holds data hostage, programs that masquerade as legitimate tools, self-spreading infections, quiet watchers that log activity, and stealthy code that hides itself — and, just as importantly, the everyday social-engineering attacks that target people rather than machines. Phishing and its relatives, along with tactics like tailgating, impersonation, and manipulation through urgency or authority, are exam staples because they are what real users actually face. The skill is recognition from a description, and it connects directly to the Software troubleshooting domain, where you remediate the infections that get through.
The heart of the domain is the protections a technician configures. This is where Core 1's mobile-security preview and the whole certification's protect-the-data logic come home: authentication and the case for multi-factor authentication, the principle of least privilege and why users should not be administrators, account and password practices, and the access controls that decide who can touch what. On Windows specifically, you are expected to understand the built-in security machinery — user account control, the local security settings, defender-style protections, firewalls, and encryption options — and to know how to configure a workstation to a reasonable baseline.
Hardening and secure configuration form the next strand. The exam expects you to know the routine steps that shrink a system's exposure: keeping software updated, disabling or removing what is not needed, using strong authentication, encrypting where appropriate, and configuring browsers and systems to sensible secure defaults. Wireless and small-office security reappear here from the security angle — choosing strong wireless encryption, changing default credentials on network gear, and segmenting guest access.
Two more strands round the domain out. Physical and facility security reminds you that a locked door, a cable lock, a privacy screen, and proper visitor handling are security controls as real as any software setting — and that a stolen device can defeat elegant digital defenses. And data destruction and disposal covers doing the end of a device's life responsibly: the difference between deleting, wiping, degaussing, and physically destroying media, and why 'I dragged it to the recycle bin' is not secure disposal. This is a surprisingly common real-world responsibility and a frequent exam topic.
The best way to study this domain is to configure protections on a system you control, which is what the lab does — safely, by creating a standard user and inspecting Windows' own access and prompt behavior. Once you have felt user account control challenge an administrative action, and seen what a non-administrator account can and cannot do, least privilege stops being a slogan. Pair that with practicing threat recognition: for each malware type and social-engineering tactic, write a one-line description of how you would spot it. Read this domain's section on the official A+ objectives page for the authoritative topic list; our explanation paraphrases that scope rather than reproducing CompTIA's wording.
See least privilege and Windows access control in action: create a standard (non-administrator) account, watch User Account Control challenge privileged actions, and observe what a limited account can and cannot do — the everyday protections this domain configures.
A working standard (non-admin) account that is stopped by a UAC prompt when it tries a privileged action, an Administrators group that does not include your test account, and a clear felt sense of what least privilege means: the limited account can do its work but cannot silently make system-wide changes. That boundary is exactly what protects a real workstation.
This lab practices the Windows security configuration, User Account Control, account/permission, and least-privilege concepts that the Security domain of the official A+ Core 2 (220-1202) objectives covers — see the official objectives page for the exam's own wording.
Stay safe & legal: Do this only on a Windows machine you own and administer, or in a VM. Creating and deleting a local account is reversible, but do not perform account changes on a work-managed or shared computer. Never lower UAC or disable security protections on a machine other people rely on.
2RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Module 8 of 9 · 220-1202 domain 3 · 23% of the exam
Core 2 (220-1202), 23%. Study it after Operating systems and Security, because it applies both — it is the diagnosis half of the software knowledge those domains build.
Plain-language explanation in our own words — paraphrased from, and checked against, the official objectives. CompTIA A+ Core 2 (220-1202) objectives — Software troubleshooting
This Core 2 domain is the software counterpart to Core 1's hardware-and-network troubleshooting: at 23%, it tests whether you can diagnose and fix problems in operating systems, applications, mobile devices, and — importantly — security incidents like malware. It leans on the same methodical mindset as its Core 1 sibling, applied now to software symptoms, and it is deeply practical because these are the tickets a support technician sees most.
The first area is operating-system problems. You should be able to recognize and reason about the ways Windows misbehaves: systems that will not boot or boot slowly, crashes and stop errors, services that fail, sluggish performance, update problems, and profiles that misbehave. The skill is connecting a symptom to a likely cause and choosing an appropriate recovery tool — the built-in repair, startup, and recovery options — while preserving the user's data wherever possible. That last instinct, fixing without needless data loss, is both a professional value and a recurring exam theme.
The second area is application problems. Software crashes, fails to install or open, throws errors, or misbehaves for one user but not another. The domain expects structured diagnosis: checking versions and recent changes, comparing behavior across user profiles, reading logs and error messages rather than ignoring them, and deciding when to repair, reinstall, or escalate. The throughline is 'what changed?' — the single most productive question in software troubleshooting, because most breakage follows an update, an install, or a configuration change.
The third and most attention-grabbing area is malware symptoms and removal, and it is where this domain and the Security domain interlock. You are expected to recognize the signs of an infected system — unexpected pop-ups, browser redirects and rogue extensions, performance collapse, security tools mysteriously disabled, files or settings changing on their own — and to know the recommended remediation approach at a conceptual level: identify and verify the symptoms, quarantine or isolate the machine so it cannot spread, disable anything that lets the malware restart, remediate with appropriate tools (often after booting into a limited environment where the malware is not active), then educate the user and re-enable protections. Understanding why each step exists — especially isolation and disabling persistence — matters more than memorizing the order.
The fourth area is mobile and browser problems, which carry a security flavor. Mobile devices bring their own symptoms — apps that crash or will not update, battery and performance issues, connectivity failures, and security concerns like unexpected data use or a device behaving as if compromised. Browsers get specific attention because they are a common infection and annoyance vector: unwanted toolbars and extensions, hijacked search and home pages, certificate warnings, and redirects. Recognizing a browser that has been hijacked, and knowing the safe way to clean it up, is a genuinely everyday support skill.
The best way to study this domain is to rehearse the malware-remediation sequence as a concept and to practice structured software diagnosis on your own harmless issues, which is what the lab does — a safe, no-real-malware walkthrough of the remediation steps plus using safe mode. Whenever an app or system misbehaves in your own life, force yourself through the questions this domain rewards: what changed, does it affect one user or all, what do the logs say, and what is the least destructive fix. Read this domain's section on the official A+ objectives page for the authoritative topic list; our explanation paraphrases that scope rather than reproducing CompTIA's wording.
Learn the recommended malware-remediation steps as a concept — with no real malware anywhere — by writing out the sequence against a scenario and then safely practicing the one hands-on skill it relies on: booting Windows into safe mode, a limited environment where most software does not auto-start.
A written remediation worksheet that walks identify, isolate, disable persistence, remediate, verify/re-protect, and educate — plus a controlled boot into Windows safe mode where you can see how few programs auto-start. You have rehearsed the professional malware-response sequence without introducing real malware and with an explicit recovery plan.
This lab practices the malware-symptom recognition and best-practice removal process, plus the OS recovery/safe-mode skills, that the Software troubleshooting domain of the official A+ Core 2 (220-1202) objectives covers — see the official objectives page for the exam's own wording.
Stay safe & legal: This lab involves NO real malware — never download or run actual malicious software to 'practice.' Do the safe-mode step only on a machine you own, ideally a VM with a snapshot you can restore, and return the system to normal boot afterward. Do not experiment on work or shared computers.
2RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Module 9 of 9 · 220-1202 domain 4 · 21% of the exam
Core 2 (220-1202), 21%. The most human domain on the exam. Career changers from service, admin, or coordination work often find it the friendliest — its skills are professionalism, documentation, and safety.
Plain-language explanation in our own words — paraphrased from, and checked against, the official objectives. CompTIA A+ Core 2 (220-1202) objectives — Operational procedures
This Core 2 domain is the one that turns a person who can fix computers into a professional a workplace trusts. At 21% it is a substantial slice of Core 2, and it is often the most reassuring domain for career changers, because its core skills — safety, documentation, communication, and professional conduct — are exactly the workplace competencies many people bring from previous careers. It covers how a technician works safely, records their work, communicates well, handles data responsibly, and behaves ethically.
Safety leads the domain, and it is genuinely important, not box-ticking. You are expected to know how to protect equipment and yourself: electrostatic-discharge precautions that keep static from silently damaging components (straps, mats, proper handling, and equipment grounding), safe handling of the electrical and physical hazards inside equipment, proper lifting technique, and awareness of the toxic and flammable materials in some devices. Environmental responsibility sits alongside safety here — proper disposal of batteries, toner, and other hazardous components, and awareness of the temperature, humidity, and power conditions equipment needs. The ESD material in particular connects back to every hands-on hardware task in Core 1.
Documentation and change management form the domain's professional backbone. The exam expects you to value the paperwork that keeps IT sane: asset inventories and ticketing systems that track what exists and what was done, knowledge-base articles that capture solutions, network and procedure documentation, and — importantly — change management, the discipline of proposing, approving, testing, and recording changes rather than making them ad hoc. A recurring theme is that undocumented or uncommunicated changes are how shared environments break themselves; documentation is a technical control, not bureaucracy.
Backup, recovery, and business continuity appear here as procedures a technician supports: the types and rotation of backups, the difference between backing up and being able to actually restore, and the basic idea that organizations plan for disruption in advance. This overlaps with the operating-system and security domains but is framed here as operational discipline — the habits that mean a failure or an infection is a bad day rather than a catastrophe.
The human strands are where this domain shines and where prior-career skills transfer directly. Communication and professionalism cover how a technician interacts with users and colleagues: clear language without unnecessary jargon, active listening, managing difficult or upset users, setting expectations, punctuality, and respecting confidential material a technician inevitably encounters. Closely related is the incident-response-and-conduct material: recognizing and properly handling prohibited content or activity, preserving evidence and chain of custody when required, and following the licensing, privacy, and regulatory rules that govern data. Scripting and remote-support basics round the domain out — enough awareness of automation and remote-access tools to use them responsibly.
The best way to study this domain is to build the very artifacts it values, which is what the lab does — an asset-and-incident documentation checklist plus a hands-on ESD safety review. Because so much of this domain is procedural, turning it into a checklist you would actually use makes it concrete and memorable. Pair that by connecting each topic to your own prior experience: if you have handled customers, kept records, or followed safety rules in any job, you already understand the spirit of this domain and only need the IT-specific specifics. Read this domain's section on the official A+ objectives page for the authoritative topic list; our explanation paraphrases that scope rather than reproducing CompTIA's wording.
Make this procedural domain concrete by producing two artifacts a real technician uses: a reusable asset-and-incident documentation checklist, and an ESD/electrical safety review you can run before any hardware work.
Two reusable artifacts: an asset and incident/ticket documentation template with example rows, plus an ESD and safety review checklist you could actually follow before opening a machine. Producing them makes this domain's procedural material concrete instead of abstract, and both are things a real technician keeps and uses.
This lab practices the documentation/change-management, communication/professionalism, and safety/ESD/environmental procedures that the Operational procedures domain of the official A+ Core 2 (220-1202) objectives covers — see the official objectives page for the exam's own wording.
Stay safe & legal: This is a documentation and planning exercise. If you later apply the ESD checklist to real hardware, follow it strictly: power off and unplug first, and never open high-voltage components such as power supplies or CRT displays. If you adapt the asset/incident templates to a real organization, treat the records as confidential.
2RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Studying CompTIA A+builds transferable skills that carry across employers and platforms, not just toward this one exam. Each has a free, source-cited RoleMath primer — what it is, a step-by-step free learning path, clearly labeled free resources, and a safe hands-on exercise:
Work through the modules above, then get a personalized read on where you stand: the readiness check maps your background against these same published domains and suggests what to study first — no score, no pass prediction.
Check your CompTIA A+ readiness →Full CompTIA A+ decision page →
A free, source-cited study companion built on CompTIA's published exam objectives — not official training, not a pass guarantee. Verify the current objectives on the official page before your exam.
Certification and vendor names are used only to identify the program this independent study companion refers to. RoleMath is not affiliated with, endorsed by, or sponsored by CompTIA.