How Long to Study for A+ Core 1: A Six- or Ten-Week 220-1201 Plan

How long to study for A+ Core 1: a six- or ten-week 220-1201 study plan across five domains and 27 objectives

How long to study for A+ Core 1 comes down to whether you have worked a support bench. If you have (reseating memory, replacing toner, sorting out a dead network jack), plan six weeks at about 8 hours a week, roughly 50 hours. If you have never opened a computer case, plan ten weeks at the same pace, roughly 80 hours. The extra four weeks are mostly hands-on time.

These are planning figures. CompTIA sets no minimum study time and publishes no pass rate. The nearest thing it does publish is the estimated length of its own Core 1 courses: 25 to 40 hours for CertMaster Learn and 15 to 25 hours for CertMaster Labs. Add the two and you get 40 to 65 hours of course time, before any review or practice.

How long to study for A+ Core 1 if you have worked support?

CompTIA recommends 12 months of hands-on experience in an IT support role before you sit Core 1. The requirements post covers what that recommendation does and does not mean. For planning, what matters is which parts of the exam experience actually shortens.

It shortens the scenario objectives. Of the 27 Core 1 objectives, 13 begin "Given a scenario", and those cover things like installing a power supply, maintaining a laser printer and troubleshooting a drive that has dropped out of an array. If you have done the job, you already know what a failing fuser looks like and which end of a SATA cable goes where. You read those chapters mainly to learn CompTIA's vocabulary for work you already know.

It does not shorten the memorization. Nobody learns that RAID 6 needs four disks or that LDAP sits on port 389 by fixing printers. Bench experience tends to help with hardware far more than with the lookup tables, so the drills below are the same length on both tracks.

What order should you study the domains in?

Follow the objective order, 1.1 through 5.6, which is also the chapter order of our book. The weights are 13% for Mobile Devices, 23% for Networking, 25% for Hardware, 11% for Virtualization and Cloud Computing and 28% for Hardware and Network Troubleshooting. The domains post walks through each one.

Some people want to start with Domain 5 because it carries the most weight. Don't. Every Domain 5 objective is a scenario built on parts you met earlier: a RAM symptom in 5.1 assumes you know the DDR generations from 3.3, and a SOHO connectivity fault in 5.5 assumes the addressing from 2.6. Study the parts first and the hours count twice, because they are also Domain 5 prep.

The plan gives Domain 4 the least time. It has two objectives and 11% of the weight, and most of it is definitions: Type 1 versus Type 2 hypervisors, containers, the cloud deployment and service models. Half a week is enough.

The week-by-week plan

Find your track in the two middle columns. Each row is a block of chapters. The last column is the hands-on and drill work for that block.

Book chapters (objectives) Domain weight With support experience Without Hands-on and drills
1.1 to 1.3: mobile hardware, accessories, connectivity 13% Week 1 Week 1 Pair a Bluetooth device step by step; review location services, account sync and hotspot settings on your phone; start the connector deck
2.1 to 2.2: ports and protocols, wireless 23% Week 1 Week 2 Start the ports deck and the Wi-Fi standards table; find which bands your own router broadcasts
2.3 to 2.8: host services, configuration, network devices, SOHO, connection types, tools 23% Week 2 Weeks 3 to 4 Read the DHCP scope and lease list on your router; work the SOHO drill on paper; make and test a patch cable
3.1 to 3.4: displays, cables, RAM, storage 25% Week 3 Week 5 Open a desktop: identify slots, the DDR notch and drive connectors; start the RAID card set
3.5 to 3.8: motherboards and CPUs, power supplies, printers, printer maintenance 25% Week 4 Weeks 6 to 7 Trace every PSU lead to its connector; print a printer's configuration page and find its IP and driver
4.1 to 4.2: virtualization, cloud 11% Week 4 Week 7 Create a virtual machine in a free Type 2 hypervisor
5.1 to 5.6: troubleshooting hardware, drives, display, mobile, network, printers 28% Week 5 Weeks 8 to 9 Break and fix your own setup: unseated RAM, wrong gateway, a cable pulled from a drive
Timed practice and repair All five Week 6 Week 10 Timed mixed set from held-back questions; reread the chapters behind every miss

On the six-week track, week 1 is the heaviest. If your week is short, move 2.2 into week 2, which carries six chapters but several short comparison ones.

On the ten-week track, Networking gets three weeks and Hardware gets three. That is deliberate. Those two domains hold 48% of the weight between them, and they are where someone without bench time has the most to build.

What hands-on work does the plan include?

Budget about two of your eight weekly hours for hands-on work on the ten-week track, and about one on the six-week track. With experience, the hands-on column is an audit: do each item once and confirm you can name every part in CompTIA's terms. Without experience, it is the core of the plan, and it is why your schedule runs longer.

Opening a PC. Any old desktop will do. Put on a wrist strap or touch bare chassis metal first; the book's first worked drill puts ESD precautions ahead of touching any internal component. Pull and reseat a memory module, and notice the notch that stops DDR4 going into a DDR5 slot. Find the PCIe x16 slot, the SATA ports and the CPU power connector. Then put it back together and check that it boots, because that check is objective 3.5 in miniature.

Cabling. Make one patch cable from bulk Cat 6 to T568B, then test it. Punch one keystone jack down with a punchdown tool. Once you have done both, the tools questions in 2.8 stop being abstract, and you will not confuse the crimper with the punchdown tool again.

