CompTIA A+ 220-1102: Core 2 Skills from a Retired Exam

CompTIA 220-1102 was the Core 2 half of A+ V14, concentrating on operating systems, endpoint security, software troubleshooting, and professional operational procedures. It paired with the historical 220-1101 Core 1 to cover a technician's responsibilities across both hardware and software. The 1100-series exams are retired: A+ V15 uses 220-1201 and 220-1202, with the latter being the corresponding current Core 2 examination. Those operating-system and support principles remain useful, but candidates booking A+ today need the current Core 2 objectives rather than retired 220-1102 dates.

Core 2 was never just about knowing which menu contains a setting. A competent technician must maintain a usable device under competing pressures: security policy, compatibility, business continuity, user productivity, and audit requirements. A seemingly small configuration change can prevent a remote worker from accessing a service or disrupt a critical legacy application. Good support involves identifying who owns the machine, which management policies apply, what data must be protected, and how a change will be reversed if it does not solve the problem. Those responsibilities persist across exam updates and operating-system releases.

Windows configuration and recovery logic

Windows administration covers more than installation. A technician should understand partitions, filesystems, boot modes, local accounts, services, scheduled work, update behavior, and device management. A new application might require a particular runtime or privilege; a malfunctioning driver can interfere with hardware while the operating system itself remains intact. Tools such as Event Viewer, Task Manager, Disk Management, Device Manager, and command-line utilities expose different types of evidence. Choosing among them depends on the symptom: a failed service start calls for service and event details, while a depleted system volume calls for storage analysis.

A boot failure needs a careful order of tests. Confirm that the hardware sees the intended disk and that the configured boot mode matches the installation. Then distinguish a damaged boot configuration from an operating-system file problem, storage failure, or recently added driver. Blindly reinstalling Windows may remove evidence and risk user data, particularly on an unmanaged endpoint. Recovery-media tools, restore facilities, system-file checks, and safe boot options each have a narrower purpose. The most defensible response preserves data first and uses the least disruptive method capable of testing the suspected cause.

User profiles and permissions frequently explain issues that appear application-specific. One user may be unable to save into a folder while another can because of NTFS permissions or a managed application policy. A program may launch under an administrator account but fail under the intended user due to missing profile data, restricted registry access, or misconfigured per-user settings. Elevating the normal user to administrator can conceal these faults while creating a persistent security weakness. Reproduce the problem with appropriate test identities and inspect effective permissions, not merely the visible ownership label.

Updates must also be understood as a lifecycle. A patch can close a security weakness while triggering incompatibility with an old driver or line-of-business application. A delayed patch can preserve one workflow while exposing the endpoint to preventable attack. Organizations should establish deployment rings and rollback procedures according to risk. Technicians need to know whether a computer is managed by centralized tools before initiating local repairs that may be overwritten. Successful maintenance restores the device to its managed state rather than creating a configuration exception that nobody can track.

macOS, Linux, and mixed operating systems

A+ Core 2 expected familiarity with more than one desktop operating system. macOS and Linux use different management conventions from Windows, but the support questions remain recognizable: how services start, how files are permitted, where logs are kept, how applications are installed, and how networking is configured. On a Linux machine, a service failing to start may be diagnosed through its system manager and logs. A permissions problem may involve owners, groups, execute bits, mount options, or a mandatory-access-control system. Copying Windows instructions into a Linux shell without understanding their effects is not a support strategy.

A mixed estate introduces cross-platform behavior that no single-machine lab demonstrates. A user may authenticate successfully to a web application on Windows but fail on a Mac because device certificates differ. Shared files can produce permission or filename behavior that varies by filesystem. Printer support may require different drivers and queues. Troubleshooting should compare common dependencies first, such as identity, network, certificate trust, and application versions, then isolate the platform-specific elements. Keeping an accurate inventory helps distinguish supported configurations from unsupported combinations.

Virtualization and dual-boot arrangements can complicate operating-system maintenance. A machine's visible environment may be a guest whose resources depend on a host, or an application may run inside a compatibility layer. Diagnosing performance requires knowing which layer controls memory, storage, and networking. Snapshots and restore points provide certain recovery capabilities but should not be mistaken for an organization-wide backup policy. A support action that works in a disposable lab may be inappropriate for an encrypted business endpoint containing unique records.

Security controls and the endpoint boundary

