Examkin

All practice questions

423 questions

All types3,551Multiple choice1,809Multiple select786Numeric12Matching521Ordering423
Question 321Question →

A technician is troubleshooting a Windows 10 workstation that displays a Boot Configuration Data (BCD) missing error during startup. The technician needs to rebuild the BCD store using the command line in the Windows Recovery Environment (WinRE). Place the steps of this repair process in the correct sequential order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequential order begins with opening the WinRE Command Prompt, executing bootrec /rebuildbcd to scan for OS installations, pressing Y to add the detected OS to the BCD store, and finally exiting to restart the workstation.
The proper troubleshooting procedure requires first opening the WinRE Command Prompt, issuing bootrec /rebuildbcd to scan the storage drive for installed Windows operating systems, confirming the prompt with Y to write the entry to the BCD store, and restarting the computer to complete the verification.

Step-by-Step Solution

1
Launch the Command Prompt from WinRE Advanced Options.
Gains elevated offline administrative CLI access.
Boot repair tools like bootrec require an offline command environment.
2
Run bootrec /rebuildbcd.
Scans disks and prompts to add discovered Windows installations to the BCD.
The /rebuildbcd switch explicitly fixes missing or damaged BCD store records.
3
Confirm the boot addition prompt by entering Y.
Writes the operating system bootloader path into the BCD configuration.
Without user confirmation, the bootrec tool will not add the identified installation to the boot loader.
4
Close the command interface and restart the PC.
Initiates normal boot process using the repaired BCD store.
A system restart is required to verify that the boot sequence completes into Windows.

Key Concept

Rebuilding the Boot Configuration Data (BCD) store using the bootrec tool in WinRE
Question 322Question →

A system administrator is preparing to deploy a newly imaged standalone Windows workstation into a high-security corporate network environment. To ensure defense-in-depth and prevent exposure to network-borne threats during setup, the administrator must execute the workstation hardening baseline in a logical, secure sequence. What is the correct order of steps the administrator should take to secure the workstation from initial setup to final network placement?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for hardening the workstation is: First, change default administrative credentials and disable the local Guest account; second, connect to an isolated VLAN to install OS patches and security definitions; third, disable unneeded OS services, AutoPlay, and unused ports; fourth, configure local group policies for screen lock and lockout thresholds; fifth, enable the host-based firewall and connect to the production network.
The correct order follows established CompTIA security hardening guidelines: credentials and accounts are secured first to eliminate default access risks; OS updates and signatures are downloaded on an isolated VLAN next; unnecessary services, ports, and AutoPlay are disabled to minimize the attack surface third; local security policies (such as screen lock timeouts and account lockout controls) are enforced fourth; and host-based firewalls are activated immediately prior to joining the production network fifth.

Step-by-Step Solution

1
Secure local identity and default access controls.
Default administrative credentials are changed, and the Guest account is verified disabled.
Initial access vector risks must be mitigated first so unauthorized users cannot log into the machine using vendor defaults.
2
Perform patch management on an isolated segment.
System OS patches and antimalware definitions are updated without exposing the unhardened system to production network threats.
An unpatched system exposed directly to the network can be compromised before security software is updated.
3
Perform attack surface reduction.
Unnecessary OS services, ports, and AutoPlay/AutoRun policies are disabled.
Disabling unneeded features reduces potential exploit vectors on the local system.
4
Enforce OS security policies.
Screen lock timeouts, account lockout controls, and password complexity rules are established.
Policy enforcement secures the operating system environment against local unauthorized physical access and brute-force attempts.
5
Activate network layer endpoint defenses and join production network.
Host-based firewall is enabled and system is moved to production network.
Activating host firewall controls before final network plug-in completes defense-in-depth isolation.

Key Concept

Workstation Hardening Sequence & Attack Surface Reduction
Question 323Question →

A senior identity engineer is planning an operating system upgrade across primary Active Directory domain controllers in an enterprise network. Place the following change management procedures in the correct chronological order from first step to final step.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of change management steps begins with conducting a risk analysis and drafting a rollback plan, followed by submitting the request to the CAB for approval, notifying affected end-users of the scheduled maintenance window, executing the upgrade during the maintenance window, and concluding with post-implementation testing and documentation.
The standard CompTIA change management lifecycle follows a structured sequence: initial documentation (scope, risk analysis, and rollback plan), formal authorization by the Change Advisory Board (CAB), end-user notification of the scheduled maintenance window, implementation during the maintenance window, and post-implementation testing alongside final documentation.

Step-by-Step Solution