Printer. You do not need to own a laser printer. Any office or school printer will print a configuration page showing its IP address, firmware and page count. Find the maintenance kit interval in its settings. Objectives 3.7 and 3.8 cover drivers, connectivity and four printer technologies, and they are much easier to read once you have seen a real one.

Mobile settings. Your own phone is the lab. Pair a headset and note the order of steps: enable Bluetooth, enable pairing, find the device, enter or confirm the PIN, test. CompTIA lists that sequence in objective 1.3, and the book flags it as a likely ordering question. Then look at location services, which accounts sync, and how the hotspot is configured.

Which facts have to be memorized cold?

Four tables carry most of Core 1's pure recall. Give them 10 minutes a day from the week each one first appears, and drill them by writing each table from memory on blank paper, then checking it. Rereading a table only makes it feel familiar. Writing it out shows you which rows you actually know.

Ports. Fourteen rows, from FTP on 20 and 21 to RDP on 3389. Learn the transport for each one along with the number: DNS uses both TCP and UDP, DHCP uses UDP on 67 and 68. Then learn the secure and insecure pairs, such as Telnet on 23 against SSH on 22 and HTTP on 80 against HTTPS on 443. The book calls those pairs the exam's favorite hook.

Connectors. RJ11 against RJ45, F-type, the three fiber connectors, and the USB family alongside Lightning, Molex and DB9. The book singles out SC against LC as the most common fiber mix-up: SC is square, and LC is a small push-pull connector about half its size.

RAID levels. For each level, learn the minimum disks and how many failures it survives. RAID 0: two disks, no fault tolerance. RAID 1: two disks, survives one failure. RAID 5: three disks, survives one. RAID 6: four disks, survives two. RAID 10: four disks, survives one per mirrored pair. Those ten numbers are worth more than any amount of reading about parity.

Wi-Fi standards. Learn the bands. 802.11b and g are 2.4 GHz only, 802.11a and ac are 5 GHz, 802.11n is dual-band, and Wi-Fi 6E is the generation that added 6 GHz. The book says plainly that you will not be asked to recite peak throughput figures.

How do you use the practice banks without spoiling them?

Core 1 gives you 90 minutes for a maximum of 90 questions, so practice at a minute a question. The difficulty post covers what the 675 passing score does and does not tell you.

Our book has 133 practice questions split into five domain banks, one per domain, with the largest banks on Hardware and Troubleshooting and the smallest on Virtualization and Cloud. Use them in two phases.

During the study weeks, after each block, work about two-thirds of that domain's bank untimed and read every explanation, including the ones for questions you got right. From the third block on, time yourself at a minute per question.

For the final week, hold back roughly a third of each bank. That gives you around 45 questions you have never seen, in close to exam proportions, for one 45-minute timed run. Unseen questions are the honest test, because repeats score higher than they should. The practice questions walkthrough shows how to read a Core 1 question before you start the clock.

If you want to see the drills and banks this schedule is built around, the CompTIA A+ Core 1 220-1201 Study Guide numbers its chapters to the objectives, so each row of the table above is a set of chapters you can open directly.

What if you only have three weeks?

Then you are cramming, which can work with support experience. Read every chapter's Exam Tip and Common Pitfall callouts first, then spend your time on the four tables and the worked drill in each scenario objective, with timed sets from week 2. Without hands-on background, three weeks is too short. Push the date back.

When should you book the exam?

Book once you are halfway through: at the end of week 3 on the six-week track, or week 5 on the ten-week track. A fixed date stops the plan from drifting. Aim for a slot two to four days after your timed run, so you still have time to repair your weakest objective. A voucher is valid for 12 months from purchase, so buying early costs you nothing in flexibility. Fees and booking steps are in the exam cost post.

Keep Core 2 in view as well. A+ requires both cores, taken in either order but from the same exam version. The Core 1 vs Core 2 post covers which to take first, and the overview of A+ Core 1 has the rest of the exam facts in one place.

FAQ

Can I study for A+ Core 1 in one month?

Yes, if you have support experience and can manage around 12 hours a week. Use the six-week track, compress the timed-practice week into the last few days, and keep the daily memorization drills. Without hands-on background, a month leaves little time for the labs that the scenario objectives depend on.

How many hours a day should I study for Core 1?

About an hour on weekdays plus a longer weekend session covers the 8 hours a week this plan assumes. The 10-minute table drills work best daily, even on days you skip reading. Short, regular sessions hold the ports and RAID numbers better than one long weekend session.

Do I need to buy hardware to study for A+ Core 1?

Not much. An old desktop, a phone you already own, access to any network printer and a basic cable kit cover the hands-on column. A free Type 2 hypervisor on your current computer covers virtualization.

Should I study Core 1 and Core 2 at the same time?

Most people do better one at a time, because each exam has its own objectives and its own memorization load. CompTIA lets you take them in either order, but both must come from the same exam version. Finish one plan, sit that exam, then start the other.


Planning your Core 1 study? The CompTIA A+ Core 1 220-1201 Study Guide gives each of the 27 objectives its own chapter, with worked drills on the scenario objectives, Exam Tips and Common Pitfalls throughout, and 133 practice questions in five domain banks, every answer explained along with why each wrong option is wrong.

Simply Certified is an independent publisher. A+, CertMaster and CompTIA are trademarks of CompTIA, Inc. Our books are independent study material and are not affiliated with, endorsed by, or sponsored by CompTIA.