220-1202 — CompTIA A+ Core 2 Study Plan
A practical 7-day, 14-day, 30-day, and 60/90-day study plan for the CompTIA A+ Core 2 (220-1202) exam.
How to use this Study Plan
This Study Plan is for candidates preparing for the CompTIA A+ Core 2 (220-1202) exam. It is designed to help you turn your available time into a realistic schedule for review, practice questions, hands-on reinforcement, and final exam readiness.
The Core 2 exam is best prepared for with a mix of:
- Operating system command and settings review
- Security concepts and practical security controls
- Software troubleshooting scenarios
- Operational procedures and technician workflow
- Timed practice questions and missed-question analysis
- Short hands-on labs for commands, tools, and configuration paths
Use the current CompTIA exam objectives as your topic checklist. This plan organizes your time; the objectives define what you must know.
Which plan should you use?
| Time until exam | Best plan | Use this if | Main goal |
|---|---|---|---|
| 7 days | Final review sprint | You have already studied most topics | Fix weak areas, build timing, avoid new overload |
| 14 days | Focused recovery plan | You know some content but feel uneven | Cover high-value topics quickly and test daily |
| 30 days | Balanced plan | You can study most days for 1 to 2 hours | Build knowledge, drill questions, and use mocks wisely |
| 60 days | Full preparation path | You are starting early or returning after a break | Learn steadily, practice deeply, and avoid cramming |
| 90 days | Extended path | You are new to IT or have limited weekly study time | Build fundamentals, hands-on confidence, and retention |
Core 2 study priorities
The CompTIA A+ Core 2 (220-1202) exam is not just vocabulary. You need to recognize technician scenarios and choose the safest, most practical next step.
Prioritize these skill areas:
| Area | What to practice | Examples of study tasks |
|---|---|---|
| Operating systems | Install, configure, manage, and troubleshoot common OS features | Windows settings, Control Panel paths, command-line tools, user accounts, files, permissions, updates |
| Security | Identify threats and apply practical controls | Malware response, authentication, permissions, encryption concepts, wireless security, social engineering |
| Software troubleshooting | Diagnose symptoms and select next actions | Boot issues, application crashes, update failures, slow performance, browser problems |
| Operational procedures | Follow professional, safe, documented processes | Change management, ticketing, backups, safety, privacy, incident handling, communication |
| Command-line familiarity | Recognize commands and when to use them | ipconfig, ping, netstat, sfc, chkdsk, gpupdate, Linux/macOS basics where applicable |
| Scenario judgment | Choose the best technician response | Verify symptoms, back up data, document changes, escalate appropriately, preserve evidence |
Daily practice rhythm
Use this rhythm on most study days. Adjust the time blocks based on your schedule.
| Study block | 30-minute day | 60-minute day | 90-minute day |
|---|---|---|---|
| Warm-up review | 5 min | 10 min | 10 min |
| Learn or review one topic | 10 min | 20 min | 30 min |
| Practice questions | 10 min | 20 min | 30 min |
| Missed-question review | 5 min | 10 min | 15 min |
| Hands-on or command review | Optional | Optional | 5 min |
The minimum effective daily session
If you are short on time, do this:
- Review 10 missed-question notes.
- Answer 15 to 20 targeted questions.
- Write down why each miss was wrong.
- Do one quick command, settings, or troubleshooting review.
- End with a short list of tomorrow’s weak areas.
Consistency is more important than one long study day followed by several missed days.
Start with a diagnostic
Before choosing topics, take a diagnostic practice set.
| Diagnostic step | What to do |
|---|---|
| Use a mixed question set | Take 40 to 60 questions across Core 2 topics |
| Time yourself | Do not pause to research answers |
| Mark confidence | Label each answer as sure, unsure, or guessed |
| Review immediately | Spend at least as much time reviewing as answering |
| Build a weak-area list | Group misses by topic, not by individual question |
Diagnostic scoring categories
Do not only look at the final percentage. Sort your results into practical categories.
| Result pattern | Meaning | Action |
|---|---|---|
| High score, high confidence | Likely stable topic | Maintain with light review |
| Correct but guessed | Hidden weakness | Review the concept before exam week |
| Wrong due to vocabulary | Terminology gap | Build flashcards or quick notes |
| Wrong due to scenario wording | Decision-making gap | Practice troubleshooting sequence questions |
| Wrong due to command/tool confusion | Hands-on gap | Run or map the command/tool purpose |
| Wrong due to rushing | Timing issue | Use timed sets twice per week |
7-day final review sprint
Use this plan if your exam is in one week. Do not try to relearn everything. Your goal is to identify what loses points and fix the most fixable weaknesses.
7-day schedule
| Day | Focus | Practice target | Output |
|---|---|---|---|
| 1 | Diagnostic and exam map | 60 to 90 mixed questions | Weak-area list ranked by risk |
| 2 | Operating systems review | 40 to 60 OS questions | Command/settings checklist |
| 3 | Security review | 40 to 60 security questions | Threat/control comparison notes |
| 4 | Software troubleshooting | 40 to 60 troubleshooting questions | Symptom-to-action chart |
| 5 | Operational procedures | 30 to 50 procedure questions | Process and documentation checklist |
| 6 | Timed mock exam | One full timed mock or longest available timed set | Final weak-area sprint list |
| 7 | Light final review | 20 to 30 confidence questions only | Rested, organized exam plan |
7-day rules
- Stop adding large new resources after Day 3.
- Use Day 4 onward for consolidation, not content hunting.
- Review every missed question from the mock.
- Do not take multiple full mocks on the final day.
- Prioritize sleep, timing, and calm decision-making.
What to memorize in the final week
Focus memorization on practical recognition, not isolated trivia.
| Topic | Final-week review action |
|---|---|
| Troubleshooting methodology | Know the order and purpose of each step |
| Malware response | Know containment, remediation, and prevention concepts |
| User account and permission issues | Compare symptoms caused by permissions, profiles, and policies |
| Windows tools | Know what each tool is used for |
| Common commands | Know command purpose and output meaning |
| Operational procedures | Know safe, documented, privacy-aware technician behavior |
| Backup and recovery concepts | Know when to protect data before making changes |
14-day focused plan
Use this if you have two weeks and need a structured catch-up schedule.
Week 1: Rebuild the core
| Day | Focus | Study actions |
|---|---|---|
| 1 | Diagnostic | Take a mixed set; create a weak-area tracker |
| 2 | OS installation and configuration | Review editions/features conceptually, settings, updates, accounts, file systems |
| 3 | Windows tools and command line | Practice command purpose, system utilities, logs, startup tools |
| 4 | macOS, Linux, and mobile OS basics | Review common navigation, commands, update concepts, security settings |
| 5 | Security concepts | Review authentication, authorization, threats, malware, physical security |
| 6 | Security controls and response | Drill wireless security, password practices, incident response, malware cleanup |
| 7 | Weekly timed set | Take 75 to 90 timed questions; review deeply |
Week 2: Troubleshooting and exam readiness
| Day | Focus | Study actions |
|---|---|---|
| 8 | Software troubleshooting | Map symptoms to likely causes and next steps |
| 9 | Boot, update, and performance issues | Review startup repair concepts, patches, services, resource usage |
| 10 | Operational procedures | Review change management, documentation, safety, professionalism, backups |
| 11 | Scenario drills | Practice mixed “best next step” and “most likely cause” questions |
| 12 | Timed mock | Take a full timed mock or equivalent long timed set |
| 13 | Weak-area sprint | Re-study only the topics that caused missed questions |
| 14 | Final review | Light practice, command review, exam-day checklist |
14-day study ratio
| Activity | Percent of study time |
|---|---|
| Practice questions and review | 45% |
| Topic review | 30% |
| Hands-on command/settings review | 15% |
| Final notes and flashcards | 10% |
30-day balanced plan
Use this if you can study most days for about 1 to 2 hours. This is the best plan for many working candidates.
30-day overview
| Phase | Days | Goal |
|---|---|---|
| Baseline and setup | 1-2 | Identify weak areas and gather materials |
| Topic coverage | 3-16 | Review each major Core 2 area |
| Practice and repair | 17-24 | Convert weak areas into reliable points |
| Timed readiness | 25-28 | Use mocks and exam pacing |
| Final review | 29-30 | Consolidate and rest |
Days 1-2: Baseline and study setup
| Day | Tasks |
|---|---|
| 1 | Take a diagnostic set; mark guessed answers; create a missed-question log |
| 2 | Review CompTIA objectives; map each weak area to OS, security, troubleshooting, or procedures |
Set up a tracker with these columns:
| Column | Purpose |
|---|---|
| Date | When you missed it |
| Topic | The actual concept tested |
| Why I missed it | Knowledge gap, misread, guessed, timing, tool confusion |
| Correct rule | The principle that would solve it next time |
| Follow-up task | Review notes, command practice, flashcard, retest |
| Retest date | When you will check retention |
Days 3-9: Operating systems
| Day | Focus | Practice |
|---|---|---|
| 3 | Windows installation, updates, and configuration | OS concept questions |
| 4 | Windows settings, Control Panel, system tools | Tool-identification questions |
| 5 | Users, groups, permissions, profiles | Scenario questions |
| 6 | Command-line tools | Command purpose drills |
| 7 | File systems, storage concepts, recovery tools | Troubleshooting questions |
| 8 | macOS and Linux basics | Mixed OS comparison questions |
| 9 | OS review day | Timed OS set and missed-question repair |
Suggested hands-on review:
Windows command/tool checklist:
- ipconfig: network configuration information
- ping: basic connectivity testing
- tracert: path testing
- netstat: active connections and ports
- nslookup: DNS lookup testing
- sfc: system file integrity review
- chkdsk: disk/file system checking
- gpupdate: refresh Group Policy
- taskmgr: process and performance review
- services.msc: service status and startup review
- eventvwr: event and log review
Do not just memorize command names. Know the situation where each command is useful.
Days 10-15: Security
| Day | Focus | Practice |
|---|---|---|
| 10 | Threats and social engineering | Threat-identification questions |
| 11 | Malware symptoms and response | Malware scenario questions |
| 12 | Authentication and authorization | Account and permission questions |
| 13 | Wireless and network security concepts | Configuration scenario questions |
| 14 | Device hardening and data protection | Control-selection questions |
| 15 | Security review day | Timed security set and missed-question repair |
Security review checklist:
- Can you distinguish phishing, shoulder surfing, tailgating, impersonation, and related attacks?
- Can you identify likely malware symptoms?
- Can you choose a safe first response when infection is suspected?
- Can you compare authentication, authorization, and accounting concepts?
- Can you recognize when permissions, encryption, backups, or updates are the better control?
- Can you explain basic physical security and privacy practices?
Days 16-20: Software troubleshooting
| Day | Focus | Practice |
|---|---|---|
| 16 | Application crashes and errors | Symptom questions |
| 17 | Boot, startup, and login issues | Troubleshooting sequence questions |
| 18 | Performance and resource problems | Cause-and-fix questions |
| 19 | Browser, update, and connectivity symptoms | Mixed software troubleshooting |
| 20 | Troubleshooting review day | Timed troubleshooting set |
Troubleshooting pattern to practice:
- Identify the user’s symptom.
- Protect data before risky changes.
- Determine what changed recently.
- Choose the least disruptive likely fix.
- Verify the result.
- Document the action taken.
Days 21-24: Operational procedures
| Day | Focus | Practice |
|---|---|---|
| 21 | Safety and environmental procedures | Procedure questions |
| 22 | Documentation, ticketing, and change management | Workflow questions |
| 23 | Privacy, professionalism, and communication | Scenario judgment questions |
| 24 | Backup, recovery, and incident process | Mixed procedure questions |
Operational procedures often test judgment. Ask:
- What protects the user’s data?
- What follows policy?
- What should be documented?
- What should be escalated?
- What is the safest next step?
- What avoids unnecessary disruption?
Days 25-28: Timed mock phase
| Day | Task | Review focus |
|---|---|---|
| 25 | Full timed mock or long mixed timed set | Timing, confidence, topic gaps |
| 26 | Deep review of mock | Rewrite missed concepts in your own words |
| 27 | Targeted weak-area drills | 20 to 30 questions per weak area |
| 28 | Second timed mock or mixed set | Confirm improvement and pacing |
Do not take a timed mock and then only check the score. The review is where improvement happens.
Days 29-30: Final review
| Day | Tasks |
|---|---|
| 29 | Review missed-question log, commands, security controls, troubleshooting steps |
| 30 | Light practice only, organize exam logistics, sleep, and stop heavy studying early |
60/90-day full preparation path
Use this path if you are starting early, new to IT, or studying while working full time.
60-day version
| Phase | Days | Focus | Outcome |
|---|---|---|---|
| Foundation | 1-10 | Objectives, OS basics, terminology | You know the exam map |
| Operating systems | 11-22 | Windows, macOS, Linux, tools, commands | You can identify tools and settings |
| Security | 23-34 | Threats, controls, malware, accounts | You can choose practical security responses |
| Troubleshooting | 35-44 | Software, boot, performance, application issues | You can follow scenario logic |
| Procedures | 45-50 | Safety, documentation, professionalism, change process | You can answer judgment questions |
| Practice build | 51-56 | Mixed timed sets and weak-area repair | You improve consistency |
| Final readiness | 57-60 | Mock review and final checklist | You avoid cramming |
90-day version
For a 90-day schedule, keep the same phases but add more repetition and hands-on practice.
| Added time | Use it for |
|---|---|
| Extra OS time | Navigate settings, review tools, compare Windows/macOS/Linux basics |
| Extra security time | Build threat/control tables and practice malware response scenarios |
| Extra troubleshooting time | Create symptom-to-cause maps |
| Extra procedure time | Practice technician communication and documentation scenarios |
| Extra mock time | Use spaced mocks instead of cramming them near the end |
Weekly rhythm for 60/90 days
| Day type | Activity |
|---|---|
| 3 days per week | Topic study plus 20 to 30 targeted questions |
| 1 day per week | Hands-on command, settings, or troubleshooting review |
| 1 day per week | Mixed timed question set |
| 1 day per week | Missed-question repair and flashcards |
| 1 day per week | Rest or light review |
Example 60/90-day weekly template
| Day | Study task |
|---|---|
| Monday | Learn one topic and answer targeted questions |
| Tuesday | Review missed questions and make flashcards |
| Wednesday | Learn next topic and do hands-on review |
| Thursday | Targeted questions by weak area |
| Friday | Mixed timed set |
| Saturday | Deep review and notes cleanup |
| Sunday | Rest or 20-minute light recall |
Hands-on review for Core 2
You do not need an elaborate lab to benefit from hands-on practice. Short, safe review sessions help you connect exam language to real tools.
Practical hands-on checklist
| Topic | Hands-on action |
|---|---|
| Windows tools | Open or locate common administrative tools and know their purpose |
| Command line | Run safe information-gathering commands and interpret what they show |
| User accounts | Review account types, permissions, and password-related settings |
| Updates | Find update history and understand update troubleshooting concepts |
| Logs | Locate system logs and recognize why a technician would check them |
| Services and startup | Review how services and startup items affect troubleshooting |
| Browser settings | Review cache, extensions, proxy settings, and security settings conceptually |
| Security settings | Locate firewall, antivirus, encryption, and authentication-related settings |
| Backup concepts | Review backup and restore options at a conceptual level |
Use a personal test system or safe virtual environment when possible. Avoid making risky changes to a work machine.
Missed-question review method
A missed question is useful only if you turn it into a rule you can apply later.
The 5-step review
| Step | Action | Example |
|---|---|---|
| 1 | Identify the tested concept | Malware response, permissions, command use, ticketing |
| 2 | Explain why your answer was tempting | “I recognized the tool name but not the scenario.” |
| 3 | Write the correct rule | “Use the least disruptive troubleshooting step first.” |
| 4 | Create a follow-up task | Review command list, redo 10 questions, make flashcard |
| 5 | Retest later | Re-answer similar questions after 2 to 4 days |
Missed-question categories
| Category | Fix |
|---|---|
| Vocabulary gap | Make a short definition card with an example |
| Tool confusion | Build a “tool purpose” table |
| Troubleshooting order error | Rewrite the scenario as a step-by-step workflow |
| Security control confusion | Compare the controls side by side |
| Misread question | Underline qualifiers such as first, best, most likely, least |
| Timing problem | Practice smaller timed sets before full mocks |
Good missed-question note format
Use short notes that are easy to review.
Topic: Malware response
Miss: Chose remediation before containment
Correct rule: When compromise is suspected, reduce spread and preserve evidence before making broad changes.
Retest: Do 15 malware-response questions in 3 days.
Timed mock exam strategy
Timed mocks are for readiness measurement and pacing. They are not the best way to learn brand-new material.
When to use mocks
| Study timeline | First timed mock | Second timed mock | Final mock |
|---|---|---|---|
| 7 days | Day 1 or Day 2 diagnostic | Day 6 | Avoid full mock on final day |
| 14 days | Day 7 | Day 12 | Optional light mixed set on Day 14 |
| 30 days | Around Day 25 | Around Day 28 | No heavy mock on Day 30 |
| 60 days | Around Day 40-45 | Around Day 52-56 | Final week only if review time remains |
| 90 days | Around Day 45 | Around Day 70 | Around Day 82-86 |
How to review a mock
After each mock, spend time on four reviews:
| Review type | What to check |
|---|---|
| Score pattern | Which topic areas caused the most misses? |
| Confidence pattern | Which correct answers were guesses? |
| Time pattern | Did you rush at the end or overthink early questions? |
| Scenario pattern | Did you miss “first,” “best,” “most likely,” or “next” wording? |
Mock exam rules
- Do not take a mock if you cannot review it afterward.
- Do not take several mocks back-to-back just to chase a score.
- Treat guessed correct answers as weak areas.
- Rebuild weak concepts before taking the next mock.
- Practice reading the last sentence of the question carefully before choosing.
Performance-based and scenario-style preparation
CompTIA exams may include practical, scenario-style tasks. Prepare by practicing workflows, not just definitions.
| Scenario type | How to prepare |
|---|---|
| OS configuration | Know where settings live and what they control |
| Troubleshooting | Practice selecting the next best step |
| Security response | Know containment, remediation, prevention, and documentation |
| Command use | Know what command fits the symptom |
| Operational procedure | Know when to document, escalate, back up, or communicate |
Scenario decision questions to ask yourself
When you see a long scenario, ask:
- What is the actual symptom?
- What changed recently?
- Is data at risk?
- Is this a security incident?
- What is the least disruptive next step?
- What action verifies the fix?
- What must be documented?
Final-week rules
The final week should reduce uncertainty, not create it.
Stop adding new material
| Time remaining | Rule |
|---|---|
| 7 days | Add only small missing topics from the objectives |
| 3 days | Stop using new full-length resources |
| 2 days | Review only notes, missed questions, and familiar practice |
| 1 day | Light recall, logistics, rest |
Final-week checklist
| Area | Ready when you can… |
|---|---|
| OS tools | Match common tools and commands to technician scenarios |
| Security | Identify threats and select practical controls |
| Malware response | Choose safe response steps in order |
| Troubleshooting | Follow a logical process without jumping to risky fixes |
| Procedures | Choose documented, professional, policy-aware actions |
| Timing | Finish timed sets without rushing the final questions |
| Confidence | Explain why right answers are right and wrong answers are wrong |
Exam-readiness checks
You are closer to ready when these statements are true:
- You have reviewed the current CompTIA objectives and can identify weak topics.
- Your missed-question log is shrinking or repeating only in a few known areas.
- You can complete timed mixed sets without running out of time.
- You can explain missed answers without memorizing the exact question.
- You know common Core 2 commands, tools, security controls, and troubleshooting workflows.
- You have stopped relying on answer recognition and can reason through scenarios.
- You have a final-day plan that includes sleep, identification, timing, and travel or check-in logistics.
If your practice scores are uneven
Uneven scores usually mean your study is too broad or your review is too shallow.
| Problem | Likely cause | Fix |
|---|---|---|
| Strong OS, weak security | Too much tool review, not enough control selection | Drill threats, controls, malware response |
| Strong definitions, weak scenarios | Memorization without troubleshooting practice | Use “best next step” question sets |
| Correct in untimed mode, weak timed mode | Pacing issue | Use 20-question timed drills |
| Same misses repeat | Notes are not being retested | Schedule retest dates for each weak topic |
| Many guessed correct answers | Confidence is unstable | Treat guessed correct answers as misses |
| Poor final-day retention | Too much new material late | Switch to review-only mode |
Practical next step
Choose the schedule that matches your exam date, take a diagnostic mixed set, and build your missed-question log today. Then use targeted CompTIA A+ Core 2 (220-1202) practice to repair weak areas before moving into timed mocks.