1
Identify the change preparation phase.
Performing a risk analysis and drafting a rollback plan is established as the initial step.
Before submitting any change for authorization, the technical scope, potential risks, and fallback procedures must be fully documented.
2
Identify the authorization phase.
Submitting the completed change request to the Change Advisory Board (CAB) follows initial preparation.
The CAB must review and authorize the plan and schedule before any implementation work or public announcements occur.
3
Identify the communication phase.
Notifying stakeholders and end-users of the upcoming maintenance window is the third step.
Users must be informed of expected service interruptions after authorization is granted but prior to starting the work.
4
Identify the deployment phase.
Executing the upgrade during the authorized maintenance window is the fourth step.
System modifications occur strictly within the designated maintenance window after all approval and communication prerequisites are satisfied.
5
Identify the post-deployment phase.
Conducting post-implementation testing and updating configuration documentation is the final step.
Testing validates that directory services function correctly, and final documentation updates complete the change lifecycle.

Key Concept

CompTIA A+ Change Management Lifecycle Order
Estimated Time:1m 30s
Question 324Question →

A security technician is decommissioning magnetic hard disk drives (HDDs) containing sensitive financial files. Arrange the following steps in the correct chronological sequence for executing a compliant hardware sanitization and disposition lifecycle.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological sequence begins with documenting chain of custody, followed by magnetic degaussing, physical shredding, and finally archiving the Certificate of Destruction.
The hardware disposition lifecycle follows a strict sequence: first, inventory logging establishes chain of custody; second, media sanitization (degaussing) renders the magnetic data unreadable; third, physical destruction (shredding) prevents hardware recovery; and fourth, administrative auditing secures a Certificate of Destruction.

Step-by-Step Solution

1
Inventory and Chain of Custody
Drive serial numbers are recorded and tracked.
Maintaining regulatory compliance requires documenting the custody of sensitive storage assets before any action is taken.
2
Data Sanitization
The magnetic drive platters are demagnetized via degaussing.
Degaussing renders data unreadable while the drives remain intact.
3
Physical Destruction
The drive hardware is reduced to small metallic fragments.
Physical shredding guarantees that no hardware components can be recovered or reassembled.
4
Compliance Verification
A Certificate of Destruction is validated and archived.
The certificate serves as formal legal proof that the data disposal process was completed according to standards.

Key Concept

Hardware Disposition Lifecycle and Chain of Custody
Estimated Time:1m 30s
Question 325Question →

A technician is troubleshooting a desktop computer that turns off immediately after being turned on. What is the correct sequence of steps the technician should follow to diagnose and resolve a suspected power supply issue according to standard troubleshooting procedures?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with verifying external power, checking internal motherboard cable seating, testing PSU rail voltages with a dedicated tester, and finally replacing the faulty power supply unit.
CompTIA troubleshooting methodology requires prioritizing simple external verifications before inspecting internal connections, taking tool-based measurements, and performing component replacement.

Step-by-Step Solution

1
Verify external power sources and connections.
Ensures utility power is actively reaching the power supply inlet.
Standard troubleshooting dictates starting with simple external checks first.
2
Inspect internal power cable seating on the motherboard.
Confirms 24-pin ATX and 8-pin EPS connectors are fully latched.
Loose motherboard power leads can cause thermal trip or immediate power-off events.
3
Test power supply outputs using a multimeter or PSU tester.
Identifies if voltage rails (+12V, +5V, +3.3V) are within proper operating specs.
Direct measurement isolates PSU electrical failure before performing component swaps.
4
Swap out the bad PSU for a functional replacement unit.
Restores consistent power to all system hardware components.
Remediation via hardware replacement occurs after empirical failure verification.

Key Concept

Power Supply Diagnostics and Isolation Sequence
Question 326Question →

A field technician is auditing print subsystem behavior on a commercial electrophotographic (EP) laser printer to identify where image corruption occurs during document creation. Place the following EP laser printing steps in the correct chronological order from the initial job receipt to the final paper output.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological sequence for the electrophotographic (EP) printing process is: 1) Processing (rasterizing data in memory), 2) Charging (conditioning the drum with negative charge), 3) Exposing (writing the latent image via laser), 4) Developing (applying toner to exposed drum areas), 5) Transferring (attracting toner to paper using positive charge), and 6) Fusing (melting toner onto paper with heat and pressure).
The standard CompTIA electrophotographic (EP) printing process follows seven primary steps: Processing, Charging, Exposing, Developing, Transferring, Fusing, and Cleaning. Processing translates the document into a bitmap image in memory. Charging applies a high negative charge across the photosensitive drum. Exposing uses a laser to lower the voltage on specific areas of the drum, creating a latent electrostatic image. Developing transfers toner onto those exposed areas. Transferring uses positive charge on the back of the paper to pull toner off the drum onto the paper. Finally, Fusing uses heat and pressure rollers to permanently fuse toner into the paper fibers.

