220-1101
CompTIA A+ Certification Exam: Core 1
CompTIA A+ Core 1 220-1101 Exam Guide
CompTIA A+ Core 1, exam 220-1101, validated entry-level technical skills across hardware, mobile devices, networking, virtualization, cloud concepts, and troubleshooting. It served candidates preparing for support, help desk, field technician, and similar roles, but the A+ V14 version that included 220-1101 retired on September 25, 2025. This guide helps you decide whether to study its objectives for legacy context or move directly to the current Core 1 version before booking an exam.
Should you still prepare for 220-1101?
The practical answer is to verify your exam code before spending time or money. CompTIA states that the A+ V14 version containing 220-1101 retired on September 25, 2025. Candidates seeking a current A+ credential should use the current Core 1 information on CompTIA’s official certification pages rather than treating this retired exam as available for new scheduling.
The 220-1101 objectives remain useful as a study reference when an employer, school, or existing training course specifically names A+ Core 1 V14. They describe a broad support foundation: identifying components, connecting devices, establishing basic network access, understanding cloud and virtualization concepts, and troubleshooting common hardware and network faults.
Do not assume that a course labelled “A+ Core 1” automatically prepares you for the current exam. Check the exam identifier, version, objective document, and language information together. Version names are not interchangeable, and an old practice bank can leave gaps even when its general IT topics still sound familiar.
What credential does Core 1 contribute to?
Passing 220-1101 alone did not award the complete CompTIA A+ certification. CompTIA required candidates to pass both Core 1, 220-1101, and Core 2, 220-1102. Core 1 concentrated on technical infrastructure and device support, while the two-exam structure assessed a wider entry-level support profile.
The official A+ materials describe the combined certification as validating the ability to install and configure end-user devices and software, connect devices to networks, perform basic cybersecurity mitigations, troubleshoot common problems, and demonstrate basic knowledge of scripting, cloud, and virtualization.
This distinction changes your study plan. If your goal is the A+ certification rather than a single exam result, reserve time for Core 2 topics as well. Core 2 materials cover areas such as operating systems, security, software troubleshooting, operational procedures, and support tools. Passing Core 1 is a milestone, not the finish line.
Who was 220-1101 designed to serve?
220-1101 was aimed at people building a foundation for hands-on IT support. CompTIA’s catalogue associates A+ with roles including IT support specialist, helpdesk technician, field technician, and Tier I support specialist. The exam’s vendor-neutral approach is suited to candidates who need to reason across different device manufacturers rather than administer one proprietary platform.
You did not need to present a specific prerequisite to sit the exam in the supplied official information. That does not mean every candidate begins at the same point. Someone who has assembled computers, configured a home router, or supported users may need less introductory practice than someone encountering hardware and networking for the first time.
Use your intended job tasks as the readiness test. If you can explain why a device fails, identify the next diagnostic step, and choose a safe corrective action, you are studying the right kind of capability. If you are only memorizing component names or port abbreviations, your preparation is incomplete.
Which skills and domains did the exam measure?
The exam covered five domains: Mobile Devices, Networking, Hardware, Virtualization and Cloud Computing, and Hardware and Network Troubleshooting. The official outline presents these as connected support responsibilities rather than isolated trivia; a technician may need to identify a component, establish connectivity, and then diagnose a fault in the same service request.
The 220-1101 domain weights were Mobile Devices 15%, Networking 20%, Hardware 25%, Virtualization and Cloud Computing 11%, and Hardware and Network Troubleshooting 29%. Hardware and Network Troubleshooting therefore had the largest official share, while Virtualization and Cloud Computing had the smallest; both percentages should be read with their domain labels, not as standalone targets.
Use the weights to allocate attention, not to ignore a domain. A smaller domain can still expose a knowledge gap, and troubleshooting questions often depend on knowledge from hardware or networking. A sensible order is to learn the underlying technologies first, then practise selecting the most likely cause and the best next action.
Mobile Devices: support the user’s endpoint
Mobile Devices required more than recognizing a phone or tablet. Your study should connect device components, displays, batteries, wireless connectivity, accessories, and mobile operating-system behaviour to practical support decisions. Focus on symptoms, likely causes, and the least disruptive fix.
Practise scenarios involving a device that cannot connect, will not charge, has a damaged display, or does not recognize an accessory. For each scenario, write down what you would verify first, what evidence would confirm the cause, and when replacement is more appropriate than repair.
Avoid studying mobile technology as a list of model-specific features. The exam was vendor-neutral, so the transferable skill is structured diagnosis across common mobile-device configurations.
Networking: establish and verify connectivity
Networking topics supported the technician’s role in connecting end-user devices to local and internet resources. Study addressing concepts, wired and wireless connections, networking hardware, common services, and the relationship between a device configuration and the network path it must use.
Build a small troubleshooting sequence: check the physical or wireless link, inspect the device configuration, test local reachability, test name resolution or service access, and compare the result with a known-good device. The purpose is not to memorize a ritual but to avoid changing settings before identifying where connectivity fails.
Learn the difference between a symptom and a cause. “The internet is down” may describe a wireless association problem, an addressing problem, a local equipment fault, or an upstream service issue. Your notes should map each observation to the next discriminating test.
Hardware: identify the right component and constraint
Hardware covered the components and peripherals a support technician installs, configures, and maintains. Study how processors, memory, storage, power, motherboards, expansion, displays, input devices, printers, and connectors fit together, including compatibility and installation constraints.
Use labelled equipment or diagrams where possible. Trace a complete installation: confirm the part and interface, check physical fit and power requirements, install it safely, configure it, and verify operation. This sequence is more useful than isolated flashcards because it links identification to a technician’s actual decision.
Common mistakes include confusing a connector’s physical appearance with its function, ignoring power or compatibility limits, and treating a failed peripheral as proof that the peripheral itself is defective. Always include the cable, port, driver or configuration, and known-good comparison in your reasoning.
Virtualization and Cloud Computing: understand the support model
This domain introduced concepts a support technician may encounter even when the underlying infrastructure is managed elsewhere. Study the distinction between local physical resources, virtual machines, hosted services, and cloud-based delivery, together with basic terminology about access, scalability, and responsibility.
The useful question is “where does this function run, and who controls it?” A problem may belong to the endpoint, a local hypervisor, a virtual guest, a network connection, or a provider-managed service. Draw simple diagrams showing the user device, network, host, guest, and service boundary.
Do not let cloud vocabulary replace troubleshooting fundamentals. A cloud service still depends on working credentials, connectivity, client software, and an available service. Practise identifying which layer you can test locally and which issue must be escalated.
Hardware and Network Troubleshooting: turn symptoms into actions
Troubleshooting was the highest-weighted 220-1101 domain at 29%, so it deserved the largest share of practical revision. The target skill was not merely naming a fault; it was applying a repeatable process to isolate the cause, choose an appropriate fix, and confirm that the result solved the original problem.
For each lab or practice scenario, record five items: the reported symptom, the facts you can verify, the most probable cause, the next test, and the validation step. Add a note explaining why two tempting alternatives are less likely. This forces you to compare evidence instead of selecting a familiar term.
Revisit scenarios after a delay. If you can solve a problem only when the answer choices remind you of the method, you have recognition rather than working knowledge. Try describing the diagnostic path aloud without seeing the options, then perform the relevant configuration or replacement in a controlled environment.
How should you sequence your preparation?
Start with the blueprint and an honest baseline, then move from concepts to guided practice, troubleshooting, and timed review. Do not begin with random question sets. A diagnostic attempt should reveal which domains and task types need work; it should not become a substitute for reading the objectives.
First, download or review the official objectives associated with the exact version you are studying. Mark each item as confident, partly familiar, or unknown. Next, study hardware and networking fundamentals before troubleshooting. Then add mobile, cloud, and virtualization topics, using practical exercises to connect terminology with observable outcomes.
After the first learning pass, use mixed-domain exercises. Real support work does not announce that a problem belongs to Networking or Hardware. Mixed practice reveals whether you can select the relevant domain from a symptom, while domain-specific review remains useful for repairing a clear weakness.
Finish with a readiness review based on explanations and procedures, not a memorized percentage from an unofficial practice site. You should be able to justify an answer, perform the underlying task where feasible, and explain why an alternative action would be premature or unsafe.
A four-phase study plan
A flexible four-phase plan works better than an arbitrary calendar. Give each phase enough time for your background: baseline and scope, foundations, applied troubleshooting, and final verification. The official domain weights should influence the amount of practice, while your diagnostic results should determine where the plan needs adjustment.
Phase one is scope control. Confirm whether you are studying legacy 220-1101 or the current Core 1 exam, collect the matching objectives, and take a short diagnostic. Create an error log with the objective, your answer, the correct reasoning, and the cue you missed.
Phase two is foundation building. Study hardware and networking in linked blocks. For example, pair a network adapter with connectivity checks, storage with installation and failure symptoms, and power with no-start or intermittent-operation diagnosis. Add mobile and cloud concepts after you can explain the core endpoint and network relationships.
Phase three is applied work. Use labs, spare equipment, simulations, or documented diagrams to install, configure, inspect, and troubleshoot. Recreate faults only in equipment you own or are authorized to manage. Record the change and its rollback so that practice reinforces safe operational habits.
Phase four is verification. Mix domains, review the error log, and explain procedures without notes. Schedule only after you have confirmed the exact exam version and have a realistic plan for the second A+ Core exam if full certification is your objective.
How to use labs without wasting study time
A lab is valuable when it produces an observable result and a reasoned diagnosis. CompTIA’s catalogue describes CertMaster Labs for A+ Core 1 and Core 2 as remote, browser-based practice using real equipment and software. Whatever lab you choose, connect each exercise to an objective and document what changed.
Use a repeatable lab record: starting state, task, command or setting used, expected result, actual result, diagnosis, correction, and verification. This format exposes weak points such as changing several variables at once or failing to test after a repair.
If you lack physical equipment, use diagrams, operating-system tools, a virtual environment, or a controlled home network where appropriate. Do not claim that a simulated result proves behaviour on every device. The objective is to practise structured decisions, not to imitate an employer’s entire environment.
Prioritize exercises that combine skills. Configure a device, connect it, introduce one controlled fault, and trace the failure. Then repeat with a different symptom. This is more demanding—and more useful—than clicking through a sequence whose outcome is already obvious.
What question formats and delivery options were evidenced?
CompTIA states that A+ exams use multiple-choice questions, drag-and-drop activities, and performance-based items. The official exam article also states that each A+ exam, including 220-1101, had no more than 90 questions. Because 220-1101 retired, confirm the current exam’s format and limits before relying on these legacy details for scheduling.
CompTIA’s scheduling page states that A+ exams can be scheduled for in-person delivery at a Pearson VUE test center or online through OnVUE. Availability, appointment conditions, identification rules, and technical requirements can change, so use the official scheduling process for the current exam rather than relying on a third-party summary.
Prepare for performance-based thinking even when most of your revision uses written questions. Practise ordering steps, matching a symptom to a tool or setting, identifying a component from a diagram, and configuring a connection. These activities test whether you can apply knowledge, not just recognize a definition.
Do not build a plan around recalled questions, exam dumps, or leaked material. They are not a reliable way to establish competence, may describe a retired version, and do not replace authorized objectives or hands-on practice.
How can you manage the booking decision?
Confirm the code, version, language, and delivery route immediately before booking. The catalogue listed 220-1101 in English, German, Japanese, Portuguese, Simplified Chinese, and Spanish, while the current CompTIA page identifies a newer Core 1 version. Treat catalogue language information as historical for 220-1101 and check the current official page for what can actually be scheduled.
If an employer or training provider gave you a 220-1101 voucher or course, ask which exam version it supports before redeeming it. A voucher, classroom seat, or practice subscription should not be assumed to transfer across versions. Resolve that administrative question first, then align study materials to the confirmed code.
Use CompTIA’s official scheduling page for appointment decisions. The supplied evidence confirms the test-center and OnVUE routes for A+ exams, but it does not establish a universal appointment date, regional availability, current price, or current exam duration for the retired 220-1101.
If your objective is the full A+ credential, check your plan for both Core 1 and Core 2. Booking one exam without considering the other can create an avoidable gap in preparation, especially when your training provider teaches the combined certification.
Which mistakes most often weaken preparation?
The most damaging mistake is studying the wrong version. The next is treating memorization as troubleshooting ability. Correct these by checking the official exam code, maintaining an error log, and requiring yourself to explain the evidence behind every answer before moving on.
Mistake one: using a combined A+ course without separating Core 1 and Core 2 objectives. Label notes by exam and domain so operating-system or security material does not crowd out the Core 1 hardware and networking work you still need.
Mistake two: allocating time evenly across domains. The official 220-1101 weights were Hardware 25%, Networking 20%, Mobile Devices 15%, Virtualization and Cloud Computing 11%, and Hardware and Network Troubleshooting 29%. Use those labelled weights as a starting point, then increase time where your diagnostic shows weakness.
Mistake three: learning acronyms without relationships. Turn each term into a comparison, a use case, or a troubleshooting clue. Ask what the technology connects, what configuration it requires, what failure looks like, and which test separates it from a similar cause.
Mistake four: changing multiple settings at once. That can make a problem appear solved while leaving you unable to identify the cause. Change one relevant variable, test the result, and record the outcome.
Mistake five: ignoring the escalation boundary. A support technician must know when a problem is outside the endpoint, network segment, permissions, or service responsibility they control. Practise stating what you can prove and what evidence an escalation should include.
Mistake six: booking from a search result rather than the official page. Version retirement makes this especially risky. Verify the identifier on CompTIA’s certification and scheduling pages before treating any appointment or study product as relevant.
What should you do after passing or changing versions?
Passing 220-1101 did not by itself complete A+, so the next credential decision was Core 2, 220-1102. If you are changing to the current Core 1 version, preserve useful foundations but rebuild your study checklist from the current objectives rather than assuming every topic, emphasis, or task is unchanged.
CompTIA states that A+ certifications are valid for three years from the date earned and can be renewed through its continuing education program. The supplied evidence also states that A+ requires continuing education and is accredited by ANSI for compliance with ISO 17024. Confirm the current renewal rules directly with CompTIA when planning beyond the exam.
Treat the certification as evidence of a foundation, not a replacement for work experience. CompTIA’s catalogue explicitly notes that certifications are a good place to start but are not a replacement for experience. Turn study into usable evidence by keeping lab notes, practising user-focused explanations, and seeking supervised support tasks.
If the exam code on your record, course, or voucher is unclear, pause and contact the relevant provider or CompTIA before making another purchase. Administrative confirmation is a faster next action than completing a course that cannot lead to the exam you intend to take.
A final readiness check for the candidate
You are ready to make a booking decision when you can identify the exact current exam, explain the five legacy 220-1101 domains or the matching current domains, and demonstrate a troubleshooting process without depending on answer memorization. You should also know whether your target is Core 1 alone or the complete two-exam A+ certification.
Use this checklist before scheduling: confirm the exam version on CompTIA’s site; obtain the matching objectives; review your weakest labelled domains; complete practical exercises; explain why each diagnostic step comes next; verify the delivery route and language; and plan Core 2 if full A+ is required.
For candidates using 220-1101 material only as background, stop treating the old blueprint as a booking target. Transfer the fundamentals—component identification, connectivity, device support, cloud concepts, and systematic diagnosis—to the current objectives, then remove any topic that the current outline does not require and add any newly specified skill.
Your next action should be specific: open the official A+ Core 1 page, compare its exam identifier with your course or voucher, and create a version-matched study list. That single check prevents the most expensive preparation error in this guide.
Conclusion
220-1101 is now a legacy A+ Core 1 exam rather than a safe default for new scheduling. Its blueprint still provides a useful model of entry-level support skills, especially hardware, networking, device support, and structured troubleshooting, but candidates should verify the current CompTIA version before preparing or booking. Study from official objectives, practise the decisions behind the answers, and remember that complete A+ certification requires both Core 1 and Core 2.
Related exams
- 220-1102 exam — CompTIA A+ Certification Core 2 Exam
- 220-1201 exam — CompTIA A+ Certification Exam: Core 1
- 220-1202 exam — CompTIA A+ Certification Exam: Core 2