Use this study plan when you want a real route through 220-1202 instead of bouncing between random Windows commands and security terms. Core 2 rewards process discipline: right scope, right recovery order, right permission boundary, and right operational habit.
Study loop
Each study block should do four things:
- classify the problem as OS, security, software troubleshooting, or operational procedure
- choose the safest supported fix or workflow
- do a short mixed question set or mini-lab
- write down whether the miss was scope, order, access boundary, or process discipline
flowchart LR
Classify["Classify OS / security / troubleshooting / procedure"] --> Fix["Choose safest supported move"]
Fix --> Drill["Do short question set or mini-lab"]
Drill --> Review["Review why misses happened"]
Review --> Classify
Background-based pacing
| Starting point |
Typical study time |
Good timeline |
| already doing help desk or desktop support work |
20-35 hours |
3-5 weeks |
| comfortable with basic support but weaker in OS internals or security |
30-45 hours |
4-6 weeks |
| new to structured endpoint support work |
45-65 hours |
6-8 weeks |
30-day intensive plan
| Week |
Focus |
Output |
| 1 |
OS: Windows tools, editions, admin utilities, profiles, and file systems |
anchor notes and short drills |
| 2 |
Security: security controls, permissions, malware sequence, BitLocker, and account models |
access and security tie-break sheet |
| 3 |
Software: startup issues, app failures, Safe Mode, WinRE, and repair tools |
weak-lane notes and mixed sets |
| 4 |
Procedures: documentation, backups, scripting awareness, and full mixed review |
final readiness check |
60-day balanced plan
| Phase |
Weeks |
Focus |
| 1 |
1 to 2 |
OS: Windows tools, editions, filesystems, and command anchors |
| 2 |
3 to 4 |
Security: permissions, account models, and malware workflow |
| 3 |
5 to 6 |
Software: troubleshooting order, recovery tools, logs, and update or driver issues |
| 4 |
7 |
Procedures: backups, communication, and scripting awareness |
| 5 |
8 |
weak-lane repair and mixed review |
90-day part-time plan
| Month |
Focus |
Goal |
| 1 |
OS and account-boundary fundamentals |
stop losing points to tool and scope confusion |
| 2 |
Security, recovery, and Software |
build stronger order-of-operations judgment |
| 3 |
Procedures and mixed review |
finish with clean scenario classification |
If misses cluster here, do this next
| Miss pattern |
Weak lane |
Fix next |
| you keep choosing a bigger fix than needed |
recovery order |
review rollback, repair, restore, then reset |
| you miss access or admin questions |
permissions |
review share vs NTFS, inheritance, ownership, and UAC |
| you know the symptom but not the malware sequence |
security workflow |
review identify, quarantine, remediate, restore-point logic |
| you solve the tech issue but miss the process answer |
operational procedures |
review documentation, safety, change control, and communication |
What strong prep usually does
- separates user profile, application, operating system, network, and security causes before changing settings
- turns recovery misses into short rules such as
least disruptive supported fix first
- practices the same-version rule for Core 1 and Core 2 so booking decisions stay correct
- keeps permissions, malware handling, and recovery order distinct instead of blending them together
Booking signal
You are getting close when:
- effective permissions, UAC, BitLocker, WinRE, and restore choices no longer blur together
- you can explain why one troubleshooting step is safer or earlier than another
- your misses narrow into clear buckets such as security workflow, Windows tools, troubleshooting order, or operational procedure
Final 72-hour plan
| Keep doing |
Stop doing |
| rereading the cheat sheet for commands, recovery paths, and high-confusion pairs |
opening unrelated new tools or random utility packs |
| using the glossary only for terms that still blur together |
trying to memorize obscure syntax with no workflow context |
| checking the resources page for current exam facts and official docs |
trusting unsupported community summaries over the live CompTIA pages |
| using the FAQ for malware, permissions, and reset or restore decision questions |
defaulting to reset or reinstall as the first move |