Step-by-Step Solution

1
Identify the data rendering phase.
Processing is identified as the initial step where print commands are rasterized into a bitmap in memory.
The printer must build the page image in memory before physical drum manipulation can begin.
2
Identify the drum preparation phase.
Charging is placed second.
The primary charge roller conditions the photosensitive drum surface with a uniform negative charge.
3
Identify the optical writing phase.
Exposing is placed third.
The laser beam scans the drum to neutralize specific areas, leaving a latent electrostatic image.
4
Identify the toner application phase.
Developing is placed fourth.
Negatively charged toner moves from the developer roller to the higher potential (discharged) areas on the drum.
5
Identify the paper contact and image transfer phase.
Transferring is placed fifth.
The transfer roller charges the paper positively to pull toner particles off the drum onto the paper.
6
Identify the final bonding phase.
Fusing is placed sixth.
Heat and pressure melt and press the toner permanently into the paper fibers.

Key Concept

Electrophotographic (EP) Laser Printing Process Sequence
Question 327Question →

A desktop support technician is constructing an automated maintenance script to compress oversized log files located within a system directory. To ensure proper execution without runtime errors, which sequence represents the correct logical order of these scripting constructs from top to bottom?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct logical order begins with initializing environment variables, followed by constructing a loop construct to process target files, placing a conditional branch inside the loop to test file size, and executing the compression action command inside the conditional block.
In standard scripting across administrative environments (such as Bash, PowerShell, or Python), scripts follow a top-down execution model. First, environment variables establishing paths and threshold values must be declared. Next, a loop construct is defined to traverse the directory. Inside the loop, a conditional branch evaluates each item against the variable threshold. Finally, the execution command (file compression) is placed inside the conditional block to execute only when the condition evaluates to true.

Step-by-Step Solution

1
Define variables
Establishes reference variables for paths and parameters before they are used in control flow statements.
Referencing undefined environment variables causes script failure or unintended behavior.
2
Establish the iteration loop construct
Creates the repetition block (e.g., `for` or `while` loop) to traverse the file collection.
A loop construct is necessary to systematically process multiple files in sequence.
3
Add conditional decision logic inside the loop
Evaluates each file's size against the previously defined variable threshold.
Conditional branching (`if/then`) ensures actions only target files meeting specific criteria.
4
Place the target action statement inside the conditional block
Compresses or archives only the log files that trigger a true evaluation result.
Action statements must be nested within the conditional block to prevent indiscriminate file modification.

Key Concept

Logical execution flow of scripting constructs (variable initialization, loop constructs, conditional branching, and action execution)
Estimated Time:1m 30s
Question 328Question →

A system technician needs to prepare a newly installed secondary hard drive for Windows file storage using the DiskPart command-line utility. Arrange the following DiskPart sub-commands in the correct execution sequence to target the disk, clear existing partition data, create a partition, apply the file system, and mount the volume for operating system access.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational order for disk initialization using DiskPart is: select disk 1, clean, create partition primary, format fs=ntfs quick, and assign.
The sequential workflow of disk management in the DiskPart CLI strictly follows target selection (`select disk 1`), disk clearing (`clean`), partition creation (`create partition primary`), file system formatting (`format fs=ntfs quick`), and volume mounting (`assign`). Each step depends directly on the successful context and output of the preceding step.

Step-by-Step Solution

1
Set execution context to target disk
Disk 1 becomes the active focus for DiskPart commands.
DiskPart requires a target disk selection before performing structural modifications to protect active system drives.
2
Wipe disk partition tables
The target disk is completely cleared and marked as unallocated space.
Existing partition records must be removed before creating a fresh primary partition layout.
3
Generate primary storage volume structure
A raw primary partition is established across the unallocated disk space.
The operating system requires a defined partition boundaries before a file system can be formatted.
4
Format partition with target file system
The primary partition is formatted with the NTFS file system metadata.
Windows native drives require a compatible file system such as NTFS to store files and security permissions.
5
Mount volume and allocate drive letter
The formatted partition receives an available drive letter (e.g., E:) and becomes accessible in Windows Explorer.
Without assigning a drive letter or mount point, users cannot access the storage volume through standard operating system paths.

