Study CompTIA 220-1202 Windows Editions, Tools, and Recovery Paths: key concepts, common traps, and exam decision cues.
Operating-systems questions on Core 2 are mostly Windows judgment questions. CompTIA is checking whether you can identify the correct tool, feature boundary, or recovery lane before you reach for the most disruptive fix.
WinRE: Windows Recovery Environment, the repair environment used when normal startup or in-session repair tools are not enough.
In-place upgrade: Installing a newer or repaired Windows image while keeping the user environment and applications when supported.
The exam usually wants you to:
Core 2 does not expect an exhaustive SKU matrix. It expects you to know where common support choices break because the edition does not provide the feature.
| Feature or support assumption | Better first reading |
|---|---|
| BitLocker | not every edition gives you the same support path, so verify edition fit first |
| Group Policy Editor | usually points to Pro or Enterprise style management assumptions, not Home |
| RDP host capability | separate remote-control expectations from mere remote-client capability |
| domain join | do not assume a Home device behaves like a domain-managed Pro device |
| If the issue is really about… | Strongest first tool lane |
|---|---|
| startup impact from drivers or services | Task Manager startup, msconfig, Safe Mode, then WinRE if normal startup is blocked |
| disk, partition, or volume state | Disk Management, diskpart, chkdsk |
| system file integrity | DISM and sfc |
| repeated crashes or unexplained failure history | Event Viewer, Resource Monitor, and system-information clues |
| device or driver behavior | Device Manager and rollback logic |
| policy or account behavior | Local Users and Groups, Group Policy, gpupdate, gpresult, and account scope checks |
flowchart LR
A["Read exact symptom"] --> B["Profile, app, startup, disk, or boot?"]
B --> C["Use least disruptive in-session tool first"]
C --> D["Safe Mode or rollback if timeline points to a change"]
D --> E["WinRE repair or restore if normal path is blocked"]
E --> F["Reset or rebuild only when smaller moves are not enough"]
Many wrong answers are technically possible, but too broad too early. Core 2 usually prefers:
CompTIA likes scenarios where the technical step is simple, but the support decision is not.
| Scenario cue | Better reading |
|---|---|
| user keeps important local data and preferences | backup and compatibility checks before upgrade or repair install |
| mixed hardware or older device | verify CPU, RAM, storage, driver, and firmware fit before upgrade assumptions |
| imaging or remote deployment | treat it as deployment choice, not just “install Windows from USB” |
| MBR vs GPT or UEFI questions | read them as boot-model and partition-style compatibility questions |
Even though Windows dominates Core 2, CompTIA still expects quick platform recognition.
| Platform | High-yield anchors |
|---|---|
| macOS | Disk Utility, FileVault, Time Machine, Finder, Keychain, Terminal |
| Linux | sudo, chmod, chown, package managers, /etc config files, basic network and filesystem tools |
| ChromeOS and mobile OSs | role and purpose awareness more than deep administration |
| Trap | Better reading |
|---|---|
| using WinRE for a problem that only affects one application | stay in the app or profile lane first |
assuming every Windows machine can join a domain or use gpedit |
verify edition and management model |
running sfc only when the component store itself may be damaged |
pair DISM and sfc when the image may be corrupted |
| treating “slow login” as a boot issue | check profile load, startup items, domain reachability, and policy timing |
A user reports that after a recent driver update, Windows reaches the sign-in screen but becomes unstable immediately after logon. Which answer best matches Core 2 support logic?
Correct answer: B. The timeline points to a reversible driver-related change. Core 2 usually prefers rollback or Safe Mode before broader recovery actions.