CompTIA 220-1202 - CompTIA A+ Core 2 (2026 Exam Update)

The best tool is SSH (Secure Shell) because the scenario requires running command-line instructions on a remote network switch and capturing the text output. SSH provides a secure, encrypted remote terminal session (TCP port 22) that is commonly used to administer Linux/UNIX systems and networking equipment, making it ideal for switches that are typically managed through a CLI. Quentin Docter explicitly notes that ssh.exe launches the Secure Shell client and that it allows you to connect to a Linux/UNIX server or networking equipment, and he explains that SSH encrypts communications for secure text-console remote access. Mike Meyers’ Lab Manual reinforces that Telnet/SSH enable you to connect to a “server or fancy router” to run commands remotely, and that SSH is the secure modern alternative because the session is encrypted. The All-in-One guide also emphasizes SSH as the encrypted replacement for Telnet and highlights its use for remote command-line administrative tasks. By contrast, RDP and VNC are graphical remote-desktop tools, and WinRM is Windows-specific remote management rather than a standard switch-access method.

RAM is an electrostatic-sensitive component. When removing or transporting RAM modules, they should be stored in antistatic bags to protect against electrostatic discharge (ESD), which can damage the memory. This is a standard best practice in hardware handling.

A. Demagnetization is not applicable to RAM.

C. Plugging in power to ground is not safe or recommended for static protection.

D. Installing identical memory pairs is applicable for dual-channel configuration, but not directly related to transporting or handling RAM.

A cable run under a carpet is vulnerable to compression, bending, and repeated physical stress from foot traffic, which can damage the cable jacket, distort the twists, loosen terminations, or partially break conductors—often showing up as intermittent connectivity. Quentin Docter notes that on a wired network, “other wired issues can include bad or poorly connected cables,” and you should check cabling and connections as a cause of intermittent problems. Putting a cable where people walk on it increases the chance it becomes “bad” over time or develops poor connections, producing the intermittent symptoms described in the answer option.

From a safety/professional practice perspective, Mike Meyers emphasizes that unmanaged cables are “dangerous tripping hazards” and that in business environments cables should be “carefully tucked away… or placed under cable runners,” using “proper cable management.” While that supports hazard reduction, the best reason in this question’s choices focuses on network reliability: repeated walking over the cable can cause intermittent issues. So the correct answer is D.

ApplicationsandLibraryare core system directories in macOS. TheApplicationsfolder contains installed applications. TheLibraryfolder contains support files, preferences, and other system-related files.

From theQuentin Docter – CompTIA A+ Complete Study Guide:

“macOS organizes system and user files into several key folders. Among them, Applications and Library are standard system folders where apps and related files are stored.”

An " OS Not Found " error typically indicates that the computer is attempting to boot from a drive that doesn ' t contain a valid operating system or bootable partition. The presence of a USB drive might be confusing the boot order. Therefore, the first step a technician should take is to verify and adjust the boot sequence in the system’s firmware (BIOS or UEFI). It ' s possible that the USB drive is being prioritized over the internal hard drive, which may cause the system to miss the OS entirely.

A. Running data recovery tools is premature before confirming boot order.

B. Repartitioning the disk would destroy existing data—this should not be done until confirmed the OS is actually missing.

D. Switching between UEFI and BIOS (legacy mode) might help in rare cases, but it is not the first step in standard OS boot issue troubleshooting.

When DHCP isn’t enabled, static IPs must be assigned manually, so the engineering team provides the IP details.

From Travis Everett – All-in-One Exam Guide:

“If DHCP is unavailable, technicians need the static IP configuration to connect devices to the network.” .

The correct answer is A. Remove account administrative rights, because unauthorized software installation is most commonly possible when users have local administrator privileges. In Windows environments, installing most applications requires elevated permissions. If users are members of the local Administrators group, they can bypass many built-in security controls and install software without IT approval.

According to the Quentin Docter – CompTIA A+ Complete Study Guide, the principle of least privilege is fundamental to endpoint security. Users should only be granted the minimum permissions necessary to perform their job functions. Removing administrative rights prevents users from installing unapproved applications and significantly reduces malware risk.

The Travis Everett & Andrew Hutz – All-in-One Exam Guide explains that while technologies like firewalls, SmartScreen, and Endpoint Detection and Response (EDR) provide important layers of protection, they do not directly stop users from installing software if they already have administrative access. EDR detects and responds to threats, but it does not prevent intentional installation by privileged users.

The Mike Meyers / Mark Soper Lab Manual reinforces that controlling user permissions is the most effective preventive control against unauthorized changes to a system. Removing admin rights stops the root cause rather than reacting after installation occurs.

Therefore, to prevent future unauthorized software installations, removing account administrative rights is the most direct and effective solution, making A the correct answer.

Removing users from the local admin group prevents them from installing unauthorized software.

From Quentin Docter – Complete Study Guide:

“Local admin privileges allow users to install unauthorized apps. Removing them from this group restricts installations and helps prevent malware.” .

An incident report documents key details such as the cause of the outage, steps taken to resolve it, and measures to prevent recurrence. It is a post-mortem analysis often shared with stakeholders to improve future response.

According to the Quentin Docter – CompTIA A+ Complete Study Guide:

“An incident report provides a summary of an event that disrupted normal operations and includes a timeline of what occurred, how the issue was diagnosed and fixed, and who was involved in the resolution”.

This is reaffirmed in Travis Everett’s All-in-One Guide:

“Documentation after an incident helps technical teams and management review the situation and learn from it. This is formalized in an incident report”.

“No OS found” commonly indicates the firmware can’t locate boot instructions for the installed OS. If the drive isn’t obviously failing (no unusual noises) and BIOS/UEFI settings are reasonable, a classic cause is a corrupt Master Boot Record (MBR) (on MBR-partitioned disks). Mike Meyers’ Lab Manual explains that when BIOS can’t find an OS, causes may include configuration issues or drive problems, but also states: “If the correct drive is already first in the boot sequence, the master boot record… may be corrupt and need to be rebuilt.”

The Lab Manual also explains what the MBR does: the first sector contains boot code that informs the system about installed operating systems, and “without this bit of code, your OS will never load.” The All-in-One guide describes the same: BIOS looks at the first sector for instructions, and without the MBR code, the OS won’t load.

NTFS corruption wouldn’t typically present as “no OS found” at the firmware stage, and TPM issues usually create different security/boot errors. Therefore, MBR (D) is most likely.