Key Concept

Windows DiskPart command-line drive initialization and partitioning workflow
Question 329Question →

A system administrator needs to configure a standalone Windows 11 Pro computer so that standard users are prompted to enter administrator credentials on the secure desktop whenever an action requires administrative privilege elevation. Place the steps required to configure this policy using the Local Security Policy snap-in in the correct sequential order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with launching secpol.msc, navigating to Local Policies > Security Options, opening the policy 'User Account Control: Behavior of the elevation prompt for standard users', selecting 'Prompt for credentials on the secure desktop', and finally clicking OK to save the changes.
To modify specific UAC behaviors in Windows, the technician must first open the Local Security Policy snap-in (secpol.msc). From there, navigating to Local Policies > Security Options exposes the granular UAC policies. Opening 'User Account Control: Behavior of the elevation prompt for standard users', selecting 'Prompt for credentials on the secure desktop', and clicking OK properly sets and saves the elevation security rule.

Step-by-Step Solution

1
Launch the management tool
The Local Security Policy management console opens.
Administrative security policy modifications require opening secpol.msc.
2
Navigate the policy console tree
The Security Options policy settings are displayed in the right pane.
UAC security policies reside inside Local Policies > Security Options.
3
Open the target policy properties
The policy configuration window opens.
The technician must open the specific policy controlling elevation behavior for standard user accounts.
4
Configure the policy value
The setting is changed to 'Prompt for credentials on the secure desktop'.
This setting forces UAC to require administrator credentials on the secure desktop during elevation requests.
5
Save policy configuration
The policy is updated and applied.
Clicking OK saves the policy setting to the local security database.

Key Concept

Configuring User Account Control (UAC) policy settings using Local Security Policy (secpol.msc)
Estimated Time:1m 30s
Question 330Question →

A technician identifies that a Windows computer is infected with malware. Arrange the following steps of the standard CompTIA malware removal procedure in the correct sequential order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of steps is: 1) Disconnect the computer from the local network and disable wireless connections, 2) Turn off System Restore in Windows to remove existing restore points, 3) Update the anti-malware signatures and perform a full system scan, and 4) Enable System Restore and create a clean restore point.
According to CompTIA's standard 7-step malware removal procedure, isolation of the infected system must occur first (Step 2) to stop the spread of infection. Disabling System Restore follows (Step 3) to clear infected restore points. Next, remediation occurs by updating anti-malware definitions and running scans (Step 4). Finally, System Restore is re-enabled and a clean restore point is created (Step 6) after verifying system cleanliness.

Step-by-Step Solution

1
Isolate the infected device
Network communication is severed, stopping potential lateral movement or C2 communication.
CompTIA Step 2 (Isolate infected systems) must happen before modifying system configuration or scanning.
2
Disable System Restore
All existing restore points (which may contain malware copies) are purged.
CompTIA Step 3 (Disable System Restore) prevents reinfection from system restore points during remediation.
3
Remediate infected systems
Malware is scanned and removed using current signatures.
CompTIA Step 4 (Remediate infected systems) cleans the operating system environment.
4
Enable System Restore
A clean recovery baseline is established for future system protection.
CompTIA Step 6 (Enable System Restore and create a restore point) takes place after the malware is confirmed removed.

Key Concept

CompTIA 7-Step Malware Removal Process
Question 331Question →

A corporate workstation is experiencing persistent web browser redirects to untrusted promotional websites whenever a user attempts to navigate to standard corporate URLs. In what order should a technician perform the following steps to properly remediate the browser security compromise?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of steps is: Disconnect the workstation from the network; Terminate active browser processes via Task Manager; Remove unrecognized browser extensions and reset browser settings; Inspect the Windows hosts file and clear unauthorized proxy settings; Perform a full system anti-malware scan, reconnect to the network, and verify proper browser operation.
Remediating a browser redirection issue follows standard malware response principles: first isolate the system from the network to stop active communication, terminate active processes, clean browser application components (extensions and settings), inspect OS-level redirection configurations (hosts file and proxy settings), and finally perform a comprehensive anti-malware scan before reconnecting to confirm resolution.

Step-by-Step Solution

