220-1101
CompTIA A+ Certification Exam: Core 1
CompTIA 220-1101 Exam Guide: Core 1 Scope, Study Plan, and Scheduling Decisions
CompTIA 220-1101 was the A+ Core 1 exam in the A+ V14 series, validating practical entry-level skills across hardware, networking, mobile devices, virtualization, cloud computing, and troubleshooting. It served candidates preparing for technical support, help desk, field service, and related roles, but the version has since retired. This guide helps you decide whether you need to study the legacy objectives, move to the current Core 1 exam, or schedule the second A+ exam after confirming your certification pathway with CompTIA.
What 220-1101 was designed to validate
220-1101 assessed whether a candidate could support common end-user technology rather than merely recognize IT terminology. Its official skill coverage included 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 computing, and virtualization. These capabilities align with the practical work performed in entry-level support environments.
The exam belonged to the CompTIA A+ certification pathway, but passing 220-1101 alone did not award the full A+ certification. CompTIA required candidates to pass both Core 1 (220-1101) and Core 2 (220-1102). Therefore, treat Core 1 as one assessment in a two-exam plan, not as a standalone certification milestone.
The catalog positioned A+ around roles such as IT Support Specialist, Helpdesk Technician, Field Technician, and Tier I Support Specialist. That makes the exam relevant to people entering technical support, changing from a non-technical role, or formalizing practical computer experience. It is less suitable as a deep specialist exam for candidates whose immediate target is advanced networking, cybersecurity, server administration, or cloud engineering.
Should you prepare for 220-1101 or the current Core 1?
The first scheduling decision is version verification: CompTIA stated that the A+ V14 version containing 220-1101 retired on September 25, 2025, while its current site identifies a newer Core 1 V15. Do not purchase a preparation product or book based only on the 220-1101 code. Confirm the active exam code and objectives on CompTIA’s current A+ pages before booking. Official reference: https://www.comptia.org/en/certifications/a/
If you already studied 220-1101, the work is still useful as a foundation in hardware, networking, mobile devices, cloud, and troubleshooting. However, it should not be treated as proof that you are ready for a different exam version. Compare your notes, labs, and practice results with the active objectives, then identify topics that changed or were reorganized.
If an employer, school, or government program specifically names 220-1101, ask the program owner how it handles a retired exam. That administrative check is more important than trying to schedule an unavailable code. The official catalog identified the legacy exam as released in April 2022 and available in English, German, Japanese, Portuguese, Simplified Chinese, and Spanish; those details describe that version and should not be assumed to describe the current exam.
Which domains carried the most examination weight?
For the legacy 220-1101 blueprint, Hardware and Network Troubleshooting carried 29%, Hardware carried 25%, Networking carried 20%, Mobile Devices carried 15%, and Virtualization and Cloud Computing carried 11%. Use the domain labels with the percentages when prioritizing study; a bare percentage is not meaningful because each figure belongs to a specific official domain.
Hardware and Network Troubleshooting was the largest domain at 29%, so a study plan focused only on component identification would leave a major gap. Hardware at 25% was the next largest domain and supplied the platform knowledge needed to diagnose many failures. Networking at 20% also deserved deliberate practice because connectivity problems often require reasoning across devices, addressing, wireless, and services.
Mobile Devices at 15% and Virtualization and Cloud Computing at 11% were smaller portions of the blueprint, not optional topics. A candidate can lose useful coverage by postponing them indefinitely. Study each domain, but allocate extra review time to Hardware and Network Troubleshooting, Hardware, and Networking because those were the three largest named areas.
These weights came from CompTIA’s explanation of the A+ 1101/1102 exams: https://www.comptia.org/en-us/blog/the-new-comptia-a-your-questions-answered/
What knowledge belongs in each domain?
The most productive way to read the objectives is to connect each topic with a support decision. You should be able to identify a technology, explain its purpose, select a reasonable configuration or replacement, and troubleshoot a symptom without jumping immediately to an unsupported conclusion. The domain names below provide the study structure; the troubleshooting mindset links them together.
Hardware
Build a working map of computer components and their relationships. Study motherboards and connectors, system memory, storage, processors, power, cooling, displays, input devices, and common peripheral technologies. Do not memorize isolated connector names only; practice deciding which component or connection is relevant to a stated symptom.
A useful lab sequence is to inspect a desktop or a documented virtual hardware environment, identify components, trace power and data paths, and write down what would change if one part failed. Pair every term with a function and a diagnostic clue. For example, the value of knowing a connector is not the label alone; it is knowing what device it supports and what failure that connection could produce.
Networking
Study the components and configurations that let an end-user device reach a local network or the internet. Include wired and wireless technologies, local networking hardware, addressing concepts, common network services, and remote or small-office connectivity. The objective is practical support, so connect terminology to configuration and fault isolation.
Practice reading a simple network description and asking where the failure occurs: device, cable or wireless link, local network hardware, address configuration, name resolution, gateway, or external service. This sequence is more durable than memorizing a list of ports or standards without understanding the problem each one helps explain.
Mobile Devices
Prepare for support decisions involving smartphones and tablets, including device components, connectivity, accessories, synchronization, and common configuration or troubleshooting issues. Mobile questions can combine hardware and networking, so study them as end-user systems rather than as a separate list of consumer features.
Use a comparison table for mobile connection types, power symptoms, display or input symptoms, storage concerns, and account or synchronization problems. For every entry, record the first safe check, the likely cause, and the escalation point. This creates a concise review tool without relying on leaked or memorized exam questions.
Virtualization and Cloud Computing
Learn the purpose and basic operating ideas of virtualization and cloud services. Focus on what a virtual machine, hosted service, or cloud resource changes for the user and support technician: where the resource runs, how it is accessed, what depends on connectivity, and which layer might be responsible when access fails.
A practical exercise is to compare a locally installed application, a virtualized workload, and a cloud-delivered service. Note the differences in hardware dependency, access path, administration boundary, and likely troubleshooting evidence. This helps prevent the common mistake of treating every remote or virtual problem as a local hardware failure.
Hardware and Network Troubleshooting
Troubleshooting requires a repeatable method: identify the problem, establish a theory, test the theory safely, plan and implement a fix, verify full functionality, and document the result. Apply that method to power, performance, display, printing, storage, wired connectivity, wireless connectivity, and service-access symptoms.
When studying, do not stop after choosing a likely cause. Explain why the symptom supports that cause, what test would distinguish it from a similar cause, and what evidence would confirm the repair. This is especially important because performance-based items and drag-and-drop activities test applied judgment in addition to recognition.
How is the exam delivered and what question formats matter?
CompTIA A+ exams use multiple-choice questions, drag-and-drop activities, and performance-based items. That format means preparation should include both recall and action: identify the correct technology, arrange or select a troubleshooting response, and apply a procedure to a presented scenario. Official overview: https://www.comptia.org/en-us/blog/what-is-on-the-comptia-a-exam/
Each CompTIA A+ exam, including 220-1101, had no more than 90 questions. That is a supported characteristic of the legacy exam, not a promise about another version or a prediction of how many questions you will see. The official materials supplied here do not establish a passing score, so do not use an invented score target when judging readiness.
CompTIA stated that A+ exams could be scheduled for in-person delivery at a Pearson VUE test center or online through OnVUE. Availability, appointment conditions, identification requirements, and technical rules can change, so review the scheduling page before selecting a delivery option: https://www.comptia.org/en-us/resources/schedule-exam/
For preparation, complete practice items in three passes. First answer normally. Next explain why the correct option fits and why the alternatives do not. Finally, classify the item as recall, configuration, sequencing, or troubleshooting. This exposes whether a high result comes from understanding or from recognizing familiar wording.
What study resources and lab work should you choose?
Choose resources that map directly to the official objectives and combine explanation with hands-on work. CompTIA’s catalog describes official A+ instructor and student guides as covering the Core 1 and Core 2 objectives, and it lists CertMaster Labs for A+ Core 1 and Core 2 as browser-based practice using real equipment and software. Official catalog: https://solutions.comptia.org/view/126049/
A sensible resource stack has three layers. Use the objectives or an objective-mapped guide as the checklist, a lab environment or available hardware for procedures, and practice questions for diagnosis of weak areas. A large question bank cannot compensate for never configuring a device, inspecting a connection, or tracing a network symptom.
Lab work does not need to be elaborate to be useful. You can document a computer’s components, configure a basic network connection in a safe environment, compare wired and wireless failure symptoms, inspect mobile settings, and work through virtualization or cloud access scenarios. Record the symptom, evidence, action, result, and lesson after each exercise.
Avoid resources that promise exact live questions, claim that memorization guarantees a pass, or encourage exam dumps. They do not build the judgment represented by performance-based troubleshooting and can leave you unable to handle unfamiliar scenarios. Prefer material that identifies the objective, explains the reasoning, and gives you a procedure to perform.
A practical six-stage study roadmap
A staged plan is more reliable than reading every topic repeatedly. Start with an objective inventory, build the technical foundation, practice procedures, diagnose mixed scenarios, test under realistic constraints, and then close only the remaining gaps. The sequence below is a recommendation, not a CompTIA requirement; adjust it to your background and the active exam version you intend to take.
Stage 1: Verify the target and establish a baseline
Confirm whether your target is the retired 220-1101 or the current Core 1 version. Download or review the applicable official objectives, then mark each topic as familiar, partly understood, or unknown. Take a diagnostic assessment only to locate gaps; do not interpret one score as a complete readiness decision.
Create a single tracking sheet with one row per objective area. Add columns for explanation, hands-on evidence, troubleshooting evidence, and final review status. This prevents broad labels such as “networking is weak” from hiding the specific issue, such as address configuration or wireless troubleshooting.
Stage 2: Build the hardware and networking foundation
Study Hardware first if you are new to IT, then connect it to Networking. Learn the purpose and interaction of components before attempting timed practice. Use diagrams, physical inspection, configuration screens, and short written explanations rather than passive rereading.
At the end of this stage, explain a basic computer build, identify likely causes for common hardware symptoms, describe a device’s path to a network, and distinguish a local connectivity problem from an upstream service problem. If you cannot explain the path, return to the relevant objective instead of simply adding more flashcards.
Stage 3: Add mobile, cloud, and virtualization scenarios
Once the foundation is stable, study Mobile Devices and Virtualization and Cloud Computing through comparisons. Ask what is local, what is remote, what is managed by the user, and what evidence is available. These questions make unfamiliar scenarios easier to analyze.
Use short scenario notes rather than long summaries. For each scenario, write the environment, symptom, first check, likely next check, and safe resolution. Review these notes alongside hardware and networking so that you practice choosing between overlapping explanations.
Stage 4: Make troubleshooting the central activity
Spend dedicated time on Hardware and Network Troubleshooting because it represented 29% of the legacy blueprint and requires the broadest integration of knowledge. Work from symptoms, not topic headings. Mix power, performance, display, storage, printing, wireless, wired, and service-access problems.
After each exercise, explain the rejected alternatives. If a device has no network access, for example, do not jump directly to replacing hardware; check the physical or wireless link, configuration, address information, local equipment, and service path in a logical order. The exact sequence should reflect the evidence presented, not a memorized script.
Stage 5: Use practice results as evidence, not as a syllabus
When practice results reveal a weak area, return to the objective and perform or explain the underlying task. Keep an error log with the missed concept, the misleading clue, the correct reasoning, and the action that would prevent the same mistake. Review recurring categories more often than isolated slips.
Do not spend the final phase repeatedly answering familiar questions. Deliberately vary the order of domains and use mixed scenarios. A candidate who can answer a hardware question in a hardware-only set may still struggle when a networking or configuration clue changes the diagnosis.
Stage 6: Conduct a readiness review and schedule carefully
Schedule only after you have confirmed the active exam code, delivery option, and objective version. Before booking, explain every domain in your own words, complete representative applied exercises, and show that your error log is shrinking for the right reason: better reasoning rather than memorized wording.
Use the official scheduling page for the current appointment process and delivery conditions. Keep preparation resources aligned with the same version you plan to take. If your date changes or the exam version changes, repeat the objective check instead of assuming that an old plan remains valid.
Which mistakes most often waste preparation time?
The most expensive study mistakes are planning errors: preparing for the wrong version, treating Core 1 as the full certification, and confusing recognition with troubleshooting ability. Correct those first. Then replace passive review with objective tracking, lab evidence, and explanations of why a diagnostic choice fits the symptom.
Using retired objectives without checking the exam code
A familiar book can create false confidence if it covers 220-1101 while your appointment is for a newer Core 1. Check the code on the official CompTIA page and on your preparation materials. Retain useful foundation knowledge, but rebuild the study checklist around the active objectives.
Treating domain weights as permission to ignore smaller domains
The legacy blueprint gave Virtualization and Cloud Computing 11% and Mobile Devices 15%, but neither domain was zero. Skipping them creates avoidable blind spots. Cover every domain, then give more practice time to the largest areas and to the topics your baseline shows are weak.
Memorizing connectors, acronyms, or commands in isolation
Lists help with recall, but support work requires selection and diagnosis. For each term, add its purpose, a related symptom, a confirmation step, and a safe corrective action. If you cannot use the term in a short scenario, it is not yet secure knowledge.
Practicing only multiple-choice questions
Because the exam included drag-and-drop and performance-based items as well as multiple-choice questions, use activities that require ordering, matching, configuration, and troubleshooting. Reading an explanation after guessing is not equivalent to performing the underlying task.
Ignoring the second A+ exam
Passing Core 1 was only part of the A+ requirement. Plan Core 2 separately, including its own objectives and preparation needs. Do not describe yourself as A+ certified after passing only 220-1101; verify the certification status after both required exams are complete.
How should you decide whether A+ is the right next credential?
A+ is a reasonable entry point when your goal is broad technical support and you need structured coverage of end-user systems. It is not a substitute for workplace experience or a specialist certification. Choose it when the work you want involves diagnosing user devices, connecting them to networks, and resolving routine technology problems.
Choose A+ first when your target is end-user support
The catalog associates A+ with IT Support Specialist, Helpdesk Technician, Field Technician, and Tier I Support Specialist roles. If your target work centers on desktops, laptops, mobile devices, peripherals, basic connectivity, and first-line troubleshooting, the A+ objectives provide a coherent starting framework.
Consider another pathway when your target is already specialized
If your immediate role requires advanced network deployment, security analysis, Linux administration, server operations, or cloud architecture, A+ may be foundational rather than sufficient. CompTIA’s catalog describes its career pathways as progressive, with certifications building on earlier skills. Use your current experience, certifications, and intended job duties to decide where to enter.
Keep experience in the plan
CompTIA’s catalog notes that certifications are not a replacement for experience and that combining certification with on-the-job work provides both knowledge and practical exposure. Build a small troubleshooting portfolio, volunteer for device support, or use a safe lab alongside exam study. The goal is to turn an objective into a repeatable support capability.
What happens after completing both A+ exams?
After passing both required A+ exams, track the certification’s maintenance requirements rather than treating the credential as permanent. CompTIA states that A+ certifications are valid for three years from the date earned and can be renewed through its continuing education program. Confirm current renewal rules directly with CompTIA because program details can change.
Record your completion and renewal information
Keep your exam records, certification account information, and the date earned in a place you will review periodically. The official A+ certification page and CompTIA’s certification-lifecycle guidance are the appropriate references for current renewal procedures: https://www.comptia.org/en-us/blog/how-long-does-the-comptia-a-certification-last/
Turn exam coverage into job evidence
Use the skills represented by A+ to describe concrete work: diagnosing a hardware fault, restoring connectivity, supporting a mobile device, configuring an end-user system, or documenting a resolution. This is more useful to an employer than repeating a list of exam domains without examples of what you can do.
Your next actions
Start with version control, not memorization. Confirm whether your requirement concerns the retired 220-1101 objectives or the current Core 1 exam, obtain the matching objectives, and create a domain-by-domain baseline. Then combine targeted reading with hands-on tasks, maintain an error log, and schedule only after the exam code and delivery process are verified through CompTIA.
If you are pursuing the legacy A+ pathway, remember that 220-1101 was Core 1, not the complete certification; Core 2 was also required. If you are starting now, use the current CompTIA A+ page as the source of truth and treat older 220-1101 material as background unless an approved program specifically directs you to it.
Conclusion
220-1101 remains useful as a map of foundational support skills, but its retired status changes the preparation decision. Verify the active Core 1 version before buying resources or booking an appointment, then study from the matching objectives and practice diagnosis rather than memorizing isolated facts. Build enough hands-on evidence to explain what you would check, why you would check it, and how you would verify the fix. Finally, plan for both A+ exams and monitor the certification’s renewal requirements after completion.
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