220-1102
CompTIA A+ Certification Core 2 Exam
CompTIA 220-1102 Exam Guide: Scope, Version Checks, and a Practical Study Plan
CompTIA A+ Core 2 220-1102 validates foundational ability to configure operating systems and software, apply basic security measures, troubleshoot common problems, and use support, scripting, cloud, and virtualization concepts. It serves candidates pursuing entry-level support roles such as help desk, field technician, and desktop support work. This guide helps you decide whether 220-1102 is the correct exam version, how to sequence study across its four domains, and when your preparation is strong enough to schedule.
Is 220-1102 still the exam you should prepare for?
Check the exam number before buying training, booking a test, or building a study calendar. CompTIA identifies 220-1102 as the Core 2 exam released in April 2022 in the A+ 1100 Core Series, while its current A+ Core 2 page identifies 220-1202 as the Version 15 exam launched March 25, 2025. The old and current versions should not be treated as interchangeable.
The current CompTIA A+ Version 15 requires Core 1 and Core 2 exams from the same version and does not allow mixing versions. Therefore, a candidate taking 220-1102 needs to confirm that the matching 220-1101 path is still appropriate for the candidate’s certification plan. Do not assume that a 220-1102 course, practice product, or exam appointment reflects the current version merely because it contains “A+” in its title.
Use CompTIA’s current certification page and the scheduling process to verify the available exam number before committing to study materials. If your voucher, training enrollment, or previous Core 1 attempt relates to the 1100 series, resolve the version question with CompTIA before scheduling. This single check prevents a common and expensive preparation error.
What does passing 220-1102 contribute to A+ certification?
220-1102 is Core 2 of the two-exam CompTIA A+ certification. Passing it alone does not earn A+; CompTIA states that candidates must pass both Core 1 exam 220-1101 and Core 2 exam 220-1102.
Core 2 assesses the software, operating-system, security, troubleshooting, and support-process side of the A+ foundation. Core 1 and Core 2 together cover the broader technician role, including end-user devices, software, network connections, basic cybersecurity mitigations, common-problem diagnosis, scripting, cloud, and virtualization.
Treat Core 2 as a separate readiness decision rather than as a short final chapter after Core 1. Hardware and networking knowledge from Core 1 can help you understand symptoms and environments, but Core 2 requires its own objective-by-objective review. A candidate who can identify a component but cannot choose a safe software, security, or support action still has a Core 2 gap.
Who is 220-1102 designed to serve?
The exam is most relevant to people preparing for entry-level technical support work, particularly IT support specialist, help desk technician, field technician, Tier I support specialist, desktop support specialist, systems support technician, junior systems administrator, and associate network engineer roles listed in CompTIA’s A+ materials.
CompTIA describes the A+ 1100 Core Series as vendor-neutral, so its purpose is not to certify administration of one manufacturer’s product. That makes the preparation useful for candidates who need to reason across different programs and tools, provided they study the official objectives rather than narrowing their preparation to one familiar operating system or workplace.
The target audience includes career changers, students, junior technicians, and support staff formalizing practical knowledge. A complete beginner can use the exam as a structured foundation, but hands-on familiarity will make the material easier to retain. CompTIA recommends approximately 9 to 12 months of hands-on lab or field experience for candidates preparing for the 220-1101 and 220-1102 exams; this is preparation guidance, not a stated prerequisite for sitting the exam.
Before choosing 220-1102, identify the job task you want to perform. If your immediate goal is user support, prioritize diagnosis, safe changes, documentation, and communication. If you are aiming toward systems administration, use Core 2 as a foundation and plan additional platform-specific learning after confirming the correct A+ version.
Which skills and domains does 220-1102 measure?
The 220-1102 blueprint is organized into four domains: Operating Systems 31%, Security 25%, Software Troubleshooting 22%, and Operational Procedures 22%. Use these labels with the percentages when planning study; the percentages are domain weights, not a guarantee of the number of questions from each topic.
Operating Systems accounts for 31% of the 220-1102 blueprint. The official course outline includes identifying operating-system types and features, supporting Windows, managing Windows 10, managing Windows 11, managing Linux and macOS, supporting mobile devices, supporting print devices, and covering virtualization and cloud concepts.
Security accounts for 25% of the 220-1102 blueprint. Preparation should connect security settings and basic cybersecurity mitigations to ordinary support work: protecting accounts and devices, reducing exposure, and choosing an appropriate response when a security-related symptom appears. Study security as a set of technician actions, not as a list of isolated terms.
Software Troubleshooting accounts for 22% of the 220-1102 blueprint. The official learning description emphasizes diagnosing and resolving common problems. Build the habit of separating symptoms from causes, changing one relevant variable at a time, checking the result, and recording the resolution.
Operational Procedures accounts for 22% of the 220-1102 blueprint. This area links technical work to repeatable support practice. The official course outline calls out using support and scripting tools and implementing operational procedures. Prepare to think about controlled changes, escalation, documentation, and consistent handling of user and device information.
The domain distribution suggests a sensible allocation of effort, but it should not replace objective-level tracking. A topic with a smaller domain weight can still be a personal weakness, and a candidate who memorizes domain names without practicing the associated tasks has not demonstrated readiness.
What should you know about operating systems?
Begin Operating Systems by building a comparison map rather than studying each platform as an unrelated chapter. You need to distinguish operating-system types and features, support Windows, work with Windows 10 and Windows 11, and recognize the support implications of Linux, macOS, mobile devices, printers, cloud, and virtualization.
Create a matrix with rows for task types and columns for the relevant platform or environment. Useful rows include installation or configuration, account and permission handling, updates, connectivity, storage, application behavior, device support, and recovery. Fill the matrix from the official objectives and your lab work; do not rely on a generic checklist that may belong to another exam version.
For Windows topics, practice finding configuration and support information rather than only recalling menu names. A useful session has a symptom, a limited set of possible causes, a chosen diagnostic step, and a written reason for the next action. Compare Windows 10 and Windows 11 only where the objectives or your materials require it, and label notes clearly so old and new interface details do not blur together.
For Linux and macOS, focus on the support concepts and actions named by the objectives. Avoid spending most of your preparation learning advanced administration that is not connected to the exam’s stated outcomes. The same principle applies to mobile devices: learn the support workflow, configuration boundaries, and likely fault categories rather than collecting disconnected product trivia.
Cloud and virtualization deserve a practical explanation. Be able to describe what is being abstracted, where the operating environment runs, and what a support technician can and cannot control. Then connect those concepts to troubleshooting: determine whether the fault belongs to the local device, the software, the network connection, or the hosted environment.
How should you prepare for the security domain?
Security preparation is strongest when every concept leads to a defensive support decision. Study the official security objectives, then ask what a technician should protect, what evidence indicates a problem, which low-risk action is appropriate, and when the issue should be escalated.
Organize notes around account and device protection, configuration choices, common threats, and response procedures. For each item, write a short chain: risk, observable symptom, immediate containment or mitigation, verification, and documentation. This turns recognition into an action plan and helps prevent the mistake of choosing a technically impressive response that is unsafe or disproportionate.
Practice least-disruption thinking. Before changing a user’s system, identify what must be preserved, what authority you have, and how you will confirm that the change worked. Security is not only about selecting a control; it is also about avoiding unnecessary exposure while troubleshooting.
Do not study security by memorizing vendor slogans or isolated abbreviations. Rephrase each objective in plain technician language and test yourself with variations: a home user, a small office device, a managed workplace computer, or a mobile device. The point is to select the appropriate principle when the surrounding details change.
Keep security and operational procedures connected. A support action that solves a problem but leaves credentials, sensitive information, or configuration history exposed is incomplete. Your notes should therefore include both the technical mitigation and the handling or documentation step that makes the work responsible.
How do you build software-troubleshooting skill instead of memorizing fixes?
Use a repeatable troubleshooting loop: define the symptom, gather relevant information, form a likely cause, choose the least risky test, apply one change, verify the result, and document or escalate. This approach matches the practical purpose of Core 2 better than memorizing a long list of one-line fixes.
Construct a fault log during lab work. Record the starting condition, user-visible symptom, tools or settings checked, hypothesis, action, result, and final resolution. When a fix fails, keep the failed attempt and explain why it was reasonable. Reviewing unsuccessful paths teaches you to discriminate between similar symptoms rather than recognizing only the answer you have already seen.
Separate application problems from operating-system problems. A program that will not open may involve installation, permissions, compatibility, corrupted data, or a wider system issue. A slow device may involve software, storage, updates, resources, or an external service. Start with evidence and scope before changing settings.
Use scenario practice only as a way to apply the objectives. Do not rely on exam dumps, leaked questions, or memorized answer keys. They do not establish that you can diagnose an unfamiliar problem, and memorization cannot guarantee a passing result. After answering a practice item, explain why the selected action is appropriate and why the alternatives are less appropriate.
Include a verification step in every exercise. A repair is not complete because a command ran or a setting changed. Confirm the original symptom, check for side effects, and state what you would tell the user or record in the ticket.
What belongs in operational-procedures preparation?
Operational Procedures tests whether technical work is controlled, supportable, and repeatable. Study the procedures attached to the task: identify the request, confirm authorization, protect information, perform the change carefully, validate the outcome, document the work, and escalate when the issue exceeds your scope.
Build a one-page procedure template and use it for every lab. Include the user’s reported problem, affected device or software, evidence collected, action taken, result, remaining risk, and recommended next step. This makes documentation practice part of technical preparation instead of a separate chore saved for the last week.
Include support and scripting tools in your practice, but keep the goal modest and objective-led. You should understand how a tool or script can make a repeatable support task more consistent, what assumptions it makes, and how to verify its output. Never run an unfamiliar script on a production device merely to create an exam example.
Practice escalation decisions. Write down the boundary between what you can safely change, what requires authorization, and what should be referred to a specialist or security process. A candidate who knows a possible fix but cannot explain when not to apply it needs more operational practice.
Review privacy and change-control habits alongside technical notes. The most efficient action is not always the best support action if it risks data, disrupts other users, or cannot be reproduced. Use the operational-procedures objectives to check the quality of your reasoning, not simply your vocabulary.
Which official materials should anchor your study?
Start with the official 220-1102 exam objectives, as CompTIA’s preparation guidance directs candidates to download and study the objectives before training. Use the objectives as a coverage checklist, then choose learning material and labs that explain or demonstrate each item.
The Official CompTIA A+ Core 2 Instructor and Student Guide for 220-1102 is described as covering end-user device and software configuration, network connectivity, basic cybersecurity mitigations, troubleshooting, scripting, cloud, virtualization, and preparation for the Core 2 exam. It is a logical primary reference when you need a version-aligned source.
CompTIA also offered CertMaster Labs for A+ Core 1 and Core 2, using real equipment and software through a remote, browser-based lab environment. If you use a lab product, judge it by whether it lets you perform and verify the objective-related tasks, not by the number of screens or exercises it contains.
Use third-party explanations for clarity, not authority. For every external lesson, map its topic to an objective and check that it is written for 220-1102 rather than 220-1202 or an older A+ release. If a resource gives a different domain structure, exam number, or feature list, stop and resolve the version conflict instead of blending the material.
Create three study documents: an objective checklist, a troubleshooting log, and a missed-question register. The first shows coverage, the second develops practical reasoning, and the third exposes recurring errors. Together they are more useful than repeatedly reading the same chapter without testing recall or application.
What is a realistic 220-1102 study sequence?
A staged plan works better than moving through a book once. First establish the exam version and baseline knowledge; then study the four domains in a deliberate order; finally use mixed review and objective-level remediation before making a scheduling decision.
Stage 1: confirm scope. Verify that 220-1102 is the exam you are expected to take and identify the matching Core 1 requirement. Download the official objectives, mark each item as new, familiar, or demonstrable, and gather only version-aligned materials.
Stage 2: build the operating-system foundation. Start with Operating Systems because it has the largest 220-1102 domain weight at 31% and provides context for software support. Work through the platforms and environments in the objectives, pairing each study block with a configuration or diagnostic exercise.
Stage 3: add security to ordinary support scenarios. Study Security, which represents 25% of the 220-1102 blueprint, while revisiting operating-system settings that affect protection. For each scenario, state the risk, the safe first action, the verification step, and the escalation or documentation requirement.
Stage 4: practice software diagnosis. Work through Software Troubleshooting, weighted at 22% of the 220-1102 blueprint. Use unfamiliar combinations of symptoms and environments. Require yourself to justify a diagnostic step before looking at an answer or reference.
Stage 5: make the work repeatable. Review Operational Procedures, also weighted at 22% of the 220-1102 blueprint, and apply its principles to the exercises from the other domains. Rewrite vague notes as procedures that another technician could follow and audit.
Stage 6: mix the domains. Stop studying in isolated blocks during the final review phase. Combine an operating-system issue with a security concern, or a software symptom with a documentation and escalation decision. Mixed practice reveals whether you can identify the domain behind a scenario.
Stage 7: decide whether to schedule. Use your objective checklist and error register, not a feeling of familiarity. You should be able to explain concepts, perform relevant tasks where a lab is available, choose safe next actions, and correct repeated mistakes without relying on recalled answer patterns.
How can you turn limited lab access into useful practice?
You do not need to wait for a perfect enterprise environment to practice the reasoning Core 2 requires. Use an authorized computer or sandbox, document every change, and focus on controlled tasks that can be reversed. When a real lab is unavailable, use configuration walkthroughs and scenario analysis, but label them as conceptual practice rather than hands-on evidence.
Create small exercises around the official outline: identify operating-system characteristics, compare support approaches, examine software behavior, review a security setting, use a support or scripting tool safely, and write the resulting ticket note. Each exercise should have a starting state and a verification condition.
Use snapshots, test accounts, backups, and isolated environments when the platform permits them. Never deliberately damage a production system, bypass controls, or experiment with another person’s data. The purpose of a lab is to develop disciplined support behavior as well as technical recall.
When using a remote browser-based lab, follow the instructions and record what you actually learned. A lab is most valuable when you predict the result before performing the task, observe the result, and explain any difference. Passive clicking through a guided exercise is weaker than making a hypothesis and checking it.
Turn every lab limitation into a study question. If you cannot access a platform, ask what symptom would distinguish it from another environment, what evidence a technician could collect, and what action would require authorization. This preserves diagnostic practice without claiming hands-on experience you did not obtain.
Which preparation mistakes should you avoid?
The most damaging mistake is studying the wrong version. The second is treating the domain percentages as a complete syllabus. The third is confusing recognition with performance. Correct these by confirming the exam number, mapping every objective, and requiring an explanation or practical exercise for important topics.
Do not combine 220-1102 and 220-1202 notes casually. CompTIA’s current Version 15 rule requires both Core exams from the same version. If a resource uses a different exam number, check its status and relevance before adding it to your plan.
Do not allocate all your time to the largest domain and ignore the others. Operating Systems represents 31% of the 220-1102 blueprint, but Security represents 25%, Software Troubleshooting represents 22%, and Operational Procedures represents 22%. Each percentage must be interpreted with its domain label, and personal weaknesses may not follow the official distribution.
Do not treat practice-test scores as proof that you can do the job. Review every missed question and every guess. If you cannot explain the underlying objective, the result identifies a knowledge gap rather than confirming readiness.
Do not memorize dumps or leaked material. Besides being an inappropriate preparation method, remembered answers do not teach safe troubleshooting, version awareness, or operational judgment. Use legitimate objective-aligned practice and create your own explanations.
Do not schedule before checking logistics. CompTIA directs candidates to schedule through CompTIA Central and Pearson VUE, with in-person test-center and online OnVUE delivery options. Confirm the current appointment details, identification requirements, and delivery conditions through the official scheduling process rather than relying on an old forum post or a training provider’s summary.
Do not assume a listed language or delivery option applies unchanged to every version or location. The 220-1100-series catalog lists English, German, Japanese, Portuguese, Simplified Chinese, and Spanish, while the current 220-1202 page lists English, German, and Japanese. Treat these as version-specific information and verify the option attached to your intended exam.
How should you decide when to schedule?
Schedule only after the version, certification path, and delivery choice are clear. Your readiness decision should be based on objective coverage and repeatable reasoning: you can explain the four domains, work through unfamiliar support scenarios, choose safe actions, and identify when documentation or escalation is required.
Before scheduling, complete a final audit. Confirm that every objective has a note, demonstration, or reasoned scenario response. Revisit the error register and look for patterns such as confusing platform features, jumping to a fix without evidence, overlooking security implications, or failing to verify the result.
Then choose the delivery route that fits your circumstances. CompTIA directs candidates to use CompTIA Central and Pearson VUE and identifies both in-person test-center and online OnVUE options. Review the official scheduling page for current availability and requirements. Do not infer that a past appointment process, local center, or online setup remains unchanged.
If one domain remains substantially weaker, delay scheduling long enough to remediate it. A last-minute review of definitions may improve recognition, but it is unlikely to repair a repeated diagnostic or procedural error. Use targeted labs, objective-linked questions, and written explanations to close the specific gap.
If your Core 1 and Core 2 versions do not align, resolve that issue before setting a date. Version consistency is a certification-path decision, not a study preference.
What should you do after this guide?
Your next action is not to start with random practice questions. Verify whether your intended path is 220-1102 or the current 220-1202, obtain the matching objectives, and build a study plan around the four named domains. That sequence protects your time and keeps every resource relevant.
Download the official objectives and mark your baseline. Next, assign study blocks to Operating Systems, Security, Software Troubleshooting, and Operational Procedures, using the official domain weights as a planning reference rather than as a question forecast. Add a lab or scenario exercise to each block.
Create a version check in your notes: exam number, matching Core 1 number, resource version, and scheduling status. Update it whenever you add a course, guide, lab, or practice product. This simple record prevents accidental mixing of the 1100 and 1200 series.
Finally, use the official scheduling route only after your preparation audit is complete. CompTIA’s A+ certification requires both Core exams, so your plan should include the relationship between Core 1 and Core 2 even when your immediate study focus is 220-1102. The best preparation decision is the one that matches the current certification version, your actual skills, and the support work you intend to perform.
Conclusion
220-1102 remains a clearly defined Core 2 exam in the A+ 1100 series, but the current CompTIA A+ version uses 220-1202, making version verification the first practical decision. Once the correct path is confirmed, study the official objectives through four domains: Operating Systems, Security, Software Troubleshooting, and Operational Procedures. Combine objective tracking with controlled practice, written diagnosis, security-aware actions, and disciplined documentation. Schedule through the official CompTIA and Pearson VUE process only when your materials, Core 1 pairing, delivery choice, and readiness evidence all align.
Related exams
- 220-1101 exam — CompTIA A+ Certification Exam: Core 1
- 220-1201 exam — CompTIA A+ Certification Exam: Core 1
- 220-1202 exam — CompTIA A+ Certification Exam: Core 2