1
Isolate the compromised machine from the network.
Network communication between the compromised browser/adware and external malicious servers is halted.
Isolation stops telemetry, prevents further adware payload downloads, and protects network assets.
2
Close active browser sessions and end malicious processes in Task Manager.
Memory-resident browser hijacker scripts and rogue helper objects are stopped.
Attempting to change settings while malicious processes are running can cause settings to immediately revert.
3
Purge rogue browser extensions and restore browser defaults.
Malicious search engines, home page hijacks, and pop-up scripts integrated into the browser profile are removed.
Browser add-ons are common vectors for search hijacking and persistent pop-up generation.
4
Review system-level network configurations including proxy settings and the hosts file.
System-wide traffic redirection rules configured in the OS layer are restored to default clean states.
Browser hijackers often inject loopback redirects into the hosts file or set up rogue local proxies to survive browser resets.
5
Execute an anti-malware scan, restore network access, and test web browsing.
System integrity is confirmed and verified clean before returning the system to normal operations.
Ensures no secondary malware persistence mechanisms remain active.

Key Concept

Browser Hijacker and Redirect Remediation Workflow
Question 332Question →

A cybersecurity technician at a digital media firm is responding to a workstation infected with spyware. Arrange the following remediation steps in the exact sequence required by the CompTIA 7-step malware removal process.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence follows the standard CompTIA 7-step malware remediation process: first quarantine the infected workstation, then disable System Restore, followed by updating anti-malware signatures and scanning, then enabling System Restore and creating a new restore point, and finally educating the end user.
The official CompTIA 7-step malware remediation process consists of: 1. Identify symptoms, 2. Quarantine infected systems, 3. Disable System Restore, 4. Remediate infected systems (update anti-malware software and use scan/removal tools), 5. Schedule scans and run updates, 6. Enable System Restore and create a restore point, and 7. Educate the end user. The sequence correctly orders steps 2, 3, 4, 6, and 7.

Step-by-Step Solution

1
Isolate the compromised system.
Workstation is quarantined from network connectivity.
Prevents lateral movement of the malware across the local network.
2
Turn off system backup mechanisms.
Windows System Restore is disabled.
Prevents malicious files from being indexed into restore snapshots.
3
Remediate active infections.
Anti-malware signatures are updated and a full scan purges infected files.
Ensures complete detection and removal of malware.
4
Re-establish system rollback points.
System Restore is enabled and a clean baseline point is created.
Restores system protection features only after the machine is verified clean.
5
Deliver user security training.
End user is trained on security awareness.
Mitigates future social engineering and malware infection vectors.

Key Concept

CompTIA 7-Step Malware Remediation Process
Question 333Question →

A computer running Windows fails to start due to a corrupted Boot Configuration Data (BCD) file. Arrange the following repair steps in the correct sequential order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct troubleshooting sequence is: 1) Boot using Windows installation USB media and select Repair your computer, 2) Navigate to Troubleshoot > Advanced options and launch the Command Prompt, 3) Execute the bootrec /scanos command, and 4) Execute the bootrec /rebuildbcd command.
The recovery sequence must begin by loading Windows Recovery Environment (WinRE) from external installation media because the corrupted BCD prevents normal booting. Opening the Command Prompt from Advanced options allows access to repair utilities. Running 'bootrec /scanos' scans connected drives to detect valid operating systems. Finally, running 'bootrec /rebuildbcd' rebuilds the BCD store and adds the detected installation back to the boot menu.

Step-by-Step Solution

1
Insert Windows installation media and boot the system into the Windows Recovery Environment (WinRE).
Access to external system repair menus is achieved.
A corrupt BCD prevents normal local booting, requiring repair tools to load from media.
2
Select Troubleshoot, open Advanced options, and click Command Prompt.
An elevated command-line window opens in the recovery environment.
Bootrec commands require a command-line prompt within WinRE.
3
Run bootrec /scanos to locate Windows installations.
All connected storage drives are scanned for active Windows installations.
Verifying existing installations ensures the utility detects the OS before updating BCD references.
4
Run bootrec /rebuildbcd to recreate the BCD store.
The Boot Configuration Data file is reconstructed with valid boot entries.
This step writes the new boot configuration entries so Windows can locate the operating system loader upon startup.

Key Concept

Rebuilding Boot Configuration Data (BCD) using WinRE command-line tools
Question 334Question →

A technician is troubleshooting a Windows 11 workstation where a specialized financial reporting application regularly hangs during data processing and subsequently crashes. Place the following troubleshooting steps in the correct sequence to systematically isolate the hanging process, identify the failing module, eliminate software conflicts, and repair corrupted system dependencies.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct troubleshooting sequence is: 1) Analyze the process wait chain in Task Manager, 2) Inspect the Event Viewer Application log for Event ID 1000 entries, 3) Perform a clean boot via System Configuration (msconfig), and 4) Run the System File Checker utility (sfc /scannow).
The correct sequence adheres to CompTIA troubleshooting best practices: start with real-time process diagnostics (Task Manager wait chain analysis), follow with historical log examination (Event Viewer Application log Event ID 1000), proceed to third-party conflict isolation (clean boot via msconfig), and conclude with system dependency repair (sfc /scannow).

