Mastering the CompTIA A+ Exam (220-1102): Your Launchpad Into a Thriving IT Career
CompTIA A+ 220-1102 was the Core 2 exam in the previous A+ generation. The active A+ V15 pathway uses 220-1202 for Core 2 alongside 220-1201 for Core 1. This distinction matters: operational-system basics from a 220-1102 resource remain useful, but old objectives and an old registration code are not a reliable guide to a new exam attempt.
On this page
- What Core 2 has traditionally assessed
- Support operating systems through repeatable evidence
- Make least privilege practical
- Understand operational procedures, not just commands
- Map old material to the active V15 exam
- Prepare a realistic Core 2 practice lab
- Two Core 2 support tickets to practice from the old objectives
- Choose a next experiment from evidence, not from the answer key
- Show Core 2 competence in a working support queue
- What to do next
Core 2 is about administering and supporting endpoint systems safely. Success depends less on recalling a large list of control-panel names and more on choosing appropriate actions for a user, device and organization.
What Core 2 has traditionally assessed
Operating systems, security, software troubleshooting and operational procedures are at the heart of Core 2. A technician may need to configure user access, diagnose an application crash, secure a workstation, clean up a failed update or decide whether a change belongs in an escalation queue.
Historical Core 2 notes can provide a foundation for Windows administration, Linux/macOS concepts, endpoint hardening and support workflows. They need reconciliation to CompTIA’s latest 220-1202 objectives before the learner assumes the content is complete.
Support operating systems through repeatable evidence
For Windows, practice explaining service state, update history, storage pressure, permissions and driver behavior. For Linux and macOS, learn the same conceptual questions—who can read a file, which process is running, what changed and where the logs live—even though the interfaces and commands differ.
Suppose an application crashes only for one user profile. Record the operating-system version, the application build and the error signature. Compare a fresh test profile with the affected one before uninstalling shared components. If the change would affect other users, obtain approval and plan rollback. The right answer is often a narrow investigation rather than a broad reset.
Make least privilege practical
An endpoint should have only the permissions required for its tasks. Security practice includes multifactor authentication where supported, patch management, device encryption, physical controls and recognition of suspicious requests. Understand the distinction between an administrator’s elevated session and ordinary daily work.
For example, a colleague who asks to turn off endpoint protection ‘temporarily’ may be reporting a genuine compatibility problem. The next step is to capture the alert and reproduce it under an approved process, not to remove safeguards reflexively. Good troubleshooting protects the data as well as the workflow.
Understand operational procedures, not just commands
A support request should progress through intake, verification, diagnosis, controlled change, validation and documentation. Explain the impact and obtain permission before touching a customer’s device. Protect personal information, keep appropriate chain-of-custody records where required and follow escalation standards.
Backups are part of incident response. Before reinstalling an operating system, confirm recoverable data, encryption keys, required applications, network access and licensing. Write a successful-restoration criterion in advance; ‘the installer finished’ does not prove the user can work.
Map old material to the active V15 exam
Download the current Core 2 220-1202 objective document and mark each old topic as directly reusable, changed or absent. Give special attention to modern cloud productivity workflows and responsible handling of AI-assisted support tools where they appear in the active objectives. Avoid claims that an AI tool’s generated script is safe without a review and test.
When evaluating practice scenarios, ask what information the technician has, what risk an action creates, what would differentiate the possible causes and how the action can be reversed. This approach performs better on unfamiliar situations than memorized multiple-choice fragments.
Prepare a realistic Core 2 practice lab
- Create separate standard and administrative accounts; verify permissions without making the daily user an administrator.
- Simulate a failed update on a disposable virtual machine and document a safe recovery route.
- Investigate a service startup failure with event logs and a controlled configuration change.
- Back up and restore sample non-sensitive files while verifying permissions and file integrity.
- Write a support-ticket summary that a second technician can use without asking the customer to repeat every step.
Use isolated devices or virtual machines and avoid questionable downloaded ‘exam dumps.’ The objective is to learn secure, transferable support skills while studying for a current credential.
Two Core 2 support tickets to practice from the old objectives
Ticket one: a workstation cannot open a business application after an update. Record the application build, operating-system version, precise error, last successful use and whether the problem affects one user or an entire group. Do not immediately uninstall a security control or grant local administrator privileges. Reproduce the issue with authorized access; examine service status, logs, update history, disk space and user permissions. A fault that occurs for one profile only points in a different direction from a service that fails system-wide.
State your hypothesis before acting. If the application cannot write to its user-owned configuration directory, test file permissions with the least privilege needed; if a service does not start, trace its dependencies and logs. Make only one documented change at a time. After the repair, ask the requester to repeat the actual work task rather than rely solely on a process-start indicator. Record what changed, how to reverse it, and whether another workstation needs the same fix.
Ticket two: a user reports a suspicious sign-in and a missing file. Begin by verifying the user and the ticket’s authority, then distinguish a possible account compromise from ordinary permission or sync trouble. Follow the organization’s incident-reporting process before changing credentials or deleting artifacts. Preserve relevant timestamps and logs, avoid circulating passwords or customer documents, and escalate when unauthorized access cannot be ruled out.
After authorized containment, review multifactor status, unusual sessions, access grants, device health, cloud sync state and available version history. Restore a file only through approved backup or versioning controls. Close the support case with a plain-language explanation of what was confirmed, what remains uncertain, and which team owns further investigation. The point of the exercise is safe troubleshooting under constraints, not merely naming security tools.
Choose a next experiment from evidence, not from the answer key
For each ticket, create a two-column work log: an observation on the left and the next falsifiable hypothesis on the right. Include an alternative explanation before the first change. This discipline turns legacy Core 2 study material into useful operational practice while keeping the 220-1102 exam code clearly historical.
Show Core 2 competence in a working support queue
Keep a portfolio of approved, synthetic troubleshooting tickets. One can document a user-profile corruption case: compare an affected and a known-good profile, inspect application and system events, check the change history, and use a reversible fix that preserves the user’s files. Another can document endpoint policy drift: show the intended MFA, update or encryption requirement, the actual policy state, and the escalation path when the device cannot comply safely.
Ticket quality is itself a career skill. The handoff should include the verified symptom, affected users, relevant environment and timestamps, what tests were already performed, which actions were approved, the final confirmation with the user, and what remains unresolved. A technician who describes uncertainty clearly is often more useful than one who reports every support incident as ‘fixed’ without validation.
Use these cases to interview for service-desk, desktop support or junior endpoint-operations work; compare the demands of each role instead of inferring a guaranteed salary from the certificate. Plan separate Core 1 and Core 2 exam preparation under the active V15 codes. The old 220-1102 edition is historical guidance, not a current registration choice.
What to do next
Treat the 220-1102 code in the title as historical. Check CompTIA’s current 220-1202 objective document and book only the current exam edition in your test region. The A+ credential requires the two appropriate core examinations.
For a focused next session, choose one operating-system failure and produce a short incident record with the expected result, observations, least-risk correction and successful validation.