The 220-1102 blueprint is split across 4 domains. Weights are the official share of the exam; see the official exam guide for the authoritative breakdown.
What you must be able to do. Choose the correct operating system feature, command-line tool, or configuration setting for a stated requirement across Windows, macOS, and Linux, and match a file system or install method to a scenario.
In one sentenceThe largest domain: Windows editions and tools, the command line, macOS and Linux features, and the file systems and install choices a technician configures day to day.
Recall check: answer these from memory first
- Name the file system to format a removable drive that must hold files larger than 4 GB and work on both Windows and macOS, and say why.
- State the partition and disk limits that separate MBR from GPT.
- Match sfc /scannow, chkdsk, DISM, and gpupdate each to the single symptom or task it is the correct tool for.
What it tests. Operating system administration in breadth: Windows editions and their features, the Control Panel and Settings applets, Windows command-line tools, and the file systems (NTFS, FAT32, exFAT, ext4, APFS) with their limits. It also covers macOS features such as Time Machine and Disk Utility and Linux basics such as chmod and common shell commands, plus install and upgrade methods and the GPT-versus-MBR and partition choices that go with them.
How to study it. Learn each Windows utility by the one symptom or task it owns, because the exam gives you a scenario and wants the tool: sfc for corrupt system files, chkdsk for disk errors, gpupdate for policy, Task Manager for a hung process. Get the file systems exact - exFAT for large files on removable media across operating systems, NTFS for permissions and journaling, FAT32 for its 4 GB file cap - and lock GPT versus MBR partition and disk limits. Add the macOS and Linux equivalents so a cross-platform stem does not catch you out.
Easy to confuse
- exFAT versus FAT32 versus NTFS for a removable drive. FAT32 is widely compatible but caps a single file at 4 GB; NTFS supports large files and permissions but macOS mounts it read-only by default; exFAT supports files well above 4 GB and is natively read and write on both Windows and macOS, so it is the answer for large cross-platform files. The exam pairs the constraint in the stem with the one file system that meets it.
- GPT versus MBR partitioning. MBR supports up to four primary partitions and a 2 TB disk limit and uses BIOS; GPT supports many partitions and disks larger than 2 TB and pairs with UEFI. A stem that claims MBR handles a 4 TB disk, or that GPT is limited to four partitions, is keyed wrong.
- sfc /scannow versus chkdsk versus DISM. sfc /scannow repairs corrupt protected system files, chkdsk finds and fixes file-system and bad-sector errors on a disk, and DISM repairs the underlying component store that sfc draws from. Matching the utility to whether the fault is a system file, the disk, or the image store is exactly what the exam tests.
Worked example from the 220-1102 bank
lock_openFree sampleOperating Systemsmedium
Priya needs to move several 6 GB video files back and forth on a single USB flash drive that must be readable and writable on both Windows 11 and macOS without installing extra software. Which file system should she format the drive with?
- AexFAT, because it supports files well above 4 GB and is natively read/write on both Windows and macOScheck_circle Correct
- BFAT32, because it is the most widely supported removable-media format across desktop operating systems
- CNTFS, because it journals writes and both operating systems fully support reading and writing it
- Dext4, because it is a modern journaling file system that stores large media files reliably
Select exFAT for removable media that must carry files larger than 4 GB with native read/write access on both Windows and macOS. The two hard constraints are files over 4 GB and native read/write on Windows and macOS. FAT32 fails the size limit, NTFS is read-only on macOS by default, and ext4 is not natively mounted by either, so exFAT is the only format that satisfies all of them.
Why A is correct: exFAT was designed for flash media, removes the 4 GB per-file limit, and is natively read/write on modern Windows and macOS, meeting every constraint.
Why B is wrong: FAT32 is broadly compatible, which makes it tempting, but it caps individual files at 4 GB, so a 6 GB video will not fit.
Why C is wrong: NTFS handles large files, but macOS mounts NTFS volumes read-only by default, so Priya could not write to the drive without third-party drivers.
Why D is wrong: ext4 is a capable Linux file system, but neither Windows nor macOS mounts it natively, so it fails the cross-platform requirement.
What you must be able to do. Select the correct security control, permission model, wireless configuration, or data-destruction method for a stated requirement, and identify the malware or social-engineering attack a scenario describes.
In one sentenceThe security core: malware and social engineering, Windows and workstation hardening, NTFS and share permissions, wireless security, and data destruction and disposal.
Recall check: answer these from memory first
- State the effective permission when NTFS and share permissions both apply to a network access, and what applies for local access.
- Pair each of WPA2 and WPA3 with the encryption it should use, and name the legacy protocol that must not be paired with them.
- Match a highest-assurance-destruction requirement and a drive-will-be-reused requirement each to the correct data-handling method.
What it tests. Applied workstation security: recognising malware types and social-engineering attacks, hardening Windows with UAC, strong password policy, account and permission restrictions, and encryption; the NTFS-versus-share permission model and effective permissions; wireless security with the WPA generations and their encryption; and choosing the correct data-destruction or sanitisation method for a stated assurance or reuse requirement, citing the media-sanitisation guidance where relevant.
How to study it. Drill the models that have one right answer under a constraint. Learn that combined NTFS and share permissions resolve to the most restrictive, while local access uses NTFS alone. Fix the wireless pairings - WPA3 current, WPA2 with AES/CCMP, TKIP and WEP legacy and weak - so a WPA3-with-TKIP option reads as wrong on sight. Map each data-destruction method to its requirement: physical destruction for highest assurance or dead drives, sanitisation such as secure or cryptographic erase when the drive will be reused, and outsourced disposal with a certificate for chain-of-custody.
Easy to confuse
- NTFS versus share permissions. When a user reaches a resource over the network, the effective permission is the most restrictive of the combined NTFS and share permissions; local access ignores share permissions and uses NTFS only. A distractor that says share permissions always win, or that the least restrictive applies, is the trap.
- WPA2 with AES versus WPA3, and the TKIP trap. WPA3 is current best practice and WPA2 should use AES (CCMP); TKIP and WEP are legacy and weak. The exam offers WPA2-or-WPA3 paired with TKIP, or WEP where WPA2/WPA3-AES is correct, so the encryption paired with the standard is the discriminator.
- Physical destruction versus sanitisation for reuse. Physical destruction (shred, incinerate, degauss) gives the highest assurance and is for dead drives or top-secret media; sanitisation such as secure erase or cryptographic erase removes data while keeping the drive usable. Choosing destruction where the drive must be redeployed, or erase where the requirement was unrecoverable destruction, is the plant.
- Disabling UAC versus fixing the privilege model. UAC prompts for elevation so standard users run with least privilege; the fix for repeated unwanted prompts is usually correcting the account or permission model, not turning UAC off. An option that disables UAC as the best answer trades security for convenience and is the wrong choice.
Worked example from the 220-1102 bank
lock_openFree sampleSecuritymedium
Priya is redeploying a working laptop SSD to another employee. Company policy requires that the previous user's data be unrecoverable, but the drive itself must stay functional for reuse. Which method should she use?
- ADegauss the SSD using a magnetic degausser rated for the drive's capacity before reassigning it.
- BDelete the existing partitions and perform a quick format of the volume before handing it over.
- CShred the SSD in an approved media shredder and provision a brand-new drive instead.
- DRun the drive's built-in ATA Secure Erase so the flash cells are reset while the SSD stays usable.check_circle Correct
When media must be reused, choose a sanitisation method such as Secure Erase rather than a destructive method or a superficial format. Reuse rules out physical destruction, and SSDs are immune to degaussing because they use non-magnetic flash storage, so a controller-level Secure Erase is the correct sanitisation that preserves the drive.
Why A is wrong: Degaussing is tempting because it works on magnetic media, but an SSD stores data in flash cells that a magnetic field cannot erase, so the data survives.
Why B is wrong: A quick format only clears the file table, so the underlying data remains and is trivially recovered with forensic tools, failing the unrecoverable requirement.
Why C is wrong: Shredding does make data unrecoverable, but it destroys the drive and defeats the stated requirement to reuse the same SSD.
Why D is correct: Secure Erase issued to the SSD controller sanitises every cell, including spare blocks, and leaves a fully working drive that can be reissued.
What you must be able to do. Apply the troubleshooting methodology and the seven-step malware-removal procedure in their published order, and choose the single best next action for a Windows, mobile, or mobile-security symptom.
In one sentenceThe applied domain: diagnosing Windows OS problems, removing malware in the correct order, and resolving mobile OS, application, and mobile-security issues.
Recall check: answer these from memory first
- List the seven malware-removal steps in their published order, marking where System Restore is disabled and where it is re-enabled.
- State where educating the end user falls in the malware-removal procedure and why it is not earlier.
- Give a mobile symptom that signals a security issue rather than an ordinary application fault, and the correct first response.
What it tests. Software fault diagnosis under order-of-operations pressure: common Windows OS problems and the correct tool or repair, the CompTIA seven-step best-practice malware-removal procedure and its fixed sequence, and mobile OS and application issues including the security-specific ones such as data leaks, over-permissioned apps, and rooted or jailbroken devices. Nearly every item is a scenario asking for the most likely cause or the correct next action, so judgement about order and priority is the skill.
How to study it. Learn the seven malware-removal steps as a reflex and practise placing a described action at the right step, because reordering is the most common trap: quarantine and disable System Restore before you remediate, re-enable System Restore and create a restore point after, and educate the user last. Do the same for the six-step troubleshooting methodology applied to software. For mobile, separate an ordinary application issue from a security issue - a data leak or rooted device is security - and choose the cheapest correct fix before a factory reset.
Easy to confuse
- Remediate-first versus quarantine-and-disable-System-Restore-first. The published order quarantines the infected system and disables System Restore in Windows before remediation, so a saved restore point cannot reinfect the machine. An option that scans and removes malware before quarantining, or that re-enables System Restore before the system is clean, reverses the sequence the exam tests.
- A mobile application issue versus a mobile security issue. An application that crashes or drains battery is an ordinary mobile OS or application issue; leaked data, unexpected permissions, or a rooted or jailbroken device is a mobile security issue with a different response. The exam keys the security scenarios to security actions such as reviewing permissions or MDM controls, not just reinstalling the app.
- Factory reset versus a cheaper mobile fix first. A factory reset is the last resort once confirmation and cheaper fixes are exhausted; clearing cache, checking permissions, updating the OS, or uninstalling a suspect app usually comes first. An option that jumps to a factory reset before the cheaper correct step is the over-reaction trap.
Worked example from the 220-1102 bank
lock_openFree sampleSoftware Troubleshootingmedium
Priya updated a banking app on her Android phone and now it force-closes the instant she taps its icon, while every other app runs normally. She does not want to lose her saved logins or in-app data. Which action should the technician try FIRST?
- AClear the app's storage and data from Settings so the app starts from a completely fresh state on next launch.
- BUninstall the app and reinstall the current version from the official app store to replace any damaged program files.
- CForce stop the app, then clear only its cache from Settings, leaving saved data and logins intact before relaunching.check_circle Correct
- DPerform a factory reset of the phone to clear any system-wide corruption that may be affecting the application at launch.
When an app crashes after an update, clear its cache first because it is the least-destructive fix that preserves user data. An app update can leave incompatible cached temporary files that make the app fail at launch. Clearing the cache forces those files to be rebuilt while leaving accounts and saved data untouched, so it is the correct first step before the more destructive clear-data or reinstall options.
Why A is wrong: Clearing storage does often fix a corrupt-state crash, but it also wipes saved logins and in-app data, so it is not the first, least-destructive step when that data must be kept.
Why B is wrong: Reinstalling can resolve the crash, but it is more disruptive than clearing the cache and can remove locally stored data, so it is tried after the lighter step fails.
Why C is correct: Clearing the cache removes stale temporary files left by the update that commonly cause launch crashes, and it preserves accounts and saved data, so it is the correct least-destructive first step.
Why D is wrong: A factory reset is far too drastic for a single misbehaving app and erases all user data, so it is a last resort and never the first action here.
What you must be able to do. Apply documentation, change-management, backup, safety, environmental, privacy, and professionalism procedures in the correct order, and choose the right backup type, script use, or remote-access method for a scenario.
In one sentenceThe procedural domain: documentation and ticketing, change management, backup and recovery, safety and environment, privacy and licensing, communication, scripting basics, and remote access.
Recall check: answer these from memory first
- State what a restore requires for a full, an incremental, and a differential backup, and which types clear the archive bit.
- Put the change-management steps in order from request to implementation, naming what must happen before any change is made.
- Give one remote-access or scripting scenario where the secure option is preferred over the more convenient one, and why.
What it tests. The non-technical-but-tested procedures a technician follows: documentation and ticketing systems, the change-management flow with approval before implementation, backup and recovery including the full, incremental, and differential types and what each restores, safety and environmental handling, privacy, licensing, and regulated-data policy, professional communication, basic scripting use cases and risks, and remote-access methods and their security.
How to study it. Fix the backup types by what a restore needs: full restores from one set, incremental needs the full plus every incremental since and clears the archive bit, differential needs the full plus only the latest differential and does not clear the archive bit. Learn the change-management order so approval and a change request always precede implementation, with a rollback plan documented. For remote access and scripting, weigh security and risk - an unattended remote tool or a script run with too much privilege is the wrong choice when a safer option is offered.
Easy to confuse
- Incremental versus differential backup. An incremental backs up changes since the last backup of any type and clears the archive bit, so a restore needs the full plus every incremental in order; a differential backs up changes since the last full and does not clear the archive bit, so a restore needs only the full plus the latest differential. Swapping their definitions or restore requirements is the classic backup trap.
- Change approval before versus after implementation. A change request and its approval, with a documented rollback plan, come BEFORE any change is implemented; end-user acceptance and verification follow. An option that implements the change first and documents or seeks approval afterwards reverses the change-management order the exam expects.
- A documented backout plan versus an undocumented rollback. A backout or rollback plan is written into the change request before work starts so the change can be reversed safely; relying on an ad-hoc undo during implementation is not change management. The exam rewards the option that plans the reversal in advance rather than improvising it.
Worked example from the 220-1102 bank
lock_openFree sampleOperational Procedureseasy
A user phones the service desk because a shared office printer keeps jamming. So the ticket can be tracked and reassigned to another technician if needed, which detail is most important to capture when first logging the ticket?
- AThe technician's own mobile number so the user can bypass the queue and call back directly later
- BThe affected user's name and contact details together with a clear description of the reported problemcheck_circle Correct
- CA guess at the most likely root cause, entered before any diagnosis has actually been carried out
- DThe final resolution steps, which the technician writes in full before starting any troubleshooting
A ticket must first capture who is affected and a clear problem description so any technician can track, contact, and resolve it. A ticketing system tracks work through its lifecycle; without the requester's identity and a clear symptom description, the ticket cannot be triaged, reassigned, or matched to the caller, which is exactly what tracking depends on.
Why A is wrong: It feels helpful and personal, but routing calls around the ticketing system leaves the issue untracked and impossible to reassign.
Why B is correct: Correct: identifying the user and the symptom is the core of a ticket, letting any technician pick it up, contact the user, and track it to closure.
Why C is wrong: Recording a theory looks proactive, but an unverified guess logged as fact can mislead the next technician and is not the priority at intake.
Why D is wrong: Resolution notes matter, but they cannot be known at logging time; writing them before diagnosis records a fix that has not happened.