Step-by-Step Solution

1
Analyze the process wait chain in Task Manager while the app is unresponsive.
Identifies immediate blocking threads, child processes, or deadlocks in real time.
Live diagnostic data gathering must occur before restarting or terminating the process.
2
Examine Event Viewer Application logs for Event ID 1000.
Reveals the faulting module name, faulting application path, and exception code.
Provides historical log evidence regarding specific file crash dependencies.
3
Execute a clean boot using System Configuration (msconfig).
Disables all non-essential third-party services and startup apps.
Isolates whether background third-party software or service conflicts are triggering the failure.
4
Execute sfc /scannow in an elevated Command Prompt.
Verifies system file integrity and replaces corrupted system binaries.
Ensures core operating system dependencies identified in the log analysis are healthy.

Key Concept

Systematic isolation and remediation sequence for Windows application hangs and crashes using native diagnostic tools.
Question 335Question →

A desktop application on a Windows workstation freezes unexpectedly during startup. As a CompTIA A+ technician, in what order should you execute the following troubleshooting steps to isolate the root cause and remediate the application crash?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct troubleshooting sequence begins with analyzing Event Viewer logs (Event ID 1002/1000), using Resource Monitor's Analyze Wait Chain feature to identify blocking threads, terminating the blocking process, and performing a system file repair using sfc /scannow.
CompTIA A+ troubleshooting protocol requires collecting diagnostic evidence prior to making system modifications. The technician first checks Event Viewer Application logs for Event ID 1000 (Application Error) or 1002 (Application Hang) to confirm the faulting module. Next, Resource Monitor's Analyze Wait Chain feature is used to pinpoint the exact thread or child process causing the freeze. The blocking process is then terminated to resolve the active deadlock. Finally, System File Checker (sfc /scannow) is executed to repair any underlying system file corruption.

Step-by-Step Solution

1
Examine Event Viewer Application logs for Event ID 1000 or 1002.
Determines the specific application executable, faulting module, and exception code.
Log investigation provides baseline empirical diagnostic information without altering system state.
2
Launch Resource Monitor and select Analyze Wait Chain for the application.
Discovers thread deadlocks and pinpoints which secondary process holds required resources.
Wait chain inspection isolates active process dependencies causing the freeze.
3
End the blocking child process or thread in Resource Monitor.
Clears the process deadlock and restores immediate system/application responsiveness.
Targeted termination clears the immediate hang without requiring a reboot.
4
Run sfc /scannow in an elevated Command Prompt.
Scans protected system files and replaces corrupted binaries with cached copies.
System repair ensures long-term stability and resolves corrupted OS dependency files.

Key Concept

Sequencing diagnostic and remediation steps for application hangs in Windows using Event Viewer, Resource Monitor Wait Chain analysis, and System File Checker.
Question 336Question →

A cloud administrator is preparing to migrate an enterprise on-premises file server to a cloud-based storage infrastructure. To ensure minimal disruption to business operations and adhere to organizational policy, the administrator must follow formal change management procedures. In what sequence should the administrator execute the following steps of the change management workflow?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with defining the purpose and scope, followed by conducting a risk assessment, creating implementation and rollback plans, obtaining CAB approval, and finally executing the change with post-implementation testing and documentation.
Standard CompTIA A+ change management workflow requires establishing scope/purpose first, evaluating risk second, building implementation/rollback plans third, securing CAB authorization fourth, and completing execution, post-testing, and documentation fifth.

Step-by-Step Solution

1
Define purpose and scope of the proposed change.
Establishes clear boundaries and technical requirements for the migration.
A documented scope is necessary to understand what is being changed and why.
2
Conduct a risk analysis.
Identifies risk levels, potential disruptions, and affected business units.
Evaluating risk helps determine the necessary safety precautions and rollback requirements.
3
Formulate implementation procedures and a rollback plan.
Produces the technical instructions and backout steps if deployment fails.
Change management guidelines require a complete rollback plan before seeking management approval.
4
Request authorization from the Change Advisory Board (CAB).
Obtains formal business and technical approval to proceed.
The CAB must review all risk analyses and backout strategies to approve the scheduled maintenance window.
5
Execute the change, test functionality, and update documentation.
Completes the migration, verifies normal operation, and updates system records.
Deployment occurs only after approval; post-testing ensures operational stability and complete configuration management tracking.

