Study CompTIA 220-1202 Boot, Update, and Connectivity Failures: key concepts, common traps, and exam decision cues.
Once you can classify the symptom family, Core 2 still expects you to work the failure mode correctly: degraded performance, boot failure, service startup problem, update breakage, or mobile connectivity issue.
Time drift: A device clock drifting away from the correct time, which can break authentication, scheduling, and domain behavior.
No OS found: A startup failure where the system cannot locate a bootable operating system, often pointing to boot path, storage, or partition issues rather than to ordinary application failures.
The exam usually wants you to:
| Symptom | Strongest first lane |
|---|---|
| BSOD or frequent shutdowns | driver, hardware-adjacent, update, or kernel-level stability path |
| degraded performance or low-memory warning | startup load, memory pressure, process pressure, or system resource path |
| service not starting | dependency, startup type, permissions, or recent change |
| no OS found or boot issue | boot order, storage path, partition, or repair environment |
| time drift on managed device | sync, domain, or service path rather than random app failure |
| USB controller resource warning | driver, resource, or device-management path |
| Symptom | Strongest first lane |
|---|---|
| app fails to update or install | compatibility, store source, storage, permissions, or OS state |
| OS fails to update | storage, policy, connectivity, or device-support path |
| random reboots | app load, OS stability, patch state, battery, or malicious behavior |
| Wi-Fi, Bluetooth, or NFC issue | radio, pairing, settings, or OS connectivity path |
| battery drains fast | process load, radio behavior, patch state, or malicious app activity |
flowchart TD
A["Name the failure mode"] --> B["Boot, service, update, performance, or connectivity?"]
B --> C["Choose the tool or lane that matches that mode"]
C --> D["Check recent change, logs, settings, and dependencies"]
D --> E["Escalate only if the narrower repair path fails"]
| Trap | Better reading |
|---|---|
| treating slow performance like a boot failure | use process, startup, and memory logic first |
| calling every update failure “corruption” | check storage, support, connectivity, and policy before rebuild logic |
| ignoring time drift | clock issues can break sign-in and networked behavior |
| treating mobile connectivity and battery symptoms as purely hardware | settings, app behavior, and OS state often explain them first |
| If two answers both sound possible… | Stronger first move |
|---|---|
| one answer uses targeted rollback and the other rebuilds everything | targeted rollback usually comes first |
| one answer checks service state and dependency while the other reinstalls Windows | service logic is narrower and often stronger |
| one answer checks Wi-Fi, Bluetooth, or NFC settings and the other replaces the device | settings and path verification come first unless hardware evidence is explicit |
A managed Windows laptop is slow, takes a long time to load the user profile, and fails domain resources intermittently. Which answer best fits Core 2?
Correct answer: B. Slow profile load plus intermittent domain-related failures points toward startup, profile, and time or reachability behavior rather than to unrelated hardware.