Operating-system security includes authentication, least privilege, patching, antimalware, firewalls, secure configuration, and protection of information at rest. These are related controls, not interchangeable solutions. Full-disk encryption protects an offline disk from disclosure, but it does not prevent a signed-in malicious process from accessing files the user can open. A local firewall limits permitted traffic but may not detect a credential-phishing attack. Multifactor authentication improves access control while still requiring safe recovery methods for lost authenticators. A technician should know what each control can and cannot accomplish.

Malware investigation requires containment before extensive repair. If a device appears compromised, the right response depends on organizational incident rules and the possibility that it contains forensic evidence. Disconnecting it may stop further communication, but powering it down or running unapproved cleanup tools might erase useful volatile state. A home computer and a corporate endpoint under incident investigation do not have identical procedures. Technicians should escalate to the responsible security team when evidence preservation or regulated data is involved, rather than improvising a complete forensic response from an entry-level checklist.

Social engineering is a software-support issue because technicians are often asked to reset accounts, install tools, and override controls. A caller claiming to be an executive might request an emergency password reset; an email may impersonate a familiar vendor and direct the user to a fake sign-in portal. Identity-verification processes must survive urgency and seniority. A support worker should use approved independent channels to confirm a request and document changes to credentials or privileged access. A technically accurate command can still cause a serious security incident if it is executed for an impostor.

Software diagnosis and application behavior

Software failures are often triggered by a dependency outside the application itself. A program that crashes after an update may require a runtime repair, compatible driver, restored configuration, or a corrected permission. A web application that freezes for one user may reflect a corrupted browser profile, a blocked extension, or a certificate problem. Start by identifying the specific error, the scope of affected users, and what changed. Determine whether the failure can be reproduced with a different profile, device, or network. This is more informative than repeatedly clearing caches without recording the results.

Performance complaints call for measurements. High CPU might indicate an unexpectedly busy process, while memory pressure leads to paging and degraded responsiveness. A drive nearly full can prevent updates or normal temporary-file operation; a DNS delay can make a web application feel slow without creating local resource pressure. Correlate process activity, storage statistics, logs, and network behavior during the reported slowdown. A support technician should avoid installing untrusted 'optimizer' utilities or making speculative registry changes, both of which can worsen reliability and make the endpoint harder to manage.

Application licensing and compatibility can create misleading messages. A piece of software may install correctly but reject an activation, device entitlement, or account association. An application may work when disconnected from a corporate VPN but fail when the VPN changes DNS or traffic routing. Resolving such issues requires an understanding of business ownership, deployment licensing, authentication, and network paths. The correct escalation includes evidence about what was tested and which layer owns the unresolved decision.

Support operations, documentation, and compliance

Professional procedures were a defining element of Core 2. Work often requires change approval, documentation, safe disposal, backups, ticket handling, privacy controls, and communication that matches the user's technical level. For example, replacing a damaged laptop involves the hardware repair, recovery of files, enrollment into management, restoration of business applications, re-creation of access, and proper handling of the retired storage. The work is not finished when the power button functions again.

Backups should be tested, not assumed. A copied folder may omit application state or hidden user data; a cloud synchronization service may propagate deletions rather than retain recoverable versions. Recovery time and data-loss tolerance depend on the importance of the workload. Before reinstalling an operating system, verify that the required files and recovery keys exist and that restoration is authorized. On an enterprise endpoint, encryption keys, certificates, and management registration can be as important as documents when returning a machine to service.

A high-quality ticket records symptoms in the user's words, objective diagnostics, changes made, resulting behavior, and remaining risk. Vague notes such as 'fixed PC' deny the next technician useful history. Respectful communication is equally important. A user who cannot access a required application needs a realistic workaround and updates, not a lecture about how they should have operated the system. Escalate clearly when the issue is caused by architecture, security restrictions, or unavailable vendor support rather than making unsupported promises.

Applying old knowledge to the current A+ route

The practical distinction in 2026 is between the durable work of OS support and the exam blueprint candidates should purchase. The current CompTIA A+ 220-1202 continues the Core 2 emphasis on operating systems, security, software troubleshooting, and operational procedures under V15 objectives. The details of supported operating systems, technologies, and tested emphasis can change. An old 220-1102 workbook may be useful for explaining Windows services or user-permission faults, but it should not be treated as proof that every topic maps identically to V15.

Learners starting now should check current CompTIA certifications against the vendor's active exam listings and candidate policies. Practice repairing devices without sacrificing security: reproduce the fault, protect data, verify the account and device scope, choose a reversible change, and confirm the result under the intended user's access. Those habits translate across Windows releases and exam generations, which is why historical Core 2 material retains educational value long after the exam itself stops being offered.