220-1101 Exam Guide: Decide Whether Core 1 Is Still the Right Booking
CompTIA A+ Core 1, exam 220-1101, was designed to validate practical entry-level skills across hardware, networking, mobile devices, virtualization and cloud computing, and hardware and network troubleshooting. It serves candidates targeting support and junior technician work, but the version matters: CompTIA states that the A+ V14 version containing 220-1101 retired on September 25, 2025. This guide helps you make the important decision first—whether to pursue the current Core 1 instead of 220-1101—then turn the relevant skills into a focused study plan without relying on exam dumps.
Should you schedule 220-1101 now?
Do not assume that a page, practice product, or search result offering 220-1101 means the exam is still available. CompTIA states that the A+ V14 version, which includes 220-1101, retired on September 25, 2025. Check CompTIA’s current A+ certification page before paying, booking, or choosing study material.
The official current Core 1 page identifies a new A+ Core 1 V15. That makes version control the first preparation task. If you have not already scheduled 220-1101, confirm the active exam code and objectives directly with CompTIA. If you have already passed 220-1101, verify how CompTIA records your result and what remains for the two-exam A+ certification through the official certification channel.
The older catalog describes 220-1101 as released in April 2022 and available in English, German, Japanese, Portuguese, Simplified Chinese, and Spanish. Those details describe the retired version and should not be treated as current booking information.
What did Core 1 validate?
220-1101 was the hardware-and-connectivity half of CompTIA A+. Its objective areas covered mobile devices, networking, hardware, virtualization and cloud computing, and hardware and network troubleshooting. The exam was intended to test whether a candidate could work with end-user technology rather than merely recognize isolated technical terms.
CompTIA’s description of the A+ skills includes installing and configuring end-user devices and software, connecting devices to networks, performing basic cybersecurity mitigations, troubleshooting common problems, and demonstrating basic knowledge of scripting, cloud, and virtualization. For Core 1 specifically, the strongest emphasis was on physical equipment, connectivity, and diagnosing device or network faults.
A+ certification requires both Core 1, 220-1101, and Core 2, 220-1102. Passing only the first exam did not by itself award the full A+ certification. Core 2 addressed a different set of operating-system, security, software, and operational topics, so candidates should plan the pair rather than treating Core 1 as the complete certification.
Who was the exam designed for?
The most direct audience was an aspiring IT support professional who needs a broad, vendor-neutral foundation. CompTIA lists roles such as IT Support Specialist, Helpdesk Technician, Field Technician, and Tier I Support Specialist among the top A+ job roles associated with the certification.
This makes 220-1101 a sensible skills reference for people who install workstations, replace components, connect users to local networks, support printers and mobile devices, or investigate why a device cannot communicate. It is also relevant to career changers who need a structured inventory of entry-level support knowledge. A formal prerequisite was not supplied in the verified facts, so do not present prior employment or another certification as a mandatory admission requirement.
CompTIA notes that its certifications mirror current IT job roles and can be pursued whether or not the candidate has job experience. It also cautions that certifications are not a replacement for experience. Use study time to build small, safe practice tasks—such as identifying components, configuring a test network, and tracing a fault—rather than memorizing terminology without understanding its use.
How were the domains weighted?
The 220-1101 blueprint assigned the largest share to Hardware and Network Troubleshooting at 29%, followed by Hardware at 25%, Networking at 20%, Mobile Devices at 15%, and Virtualization and Cloud Computing at 11%. Use these labels with the percentages when allocating study effort; a bare percentage does not tell you what to study.
Hardware and Network Troubleshooting accounted for 29% of the exam domain weighting. This domain should anchor revision because it combines component knowledge with a method for isolating faults. Practice stating the symptom, identifying likely causes, choosing a safe test, interpreting the result, and selecting the next action.
Hardware accounted for 25% of the exam domain weighting. Review components, connectors, installation considerations, storage, memory, displays, power, and common peripheral issues as an interconnected system. Avoid learning a list of parts without linking each part to its installation, compatibility, or failure symptoms.
Networking accounted for 20% of the exam domain weighting. Concentrate on how devices connect, how local networking hardware differs, how addressing and internet connections are configured, and how a support technician distinguishes a device problem from a network-service problem.
Mobile Devices accounted for 15% of the exam domain weighting. Study device components, connectivity, configuration, and common support situations. The practical goal is to reason about a mobile endpoint with constraints that differ from a desktop, including portability and wireless dependence.
Virtualization and Cloud Computing accounted for 11% of the exam domain weighting. Learn the basic concepts and the support implications of hosted resources, virtual machines, and cloud services. Do not let this smaller domain disappear from your plan, but do not allow it to displace troubleshooting practice.
What question formats should you practise?
CompTIA states that A+ exams use multiple-choice questions, drag-and-drop activities, and performance-based items. Preparation should therefore include recognition, ordering or matching, and task-oriented reasoning. A candidate who only reviews definitions may be unprepared for a prompt that asks for the best sequence or the most appropriate fix.
For multiple-choice practice, explain why the selected option is appropriate and why the alternatives are less suitable. This is more useful than recording a letter or memorizing a phrase. When a question describes a symptom, underline the constraints: what changed, what still works, and what the technician is expected to do first.
For drag-and-drop and performance-based preparation, reproduce the logic with ordinary equipment, diagrams, or a virtual lab. Sort connectors by purpose, sketch a simple network, document a troubleshooting flow, or configure a disposable test environment. These activities are recommendations, not descriptions of live exam content, and they should be based on the published objectives rather than recalled questions.
Do not use exam dumps, leaked questions, or unauthorized answer collections. They do not establish that you can perform the underlying work, may be inaccurate or outdated, and cannot guarantee a passing result. Use official objectives and legitimate learning resources to identify gaps, then practise the skill represented by each gap.
How should you allocate study time?
Start with a diagnostic, then weight your effort toward Hardware and Network Troubleshooting and Hardware while protecting time for every domain. A sensible sequence is to establish component and connectivity fundamentals, apply them in troubleshooting scenarios, then close gaps in mobile, cloud, and virtualization topics.
First, obtain the relevant official objectives for the version you intend to take. Mark each objective as unfamiliar, partly understood, or usable in a practical task. This prevents a familiar-sounding topic from receiving too much attention simply because it is easy to recognize.
Next, study Hardware before attempting complex troubleshooting. You need a working mental model of components, connectors, power, storage, memory, displays, and peripherals before a fault scenario becomes meaningful. For every topic, add one practical question: what would I inspect, change, measure, or document if this failed?
Then combine Networking with troubleshooting. Draw the path from an endpoint through local networking hardware to network services and the internet. Practise deciding whether the next check belongs on the device, the cable or wireless link, the local network, the address configuration, or the service path.
Finish with mixed-domain review instead of five isolated quizzes. The real support task often crosses boundaries: a mobile device may have a wireless problem, a desktop fault may be caused by power or storage, and a virtual or cloud resource may change where the technician looks for evidence. Mixed review reveals whether you can choose a diagnostic path rather than recite a domain.
What should a practical lab contain?
A useful Core 1 lab does not need to reproduce an exam screen. It needs to let you identify hardware, configure connections, observe symptoms, and record a repeatable troubleshooting process. Use equipment and software you are authorized to handle, and avoid experiments that could damage production systems or expose personal data.
For hardware, work with a computer that can be safely opened or use labelled components and diagrams if physical access is limited. Identify connectors and system devices, practise careful installation reasoning, and relate each component to likely symptoms. Keep a parts-and-symptoms log in your own words.
For networking, create a small test arrangement with an endpoint, local networking hardware, and a controlled internet or isolated environment. Practise checking physical connectivity, addressing, and service reachability in sequence. Change one variable at a time and write down the expected result before testing it.
For mobile devices, use a device or simulator that contains no sensitive information. Work through wireless connection, peripheral, account, and configuration scenarios without changing another person’s settings. For cloud and virtualization, use a permitted learning environment and focus on the difference between a local device issue and a resource delivered from elsewhere.
If you want guided practice, the catalog identifies CertMaster Labs for A+ Core 1 and Core 2 as a remote, browser-based lab environment using real equipment and software. That is an official resource description, not a claim that a lab is required. Choose a lab when your weakness is procedural and reading alone has not made the steps clear.
What is a workable study roadmap?
Use a four-stage roadmap: verify the exam version, map the objectives, build the core knowledge, and test your troubleshooting decisions. The stages can be compressed or extended around your schedule; the important point is to measure readiness by objective coverage and practical explanation, not by the number of pages or practice questions completed.
Stage one is administrative. Confirm whether you need the retired 220-1101 knowledge for an existing record or whether you should move to the current Core 1 V15. Check the current CompTIA page, exam code, objectives, language information, and scheduling route. Do this before buying a course labelled only “A+ Core 1.”
Stage two is the baseline. Create a domain checklist and take an honest diagnostic from a legitimate study source. For each missed item, record the concept, the reason for the error, and a corrective task. “I guessed” and “I confused two similar connectors” require different remedies.
Stage three is structured learning. Work through Hardware and Networking first, linking each concept to installation or connectivity. Add Mobile Devices, then Virtualization and Cloud Computing. Return repeatedly to Hardware and Network Troubleshooting, where the 29% domain weighting makes broad integration especially important. This ordering is a practical recommendation based on the blueprint, not an official required sequence.
Stage four is application and review. Perform short lab tasks, explain a troubleshooting path aloud or in writing, and complete mixed practice without consulting notes. Revisit only the objectives that remain weak. Schedule only after you can explain the relevant concepts, choose a defensible first action, and distinguish a safe diagnostic step from an unnecessary replacement.
A first study session
Confirm the version, download or review the official objectives, and make five labelled columns for the exam domains. Under each objective, write one sentence describing the technician’s task. This turns a broad blueprint into a list of observable abilities and immediately exposes topics that you cannot yet describe.
The middle of preparation
Alternate knowledge review with lab work. After studying a component or network concept, perform a related identification or configuration task. After a lab fault, return to the objective that explains the symptom. This two-way link reduces the risk of passing a quiz while remaining unable to perform the underlying support action.
The final review
Use a short error log rather than restarting every book. Group errors into terminology, configuration, sequencing, and troubleshooting judgment. Your last revision should target recurring categories and include mixed scenarios across the five labelled domains. Do not spend the final phase trying to memorize recalled exam questions.
Which official resources are worth checking?
Use CompTIA’s current certification and Core 1 pages for version status, objectives, and current certification information, then use the scheduling page only after you have confirmed the active exam. CompTIA’s A+ exam article is useful for the published question-format overview. These sources should control version-sensitive decisions.
The catalog describes Official CompTIA Instructor and Student Guides for A+ Core 1 and for the combined Core 1 and Core 2 path. It also describes official CertMaster Labs and CertMaster Practice. A guide supports structured coverage, a lab supports procedural practice, and an assessment tool helps identify remediation needs; select according to the gap you have measured.
A third-party course can be useful for explanation, but compare its module names and version code with the official objectives before relying on it. Be especially careful with material that still presents 220-1101 as an actively schedulable exam after CompTIA’s stated retirement date. Old material can explain concepts, but it should not decide your booking.
CompTIA identifies A+ as accredited by ANSI for compliance with ISO 17024 and approved by the U.S. Department of Defense under Directive 8140/8570.01-M in the catalog. Those are credential facts, not substitutes for checking whether the particular exam code is current.
How do delivery and scheduling work?
For A+ exams, CompTIA states that candidates can schedule in-person delivery at a Pearson VUE test center or online through OnVUE. Because delivery availability, identity requirements, technical checks, and appointment details can change, use CompTIA’s scheduling page and the instructions shown during the current booking process.
Do not book from a cached page or a reseller description that omits the exam version. Confirm the code displayed at checkout, the applicable language, and the delivery option before finalizing. The older 220-1101 catalog listed six languages, but that historical list should not be assumed to apply to a current Core 1 exam.
A practical scheduling rule is to choose a date only after your objective checklist has no major unknowns and your practice has shown repeatable reasoning across all five domains. If your preparation depends on memorizing answers or you cannot explain why a troubleshooting step comes first, postpone the booking and repair that weakness.
Which mistakes waste the most preparation time?
The most expensive mistake is preparing for the wrong version. The second is treating Core 1 as the whole A+ certification. Other common failures include studying hardware as isolated trivia, neglecting troubleshooting, ignoring hands-on tasks, and interpreting practice-question familiarity as proof of readiness.
Mistake one: buying a 220-1101 resource without checking status. Fix it by confirming the active code on CompTIA’s current site and matching every major resource to that code.
Mistake two: studying by percentage alone. The 29% Hardware and Network Troubleshooting domain is important, but the 15% Mobile Devices domain, the 11% Virtualization and Cloud Computing domain, and the other labelled domains still represent required coverage. Use the weights to allocate attention, not to eliminate topics.
Mistake three: memorizing port, connector, or component labels without context. Fix it with a symptom-and-action table: identify the observed issue, list plausible causes, name the safest first check, and state what result would change your next step.
Mistake four: taking repeated practice tests without reviewing errors. A score or completion mark has little value if you cannot say what concept produced the error. Keep an error log and retest the concept in a different form, preferably with a lab or explanation task.
Mistake five: overlooking Core 2 planning. Passing Core 1 does not complete A+. Review the current relationship between the two exams before committing to a study calendar, especially if you are working toward the full certification rather than a single exam objective.
What should you do next?
Your next action should be a version check, not another question bank. Open CompTIA’s current A+ page, confirm whether you need a historical 220-1101 record or the current Core 1 exam, and then select objectives and study material that match that decision.
If 220-1101 is relevant because you already took or passed it, document your status and check CompTIA’s official certification record guidance. If you have not booked it, treat the retirement statement as a reason to investigate the current replacement rather than assuming a late appointment is possible.
After the version decision, create the five-domain checklist, perform a diagnostic, and schedule lab work for the weakest procedural areas. Prioritize Hardware and Network Troubleshooting and Hardware, while giving deliberate review to Networking, Mobile Devices, and Virtualization and Cloud Computing.
Finally, plan Core 2 if your goal is the full A+ certification. Keep the two exam codes, their objectives, and your evidence of readiness separate. That simple separation prevents a common planning error: finishing a Core 1 study plan and mistaking it for completion of the A+ credential.
Conclusion
220-1101 remains useful as a description of the A+ V14 Core 1 skill set, but CompTIA’s stated retirement of that version changes the candidate’s immediate decision. Verify the current exam before spending money or selecting a date. Then prepare through objective-led study, labelled domain coverage, safe lab practice, and troubleshooting explanations—not dumps. That approach supports both an informed scheduling choice and the practical foundation the A+ pathway is intended to develop.
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