Key Concept

CompTIA Change Management Lifecycle
Question 337Question →

A desktop computer shuts down unexpectedly after running heavy processor workload applications for several minutes. A technician suspects the CPU is overheating due to degraded thermal compound. In what order should the technician perform the following steps to properly service the CPU thermal interface and verify the resolution?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

Disconnect power and remove heatsink -> Clean off old thermal compound -> Apply small dot of new thermal paste -> Reinstall heatsink, connect fan, and verify temperatures in BIOS/UEFI.
The correct diagnostic and repair sequence begins with safely isolating power and removing the heatsink. Next, old compound is cleaned off with isopropyl alcohol so fresh thermal paste can be applied to a clean metal surface. Finally, the heatsink is remounted securely, the fan power cable is reconnected, and temperature levels are monitored in the BIOS/UEFI setup utility.

Step-by-Step Solution

1
Disconnect workstation power and remove the CPU cooling heatsink assembly.
The CPU heat spreader surface and heatsink contact plate are exposed.
Ensures physical safety and permits direct access to the thermal interface.
2
Clean dried thermal compound using high-percentage isopropyl alcohol and a lint-free cloth.
Both contact surfaces are clean and free of old debris.
Old, dried thermal paste acts as an insulator rather than a conductor, preventing effective heat dissipation.
3
Dispense a small, pea-sized dot of fresh thermal paste onto the center of the CPU heat spreader.
Thermal paste is positioned to spread evenly under pressure.
Provides optimal thermal conductivity without overflowing onto motherboard components.
4
Reattach the heatsink evenly, plug in the CPU_FAN header, power on the system, and check CPU temperature hardware monitors in BIOS/UEFI.
The cooling fan receives power and processor operating temperatures are confirmed within normal ranges.
Validates that the cooling system is fully functional and thermal throttling/overheating is resolved.

Key Concept

CPU Cooling Maintenance and Thermal Interface Servicing
Estimated Time:1m 0s
Question 338Question →

A Windows workstation running an enterprise database client frequently becomes unresponsive ('Not Responding') during high-volume queries. A CompTIA A+ technician must isolate the process hang in real-time, preserve system diagnostics prior to process termination, and correlate the event with historical system stability data. Place the administrative troubleshooting steps in the correct chronological order from initial real-time isolation to historical root-cause analysis.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with using Analyze Wait Chain in Task Manager to isolate thread dependencies, followed by creating a memory dump file while the process is still active. Next, the technician terminates the blocking process to recover system responsiveness. Finally, the technician inspects Event Viewer (Event ID 1002) for module error details and reviews Reliability Monitor (perfmon /rel) to correlate the hang with historical software changes.
The proper sequence follows standard Windows performance troubleshooting methodology: real-time diagnosis (Analyze Wait Chain), diagnostic state preservation (Create Memory Dump), symptom remediation (Ending the Blocking Process), log-level examination (Event Viewer Event ID 1002), and long-term trend correlation (Reliability Monitor). Creating a memory dump must always occur before terminating the process, as process termination purges the target memory space.

Step-by-Step Solution

1
Use Task Manager's Analyze Wait Chain feature on the hung application process.
Identifies whether the application is waiting on another process ID (PID) or thread to release a shared system resource.
Troubleshooting must start with real-time thread inspection to determine the immediate cause of the freeze.
2
Select 'Create memory dump file' from the process context menu in Task Manager.
Generates a .dmp file capturing the active volatile memory footprint of the hung application.
Process dump files must be created prior to terminating the process, as ending the process purges its active memory space.
3
Terminate the identified blocking PID or force-close the hung process.
Releases the resource lock and restores user responsiveness on the workstation.
Clearing the deadlock is necessary to recover workstation usability after diagnostic memory state has been saved.
4
Check Event Viewer under Windows Logs > Application for Event ID 1002.
Reveals logged specifics regarding the hung process, faulting module, and crash timestamps.
Post-remediation log analysis captures binary-level details recorded by the OS during the application hang.
5
Open Reliability Monitor using perfmon /rel.
Displays a chronological graph of application failures, hardware faults, and recent software installations.
Macro-level historical evaluation determines whether the hang is part of a broader pattern triggered by recent patches or updates.

Key Concept

Windows Application Crash & Hang Isolation Workflow
Estimated Time:2m 30s
Question 339Question →

