220-1201 — CompTIA A+ Core 1 Study Plan
A practical 7-day, 14-day, 30-day, and 60/90-day study plan for CompTIA A+ Core 1 (220-1201) exam preparation.
How to use this Study Plan
This Study Plan is for candidates preparing for the real CompTIA A+ Core 1 (220-1201) exam from CompTIA. It is designed for practical preparation: diagnostics, topic review, hands-on reinforcement, missed-question review, and timed practice.
Core 1 preparation should not be only reading. You need to recognize hardware, select networking options, compare mobile device features, understand virtualization and cloud concepts, and troubleshoot hardware and network problems under exam timing.
Use the plan that matches your available time, then follow the daily rhythm consistently.
Which plan should you use?
| Time until exam | Best for | Main goal | Practice focus |
|---|---|---|---|
| 7 days | Final review or urgent retake | Fix weak areas and improve timing | Daily mixed sets, PBQ-style practice, one or two timed mocks |
| 14 days | Candidates with some prior A+ knowledge | Cover every major area once and review misses | Diagnostic-first study, topic drills, timed sections |
| 30 days | Most candidates | Balanced learning, practice, and review | Objective-by-objective study plus repeated mixed practice |
| 60/90 days | Newer IT candidates or busy schedules | Build durable fundamentals | Hands-on review, spaced repetition, gradual mock exams |
If you are unsure, take a diagnostic practice set first. Your score is less important than the pattern of misses.
Start with a diagnostic
Before choosing what to study first, complete a short diagnostic.
| Step | Action | Time |
|---|---|---|
| 1 | Take 40-60 mixed Core 1 questions without notes | 45-75 min |
| 2 | Mark every question as Know, Guess, or Miss | 10 min |
| 3 | Sort misses by topic | 15 min |
| 4 | Choose your first three weak areas | 10 min |
| 5 | Build the next three study sessions around those areas | 5 min |
Use these Core 1 topic buckets for sorting:
- Mobile devices: laptops, mobile device accessories, ports, display components, wireless connectivity, synchronization, device configuration
- Networking: TCP/IP concepts, common ports, wireless standards, SOHO networking, network hardware, internet connection types
- Hardware: cables, connectors, RAM, storage, printers, motherboards, power, peripherals, custom PC considerations
- Virtualization and cloud computing: client-side virtualization, cloud models, hosted services, virtual networking basics
- Hardware and network troubleshooting: symptoms, probable causes, isolation steps, replacement decisions, and verification
Daily practice rhythm
Use the same rhythm regardless of your timeline. Adjust the duration, not the order.
| Session length | Warm-up | Main study block | Practice block | Review block |
|---|---|---|---|---|
| 45 minutes | 5 min flash review | 15 min one weak topic | 15 min 10-15 questions | 10 min missed-question notes |
| 75 minutes | 10 min flash review | 25 min topic review | 25 min 20-30 questions | 15 min missed-question notes |
| 120 minutes | 10 min recall | 40 min topic + hands-on | 45 min 35-50 questions | 25 min error log review |
A good study day includes:
- Recall before reading: write what you remember first.
- One focused topic: do not jump between five domains in one session.
- Practice questions: answer under light timing pressure.
- Missed-question review: explain why the correct answer is correct and why your answer was wrong.
- One small hands-on action: inspect a setting, identify a connector, compare standards, map a troubleshooting flow, or configure a simple virtual/network scenario.
Missed-question review method
Do not only record the correct answer. Build an error log that changes how you think.
| Error type | What it means | Fix |
|---|---|---|
| Knowledge gap | You did not know the concept | Re-read the objective area and create a short note |
| Misread | You missed a keyword such as best, first, most likely, or least | Slow down and underline decision words |
| Confused pair | Two options looked similar | Make a comparison table |
| Troubleshooting order error | You chose a later step too early | Review the troubleshooting sequence and verification step |
| Port/protocol miss | You confused a service, port, or purpose | Drill with flashcards and scenario questions |
| Hardware identification miss | You could not identify connector, cable, RAM, storage, printer, or motherboard details | Use images, diagrams, or physical inspection if available |
For each missed question, write:
- Topic: networking, hardware, mobile, cloud, troubleshooting
- Why I missed it: knowledge, wording, process, or memorization
- Correct rule: one sentence
- Retest date: 2-3 days later
- Status: open, improved, or closed
7-day final review plan
Use this if your exam is one week away. This is not the time to learn every detail from scratch. Prioritize weak areas, troubleshooting, timing, and recall.
| Day | Main focus | Practice target | Review task |
|---|---|---|---|
| 1 | Diagnostic and weak-area map | 60-90 mixed questions | Build error log and rank top 5 weak areas |
| 2 | Hardware review | 40-60 hardware questions | Cables, connectors, RAM, storage, printers, power |
| 3 | Networking review | 40-60 networking questions | Ports, protocols, SOHO, wireless, network devices |
| 4 | Mobile devices + virtualization/cloud | 40-60 topic questions | Laptop parts, mobile setup, cloud models, virtualization basics |
| 5 | Troubleshooting day | 50-75 scenario questions | Symptoms, first step, most likely cause, verification |
| 6 | Timed mock exam | One full timed mock or two timed half-mocks | Review every miss; no new broad topics |
| 7 | Light final review | 20-40 confidence questions | Review notes, port/protocol list, troubleshooting flow |
7-day rules
- Stop adding new resources after Day 5.
- Do not spend Day 7 taking a difficult mock unless you need timing practice.
- Focus on high-frequency decision skills: what to check first, what is most likely, what is the best replacement, and what verifies the fix.
- Sleep matters more than one more late-night chapter.
14-day focused plan
Use this if you have two weeks and already understand some PC hardware or help desk basics.
| Day | Study focus | Practice |
|---|---|---|
| 1 | Diagnostic and exam objective mapping | 60 mixed questions |
| 2 | Mobile devices: laptop hardware, displays, ports, docking, accessories | 30-40 topic questions |
| 3 | Mobile devices: wireless, synchronization, configuration scenarios | 30-40 topic questions |
| 4 | Networking: TCP/IP basics, ports, protocols, addressing concepts | 40-50 topic questions |
| 5 | Networking: SOHO networks, wireless security concepts, network hardware | 40-50 topic questions |
| 6 | Hardware: motherboards, CPUs, RAM, storage, power, adapters | 40-50 topic questions |
| 7 | Hardware: printers, cables, connectors, peripherals, custom PC scenarios | 40-50 topic questions |
| 8 | Virtualization and cloud computing | 30-40 topic questions |
| 9 | Hardware troubleshooting | 40-60 scenario questions |
| 10 | Network troubleshooting | 40-60 scenario questions |
| 11 | Mixed review of weak areas | 60 mixed questions |
| 12 | Timed mock exam | Full timed mock or timed sections |
| 13 | Missed-question repair day | Retake weak topics only |
| 14 | Final review | Light mixed set, notes, rest, logistics |
14-day emphasis
Spend more time on questions that ask for:
- The first step in a troubleshooting process
- The most likely cause of a symptom
- The best hardware or networking choice for a scenario
- The difference between similar technologies
- Matching connectors, ports, devices, and use cases
30-day balanced plan
Use this if you want a realistic plan that includes learning, practice, and review without cramming.
Weekly structure
| Week | Goal | Study mix |
|---|---|---|
| Week 1 | Build hardware and mobile foundations | Reading/objective review, diagrams, hands-on identification |
| Week 2 | Build networking and cloud foundations | Ports, protocols, SOHO, wireless, virtualization, cloud models |
| Week 3 | Troubleshooting and scenario practice | Hardware symptoms, network symptoms, printer issues, mobile problems |
| Week 4 | Timed practice and weak-area repair | Mocks, error log review, final objective sweep |
30-day calendar
| Day | Focus | Practice target |
|---|---|---|
| 1 | Diagnostic | 60 mixed questions |
| 2 | Mobile device hardware | 25-35 questions |
| 3 | Laptop displays, ports, docks, accessories | 25-35 questions |
| 4 | Mobile connectivity and synchronization | 25-35 questions |
| 5 | Hardware: motherboard, CPU, RAM, BIOS/UEFI concepts | 30-40 questions |
| 6 | Hardware: storage, RAID concepts, power, cooling | 30-40 questions |
| 7 | Review Day 1-6 misses | 40 mixed questions |
| 8 | Cables and connectors | 30-40 questions |
| 9 | Printers and imaging process concepts | 30-40 questions |
| 10 | Peripherals and custom PC selection | 30-40 questions |
| 11 | Networking: IP concepts and common services | 35-45 questions |
| 12 | Networking: ports and protocols | 35-45 questions |
| 13 | Networking: wireless standards and security concepts | 35-45 questions |
| 14 | Timed section review | 60 timed mixed questions |
| 15 | SOHO network hardware and setup | 35-45 questions |
| 16 | Internet connection types and network devices | 35-45 questions |
| 17 | Virtualization concepts | 25-35 questions |
| 18 | Cloud models and hosted service scenarios | 25-35 questions |
| 19 | Hardware troubleshooting method | 40-50 scenario questions |
| 20 | Storage, boot, display, power troubleshooting | 40-50 scenario questions |
| 21 | Review Day 15-20 misses | 50 mixed questions |
| 22 | Printer troubleshooting | 35-45 scenario questions |
| 23 | Mobile device troubleshooting | 35-45 scenario questions |
| 24 | Network troubleshooting | 45-60 scenario questions |
| 25 | PBQ-style practice: matching, ordering, configuration scenarios | 30-45 min plus review |
| 26 | Timed mock exam 1 | Full timed mock |
| 27 | Mock review | Rework every miss |
| 28 | Weak-area sprint | 60 targeted questions |
| 29 | Timed mock exam 2 or timed sections | Full mock if stamina is weak; sections if accuracy is weak |
| 30 | Final review | Light practice, notes, rest |
30-day workload
| Available time per day | Recommended approach |
|---|---|
| 45 minutes | Follow the topic sequence; reduce question counts by half |
| 60-75 minutes | Complete one topic block plus review daily |
| 90-120 minutes | Add hands-on review and larger mixed sets |
| Weekends only | Combine two weekday topics per weekend session and keep short weekday flash review |
60/90-day full preparation path
Use this if you are newer to IT, returning after a break, or studying around work and family.
Phase overview
| Phase | 60-day pace | 90-day pace | Goal |
|---|---|---|---|
| Foundation | Days 1-15 | Days 1-25 | Learn objectives and terminology |
| Topic practice | Days 16-35 | Days 26-55 | Drill each domain and build accuracy |
| Troubleshooting | Days 36-45 | Days 56-70 | Practice symptom-to-cause reasoning |
| Mock exams | Days 46-55 | Days 71-82 | Improve timing and endurance |
| Final review | Days 56-60 | Days 83-90 | Repair weak areas and reduce errors |
60-day plan
| Days | Focus | Actions |
|---|---|---|
| 1-3 | Diagnostic and setup | Take diagnostic, organize notes, download current objectives from CompTIA |
| 4-10 | Mobile devices | Study laptops, displays, ports, accessories, mobile connectivity, synchronization |
| 11-18 | Hardware | Study motherboards, CPU, RAM, storage, power, printers, cables, connectors |
| 19-27 | Networking | Study IP concepts, common ports, protocols, wireless, SOHO, network hardware |
| 28-32 | Virtualization and cloud | Study client-side virtualization, cloud models, hosted services, virtual networking basics |
| 33-42 | Troubleshooting | Drill hardware, printer, mobile, and network troubleshooting scenarios |
| 43-47 | Mixed practice | 60-80 mixed questions every other day; review misses deeply |
| 48-50 | Timed mock 1 and review | Take one timed mock, then spend at least as long reviewing |
| 51-54 | Weak-area sprint | Target lowest three topics from mock results |
| 55-57 | Timed mock 2 and review | Confirm timing and accuracy improvements |
| 58-60 | Final review | Light practice, notes, exam logistics, rest |
90-day plan
| Days | Focus | Actions |
|---|---|---|
| 1-7 | Diagnostic and Core 1 orientation | Baseline test, objective map, study schedule |
| 8-20 | Mobile devices | Slow review with diagrams, physical identification, and topic questions |
| 21-35 | Hardware | Build strong recognition of components, connectors, printers, storage, and power |
| 36-50 | Networking | Ports, protocols, SOHO, wireless, internet connection types, device roles |
| 51-58 | Virtualization and cloud | Compare cloud models, virtualization use cases, resource and networking concepts |
| 59-70 | Troubleshooting | Daily scenario practice across hardware and networking symptoms |
| 71-76 | Mixed review | Timed sets, error log cleanup, flashcard reduction |
| 77-80 | Timed mock 1 and repair | Mock, deep review, targeted drills |
| 81-84 | Timed mock 2 and repair | Mock, compare weak areas, update final list |
| 85-88 | Final weak-area sprint | Only the top remaining weak topics |
| 89-90 | Exam readiness review | Light practice, logistics, rest |
Hands-on review checklist
Even if the exam is multiple-choice and performance-based, hands-on familiarity helps you answer scenario questions faster.
| Topic | Practical action |
|---|---|
| Laptop hardware | Identify common laptop components, ports, display parts, docking options, and replaceable items |
| Mobile devices | Review setup steps for Wi-Fi, Bluetooth, email sync, hotspot/tethering, and account synchronization |
| Cables and connectors | Match connector types to use cases; review video, storage, networking, and power connectors |
| Storage | Compare HDD, SSD, NVMe, optical, removable media, and basic RAID concepts |
| Printers | Review laser, inkjet, thermal, and 3D printing concepts; map symptoms to likely causes |
| Networking | Draw a simple SOHO network with modem/ONT, router, switch, access point, clients, and printer |
| Wireless | Compare common wireless standards, frequencies, encryption concepts, and interference sources |
| Ports and protocols | Drill service purpose, not just numbers |
| Virtualization | Create or review a simple VM conceptually: host, guest, resources, virtual NIC, snapshots |
| Cloud | Compare public, private, hybrid, IaaS, PaaS, SaaS, and common hosted service scenarios |
| Troubleshooting | Practice “symptom, probable cause, test, fix, verify” on realistic support tickets |
What to memorize vs. understand
| Memorize | Understand |
|---|---|
| Common ports and protocols | Why a service uses a protocol and how symptoms appear when it fails |
| Connector names and shapes | Which connector is appropriate for a scenario |
| Printer process terms | How print symptoms map to components or supplies |
| Wireless terms | How range, interference, security, and device compatibility affect choices |
| Storage and RAM terminology | How component choices affect performance and compatibility |
| Cloud model definitions | Which model fits a business or support scenario |
| Troubleshooting steps | Why order matters and when to verify the fix |
Timed mock exam strategy
Timed mocks should be used after you have covered most objectives at least once. Taking too many mocks too early can waste good practice material.
| Timeline | First timed mock | Second timed mock | Final timed practice |
|---|---|---|---|
| 7 days | Day 6 | Optional shorter timed set | Day 7 light review only |
| 14 days | Day 12 | Optional Day 13 sections | Day 14 light review |
| 30 days | Day 26 | Day 29 | Day 30 light review |
| 60 days | Around Day 48 | Around Day 55 | Final 2 days light review |
| 90 days | Around Day 77 | Around Day 81 | Final 2 days light review |
How to review a mock
For each missed or guessed question:
- Identify the topic.
- Identify the tested decision: definition, selection, troubleshooting, comparison, or process order.
- Write the rule you should have used.
- Re-answer without looking at choices.
- Add it to your retest list.
- Retest the topic within 48-72 hours.
Do not judge a mock only by the score. Also review:
- Questions changed from correct to incorrect
- Questions answered correctly by guessing
- Slow questions that consumed too much time
- Repeated misses in the same topic
- Trouble with scenario wording
PBQ-style preparation
CompTIA exams may include performance-based question formats. Prepare for task-style thinking, not memorized wording.
Practice tasks such as:
- Matching connectors, cables, devices, or ports to scenarios
- Ordering troubleshooting steps
- Selecting appropriate hardware for a user requirement
- Interpreting a simple network diagram
- Choosing SOHO network components
- Matching printer symptoms to probable causes
- Identifying mobile device configuration choices
- Comparing virtualization or cloud service models
When practicing PBQ-style items, first ask: What outcome is the task asking me to produce? Then eliminate options that do not fit the environment or symptom.
Weekly review template
Use this at the end of each week in the 30-day, 60-day, or 90-day plan.
| Question | Your answer |
|---|---|
| Which three topics caused the most missed questions? | |
| Which topic improved the most? | |
| Which errors were wording mistakes instead of knowledge gaps? | |
| Which hands-on items did I review? | |
| Which topics need retesting in 48-72 hours? | |
| Am I improving under timing, or only untimed? |
Final-week rules
During the final week, shift from learning mode to scoring mode.
Keep doing
- Mixed question sets
- Missed-question review
- Troubleshooting scenarios
- Port/protocol recall
- Connector and hardware identification
- Light PBQ-style tasks
- Timed sections if pacing is weak
Stop doing
- Starting a new full course
- Rewriting all notes
- Watching long videos passively
- Taking multiple full mocks in one day
- Studying only your strongest topics
- Ignoring guessed-correct questions
- Cramming late the night before the exam
Exam-readiness checks
You are likely ready to schedule or sit for the exam when most of these are true:
| Readiness check | Target condition |
|---|---|
| Objective coverage | You have reviewed every major Core 1 topic at least once |
| Error log | Most repeated misses are closed or improving |
| Troubleshooting | You can identify first step, likely cause, and verification step in scenarios |
| Networking | You can explain common services, ports, wireless concepts, and SOHO components |
| Hardware | You can match components, connectors, printers, storage, and power issues to scenarios |
| Mobile devices | You can answer laptop, connectivity, accessory, and synchronization questions confidently |
| Cloud/virtualization | You can compare models and use cases without relying on buzzwords |
| Timing | You can complete timed sets without rushing the last questions |
| Confidence | You can explain why wrong answers are wrong, not just pick familiar terms |
If you are not ready
If your mock results or error log show major gaps close to exam day, do not keep taking full mocks without repair. Use a two-day reset:
| Session | Action |
|---|---|
| Session 1 | Pick the weakest topic and review only its objectives |
| Session 2 | Do 25-40 targeted questions on that topic |
| Session 3 | Review every miss and create comparison notes |
| Session 4 | Do a mixed timed set to confirm improvement |
Repeat for the next weakest topic.
Practical next step
Choose your timeline, take a diagnostic set, and build today’s session from your top three weak areas. For CompTIA A+ Core 1 (220-1201), the fastest improvement usually comes from combining objective review with targeted practice and careful missed-question analysis.