Baseline and hardware inventory
Take a short diagnostic. Review CPUs, RAM, storage, ports, cabling, printers, mobile devices, and workstation components. Build a quick-reference sheet for connectors and common specs.
The cleanest A+ path is not to treat Core 1 and Core 2 as trivia lists. Build a support workflow: identify symptoms, isolate likely causes, choose the least disruptive fix, and document what changed.
The 10-week plan
Pass Core 1 first, then keep the troubleshooting rhythm for Core 2
Networking and hardware troubleshooting
Study IP basics, Wi-Fi standards, SOHO equipment, network services, and hardware failure patterns. Practice explaining the next best troubleshooting step, not just the final answer.
Virtualization, cloud, and Core 1 review
Cover virtualization, cloud models, client-side cloud work, and mixed troubleshooting. Take a Core 1 practice exam and convert misses into a two-page repair list.
Core 1 final practice
Run timed Core 1 sets and PBQ-style scenarios. Sit Core 1 when practice scores are steady and your misses are mostly wording or pace, not whole domains.
Operating systems and software
Study Windows editions and tools, macOS and Linux basics, command-line utilities, application install and repair, and OS troubleshooting. Use a home lab or VM for commands where possible.
Security and operations
Work through account security, malware handling, wireless security, backups, change management, documentation, scripting basics, safety, and professionalism.
Core 2 practice and repair
Take a Core 2 practice exam. Separate misses into OS commands, security decisions, operational procedure, and software troubleshooting. Redo the worst topics after a delay.
Final Core 2 review
Run mixed timed blocks, PBQ-style practice, and command review. Keep troubleshooting steps and least-privilege security decisions fresh in the final 48 hours.
Study strategy
Make every topic operational
Hardware and networking
Do not only define parts. Practice what symptoms they cause, what tool verifies the issue, and what replacement or configuration step comes next.
Operating systems
Hands-on commands stick faster than reading lists. Use Windows tools, basic Linux commands, and common repair flows until they feel familiar.
Security and procedures
Expect questions where the technically possible answer is not the best professional answer. Least privilege, documentation, safety, and escalation matter.
Simple weekly cadence: three content blocks, two lab or troubleshooting blocks, one timed set, and one review block for missed questions.
Make it adaptive
Turn your A+ timeline into a schedule
Use the free planner to map Core 1, Core 2, weekly hours, and weak domains into a day-by-day study plan.
Sources