A technician is troubleshooting a UEFI-based Windows 11 computer that fails to boot, displaying a boot configuration error. After booting into the Windows Recovery Environment (WinRE) Command Prompt, the technician decides to manually recreate the corrupted EFI System Partition (ESP) structure and Boot Configuration Data (BCD). In what correct sequence should the technician execute the following repair steps?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for repairing the EFI boot environment in WinRE is: 1) Run diskpart to locate the hidden EFI System Partition volume number; 2) Assign a temporary drive letter to the EFI System Partition and exit diskpart; 3) Navigate to the EFI boot directory and execute attrib -h -r -s BCD to remove system attributes from the BCD file; 4) Rename the existing BCD file to BCD.old to preserve a backup; 5) Execute bcdboot C:\Windows /s Z: /f ALL to recreate the boot environment files.
To repair a corrupted UEFI boot setup, the hidden EFI System Partition must first be located and assigned a volume drive letter using diskpart. Once accessible, file protections on the existing BCD must be cleared with attrib so it can be renamed as a backup. Finally, bcdboot is executed targeting the assigned drive letter to write clean boot files and rebuild the BCD.

Step-by-Step Solution

1
Open Diskpart utility to inspect disk partitions and volumes.
The hidden FAT32 system partition (ESP) volume index is identified.
You cannot access or target the ESP drive until its volume number is found.
2
Select the ESP volume and assign a drive letter (e.g., Z:), then exit Diskpart.
The ESP volume becomes accessible via the Z: drive path.
Command-line tools like attrib and ren require an accessible drive letter path.
3
Change directory to Z:\EFI\Microsoft\Boot\ and run attrib -h -r -s BCD.
The file attributes locking the BCD store are cleared.
System files cannot be modified or renamed while marked as read-only, hidden, or system files.
4
Rename the BCD file using ren BCD BCD.old.
The corrupted BCD file is renamed and no longer active.
Renaming the file prevents collision errors when generating fresh BCD files.
5
Run bcdboot C:\Windows /s Z: /f ALL.
Fresh EFI system files and a new BCD store are written to the ESP partition.
bcdboot copies system boot files from the Windows directory to the target boot partition.

Key Concept

UEFI EFI System Partition (ESP) and BCD manual repair procedure using WinRE Command Line Tools
Estimated Time:2m 0s
Question 340Question →

A helpdesk technician is troubleshooting a third-party screen-recording application on a standalone Windows 11 Pro computer. The application crashes whenever the display dims to show the User Account Control (UAC) prompt. To prevent the screen dimming while preserving elevation prompts for application changes, what is the correct sequence of steps to reconfigure the UAC notification level?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts by opening Control Panel, opening User Accounts and selecting Change User Account Control settings, moving the slider down to 'Notify me only when apps try to make changes to my computer (do not dim my desktop)', clicking OK, and finally confirming the elevation prompt by selecting Yes.
To modify UAC settings in the Windows GUI, a technician must open Control Panel, navigate to User Accounts, and select 'Change User Account Control settings'. To prevent the display driver from dimming the screen (which causes third-party screen recorders to crash), the technician moves the slider to 'Notify me only when apps try to make changes to my computer (do not dim my desktop)'. Clicking OK and approving the UAC elevation consent prompt finalizes the change.

Step-by-Step Solution

1
Launch Control Panel from the Start Menu.
Control Panel navigation options become available.
UAC configuration applets for account management are located in Control Panel.
2
Navigate to User Accounts and select 'Change User Account Control settings'.
The User Account Control Settings dialog opens with the vertical configuration slider.
This applet provides the graphical interface for setting system-wide UAC notification levels.
3
Adjust the slider to the second notch from the top: 'Notify me only when apps try to make changes to my computer (do not dim my desktop)'.
Secure desktop dimming is disabled while UAC prompts remain active for application installer/configuration actions.
This specific UAC state stops Windows from switching to the isolated Secure Desktop, resolving display driver conflicts with screen recording tools.
4
Select OK at the bottom of the User Account Control Settings window.
Windows prepares to update registry keys under HKEY_LOCAL_MACHINE.
Submitting the dialog requests system privilege elevation to apply the change.
5
Select Yes when prompted by User Account Control to confirm the security setting update.
The new UAC notification state is saved and applied immediately without requiring a reboot.
Modifying UAC settings requires administrative approval to prevent unauthorized tampering.

Key Concept

Configuring User Account Control (UAC) notification levels and Secure Desktop behavior.
PreviousPage 17 / 22Next
All practice questions — CompTIA A+ (Core 1 & Core 2) | Examkin