When a system begins randomly crashing after a hardware change (installing a GPU) and the correct vendor driver update does not resolve it, the best next troubleshooting step is to collect evidence about what is failing.
Windows records crash details, driver faults, and unexpected shutdowns in Event Viewer (System/Application logs) and related reliability tools. Quentin Docter specifically states that Event Viewer should be the first place you look when the solution is not evident because applications and the OS often create log entries that help verify operation and diagnose problems. These logs can reveal whether the crash is tied to a display driver fault, power/kernel events, or another subsystem. Docter also notes you can often find more information about application crashes by reviewing the Application log, and for instability/shutdown patterns you "start combing through the logs" in Event Viewer to determine whether the system lost power or crashed.
Mike Meyers adds that Event Viewer is the tool used to read and understand Windows logs (Application
/System/Setup/Security) for diagnosing what's happening on a system.
References: Quentin Docter - CompTIA A+ Complete Study Guide (Event Viewer as first stop; crash
/shutdown investigation via logs); Travis Everett & Andrew Hutz - CompTIA A+ All-in-One Exam Guide (Event Viewer logs and event levels for troubleshooting); Mark Soper - Mike Meyers' A+ Lab Manual (Event Viewer and the "big four" Windows logs).

The correct answer is A. .app, because macOS applications packaged as .app files are typically self- contained application bundles. This means that all required application files are stored within a single directory that appears as one file in Finder. When the .app file is moved to the Trash, the application is effectively removed from the system.
According to the Quentin Docter - CompTIA A+ Complete Study Guide, macOS applications are commonly distributed as .app bundles, allowing for simple installation and removal. This design contrasts with Windows, where applications often install files across multiple directories and require uninstallers.
The Travis Everett & Andrew Hutz - All-in-One Exam Guide explains that dragging a .app file to the Trash is generally sufficient to uninstall the software, although some applications may leave behind preference files or caches. However, from an exam perspective, .app is the only option that supports this uninstall behavior.
The Mike Meyers / Mark Soper Lab Manual further clarifies that .msi and .exe are Windows formats, .rpm is used by Linux package managers, and .pkg installers often install system-wide components that require a formal uninstallation process.
Because .app files support simple drag-to-trash uninstallation, A is the correct answer.

Comprehensive and Detailed Explanation From Exact Extract:
Just recognizing the device isn't enough-audio output must be routed to it manuallyby setting it as the default playback device in sound settings.
FromMark Soper - Mike Meyers' Lab Manual:
"If audio is still playing through the internal speaker, verify that the Bluetooth headset is set as the default playback device. This can be configured under Windows Sound Settings."

Comprehensive and Detailed Explanation From Exact Extract:
Multifactor authentication (MFA) is considered one of the most effective security measures for cloud environments. It requires users to verify their identity using two or more factors (e.g., password + phone app code), making it significantly harder for external attackers to gain access, even if the primary password is compromised.
B: Encryption is important for data protection but doesn't prevent unauthorized logins.
C: Backups protect against data loss but don't stop breaches.
D: Strong passwords are helpful but can still be phished or cracked - MFA adds a critical extra layer.
Reference:
CompTIA A+ 220-1102 Objective 2.2: Compare and contrast authentication technologies.
Study Guide Section: Cloud security best practices - MFA and access control

Comprehensive and Detailed Explanation From Exact Extract:
PXE (Preboot Execution Environment) allows workstations to boot over the network and download an OS image from a server. It is ideal for automating mass deployments using baseline images across many machines without the need for physical media.
A: An ISO is a disk image file but requires mounting or physical media.
B: Secure Boot is a security feature, not a method of deploying OS images.
C: USB requires manual installation and is not suitable for automated deployment at scale.
Reference:
CompTIA A+ 220-1102 Objective 1.4: Given a scenario, use appropriate Microsoft operating system installation methods.
Study Guide Section: Remote installation methods - PXE boot deployment