A+ study hours: turn your real week into two exam dates that hold
Plan on 60 to 90 hours per core, or 120 to 180 hours for A+. That is a working assumption built on CompTIA's own figures for its products, not an official number. Split each core's hours by domain weight, divide by your real weekly hours and add roughly one buffer week for every eight weeks. Keep at least a quarter of every week for hands-on work. Run four stages for each core.
"Pass A+ in two weeks" plans are written by experienced technicians. They collapse in the first week for everyone else, and the candidate blames himself. This guide starts from your calendar instead, and it plans both exams, not one.
How many hours does A+ really take?
CompTIA publishes figures for its own products. For each core, its V15 pages list Learn at 25 to 40 hours, Labs at 15 to 25 hours and Practice at 10 to 20 hours. This book therefore uses 60 to 90 hours per core, or 120 to 180 hours for A+, as a working assumption. Move towards the top of the range if IT is new to you.
Nobody can give you your own figure without a diagnostic. Take one practice test per core in your first week, and note which domains feel strange.
How should you split the hours?
Split each core's hours in proportion to its domain weights, then move hours towards your lowest-rated objectives. For a 140-hour plan with 70 hours per core, the starting split looks like this.
| Domain and weight | Hours | Objectives to study first |
|---|---|---|
| Core 1 · Hardware and Network Troubleshooting (28%) | 20 | The troubleshooting method, network and power faults |
| Core 1 · Hardware (25%) | 17 | Motherboards, storage, printers |
| Core 1 · Networking (23%) | 16 | Ports and protocols, SOHO set-up |
| Core 1 · Mobile Devices (13%) | 9 | Laptop parts, mobile connectivity |
| Core 1 · Virtualization and Cloud (11%) | 8 | Hypervisors, cloud models |
| Core 2 · Operating Systems (28%) | 20 | Windows tools and command line, Linux |
| Core 2 · Security (28%) | 20 | Malware removal, Windows security, social engineering |
| Core 2 · Software Troubleshooting (23%) | 16 | Windows and PC security issues |
| Core 2 · Operational Procedures (21%) | 14 | Change management, backups, AI basics |
Which weekly track is yours?
| Track | Hours a week | Best for |
|---|---|---|
| Light | 4 to 6 | A full-time job and family |
| Standard | 7 to 12 | Most working candidates |
| Intensive | 15 to 25 | A career break or a firm deadline |
Pick the track that matches your real weekly time, not your best week.
How do hours become dates?
Divide your total hours by your weekly hours, then add roughly one buffer week for every eight weeks of plan. At 140 hours:
| Track | Weekly hours | Weeks | Buffer weeks | Total |
|---|---|---|---|---|
| Light | 5 | 28 | 4 | 32 weeks |
| Standard | 10 | 14 | 2 | 16 weeks |
| Intensive | 20 | 7 | 1 | 8 weeks |
Place your first exam at the end of the first core's hours, not the end of the whole plan. On the standard track that is about week 7 or 8. Rana, in the book, planned this way and sat Core 2 in week 8 and Core 1 in week 16.
What goes in each stage?
A+ rewards hands-on practice, so labs and questions deserve a large share of your hours. Run these four stages once for each core. For a 70-hour core the hours are shown in brackets.
- Stage A, foundation (about 10 per cent, 7 hours). Rate yourself on every objective, take a diagnostic practice test and set up your lab.
- Stage B, first coverage (about 45 per cent, 31 hours). Work through your course once, with a lab for each domain.
- Stage C, practice (about 30 per cent, 21 hours). Question sets by domain, performance-based practice and a review of every wrong answer.
- Stage D, simulation (about 15 per cent, 11 hours). Full timed practice exams and light revision.
Practice and simulation take almost half of each core. If your schedule slips, cut from Stage B's reading, not from Stage C's hands-on work.
What should your home lab look like?
Build a small lab from what you have: an old desktop or laptop, a spare drive and a home router. Take the computer apart and rebuild it. Install Windows and a Linux distribution in virtual machines. Set up a secure home Wi-Fi network. Practise the troubleshooting method on faults you create on purpose, and write each one in a log.
On the limited-time route, with six hours a week or less, choose one V15 course, one practice-test source and a home lab, and keep at least a quarter of every week for hands-on work.
How will you know you are ready for each core?
Readiness is a pattern, not a single score. Look for consistent results across two or three full practice exams for that core, no domain far behind the others and confidence with performance-based tasks. Book that core when the pattern holds. The cost and booking guide covers vouchers and retakes. Appendix B of CredenTrek For CompTIA A+ has the weekly plan template with a row for each core.
- Choose your core order, track and a total of 140 study hours.
- Divide by your real weekly hours and add buffer weeks.
- Write the dates of Stages A to D for each core into your calendar.
- Gather an old computer, a spare drive and a router for your first lab session this week.
Questions readers ask
Can I pass A+ in a month?
Do I need to buy equipment for the lab?
Should I study both cores at the same time?
What if my practice results are uneven?
- CompTIA A+ certification page
- CompTIA CertMaster Learn, Labs and Practice product pages
- CompTIA A+ 220-1201 and 220-1202 exam objectives
This guide is independent and is not endorsed by CompTIA. Facts change: confirm them on the official page before you act.