Examkin

All practice questions

423 questions

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

An IT technician is tasked with migrating user profiles, desktop settings, and application data from a legacy Windows workstation to a newly deployed machine using Microsoft's User State Migration Tool (USMT) during an enterprise operating system upgrade. What is the correct order of steps the technician should take to execute this migration process successfully?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The proper USMT migration sequence begins with configuring XML migration rules (MigUser.xml/MigApp.xml), running ScanState.exe on the source computer, completing the clean OS installation on the target computer, installing necessary software applications, and finally running LoadState.exe on the target computer to restore user data.
The User State Migration Tool (USMT) requires a structured sequence for command-line migrations in automated OS deployments. Customizing XML migration rule files comes first to define what data to harvest. Next, running the ScanState utility captures the profiles and settings from the source computer into a store. The target operating system is then freshly installed, followed immediately by installing required applications so their default registry entries exist. Finally, running the LoadState utility restores the saved profiles and settings into the target system and application environments.

Step-by-Step Solution

1
Configure XML control files
Defines parameters for files, settings, and application states to collect.
USMT requires custom or standard XML rule files (like MigUser.xml) to dictate what gets captured.
2
Run ScanState.exe on source system
Gathers user state and stores it in an encrypted/compressed network or local store.
Data must be extracted from the old operating system environment before replacing or decommissioning it.
3
Deploy clean OS on target system
Establishes a baseline operating system environment.
The destination system must have a functional OS installation ready to accept software and user profiles.
4
Install local applications on target system
Prepares application paths and registry hives on the new OS.
If applications are not installed before restoring settings, USMT cannot properly map application preferences and registry keys.
5
Run LoadState.exe on target system
Applies user files, settings, and profile configurations to the new OS.
LoadState is the final command that completes data restoration into the newly configured application and OS environment.

Key Concept

User State Migration Tool (USMT) Workflow
Estimated Time:2m 0s
Question 122Question →

A desktop computer in a corporate office suddenly loses access to the company intranet after a workstation relocate. A technician is dispatched to troubleshoot the issue using a standard OSI bottom-up approach. In what sequence should the technician perform the following diagnostic steps?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct troubleshooting sequence from first to last is: 1) Inspect the physical RJ-45 cable connections and link LED lights, 2) Execute ipconfig /all to verify IP configuration, 3) Ping the local default gateway address, 4) Perform an nslookup query to test domain name resolution.
Following the standard bottom-up troubleshooting methodology, the technician begins at Layer 1 by physically checking cable connections and NIC status LEDs. Next, at Layer 2/3, local IP addressing is checked with ipconfig /all. Third, Layer 3 routing reachability is verified by pinging the default gateway. Finally, higher-layer services such as DNS resolution are tested with nslookup.

Step-by-Step Solution

1
Verify Physical Connectivity (Layer 1)
Ensure physical cables are securely seated and link LEDs indicate active hardware signal.
Bottom-up troubleshooting mandates confirming physical Layer 1 media before testing software or network protocols.
2
Verify Logical IP Configuration (Layer 2/3)
Determine whether the NIC has a valid DHCP configuration or a 169.254.x.x APIPA address.
Before sending network traffic, the host must possess a properly assigned IP address and subnet mask.
3
Test Local Gateway Reachability (Layer 3)
Confirm ICMP echoes return successfully from the default gateway.
Pinging the default gateway isolates whether the issue is local to the subnet or further up the routing path.
4
Test Name Resolution (Layer 7 / DNS)
Verify that domain names resolve correctly to destination IP addresses.
Testing DNS name resolution with nslookup confirms high-level application service accessibility.

Key Concept

OSI Model Bottom-Up Network Troubleshooting Sequence
Estimated Time:1m 30s
Question 123Question →

A technician is troubleshooting a computer that unexpectedly shuts down during operation and refuses to turn back on until the AC power cord is unplugged for several seconds. Place the diagnostic steps in the correct order to determine if a tripped power supply unit (PSU) protection circuit or a motherboard short is causing the failure.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct diagnostic sequence is: 1) Unplug the AC power cable and wait 30 seconds to drain flea power, 2) Disconnect all internal power cable harnesses from the motherboard and components, 3) Bridge the PS_ON pin to ground on the 24-pin connector and reconnect AC power, and 4) Measure DC voltage output on the +3.3V, +5V, and +12V rails using a multimeter.
When a system shuts down and requires AC power removal to turn back on, a PSU safety circuit has tripped. The proper order of operations requires first clearing flea power by disconnecting AC power. Next, all internal hardware components must be disconnected to isolate the PSU. Then, bridging the PS_ON pin manually tests basic power-on capability. Finally, using a multimeter verifies that output voltage rails fall within standard ATX specifications.

Step-by-Step Solution

1
Remove main AC power to allow internal capacitors to discharge.
Residual energy (flea power) is completely drained, resetting any latched protection circuits inside the power supply unit.
Latching safety circuits in modern PSUs keep power disabled until AC power is fully cycled.
2
Disconnect all internal PSU cables from motherboard and hardware components.
The power supply unit is isolated from all potential downstream electrical shorts.
A shorted motherboard component or drive will immediately trip the PSU again if left connected during diagnostic testing.
3
Insert a jumper between the PS_ON (green wire) and a Ground (black wire) pin on the 24-pin main connector.
The PSU turns on independently, and its cooling fan begins to spin.
This simulates the power switch signal normally sent by the motherboard power header.
4
Use a multimeter set to DC voltage to test output pins on the power connectors.
Voltage readings are verified against expected values (+12VDC, +5VDC, +3.3VDC).
Confirms the power supply outputs stable voltages within standard ATX tolerance limits under no-load testing.

Key Concept

Power Supply Unit (PSU) Protection Circuit Reset and Isolation Testing
Question 124Question →

A network technician needs to resolve persistent network stack corruption on a Windows 11 client workstation by performing a full reset of the Winsock catalog and TCP/IP stack. In what order should the technician execute the required actions to complete this process?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence is: Open an elevated Command Prompt -> Execute netsh winsock reset -> Execute netsh int ip reset -> Restart the Windows operating system.
To repair a corrupted network stack on Windows, the technician must first launch an elevated Command Prompt to gain administrative rights. Next, running 'netsh winsock reset' restores the API catalog. Following that, executing 'netsh int ip reset' rewrites the core TCP/IP registry keys. Finally, restarting the computer is mandatory to apply the low-level driver and protocol configuration changes.

Step-by-Step Solution

1
Open Command Prompt as Administrator
Grants the necessary elevated user rights to modify protected network configurations.
Standard command prompt sessions lack the administrative rights needed to execute low-level netsh reset commands.
2
Run netsh winsock reset
Resets the Winsock catalog back to a clean default state.
Corrupted Windows Sockets API entries must be restored before re-binding network protocol interfaces.
3
Run netsh int ip reset
Overwrites and rebuilds the Windows TCP/IP registry keys (IPv4 and IPv6 stack reset).
Clears core protocol bindings to resolve transport layer and routing table corruption.
4
Reboot the workstation
Unloads existing drivers, reloads the clean registry configurations, and restores standard network functionality.
Low-level protocol stack updates take effect only after a system restart.

Key Concept

Windows TCP/IP Stack and Winsock Reset Procedure
Question 125Question →

A technician is troubleshooting an impact dot-matrix printer used in a warehouse to print multi-part continuous shipping forms. The printer is running, but text on the carbon copy pages is faint and barely legible. Place the troubleshooting and corrective steps in the logical order they should be performed according to standard methodology.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The proper sequence begins with inspecting the ribbon consumable, followed by adjusting the mechanical platen gap for paper thickness, running a local hardware self-test page, and lastly replacing the printhead assembly if hardware fault is confirmed.
Standard CompTIA troubleshooting dictates beginning with simple physical checks (inspecting ribbon tension and condition), moving to mechanical adjustments specific to the media (setting the platen gap lever), performing standalone hardware tests (printing a self-test page), and executing component replacement (replacing the printhead) only after isolating a physical defect.

Step-by-Step Solution

1
Inspect the ink ribbon cassette for proper installation, proper ribbon tension, and excessive wear or dryness.
Confirms whether the ribbon is properly delivering ink to the paper surface upon pin impact.
Always check simple physical consumables first before modifying mechanical settings or replacing parts.
2
Adjust the printhead platen gap lever setting based on the thickness of the multi-part forms.
Positions the printhead at the correct distance to allow full pin impact force through carbon duplicate layers.
An incorrect platen gap setting prevents pins from exerting enough force on thicker multi-part paper.
3
Execute a built-in hardware self-test page from the printer control panel.
Determines if the physical mechanical components print correctly independent of computer drivers or print queues.
Isolates hardware print defects from host system driver configuration errors.
4
Replace the printhead assembly.
Restores pin matrix striking mechanism if specific pins are bent or broken.
Major hardware component replacement is performed only after isolating the fault to a broken internal assembly.

Key Concept

Impact Dot-Matrix Troubleshooting Methodology
Question 126Question →

A desktop support technician needs to automate Windows deployments across several new workstations using an answer file. Arrange the steps involved in creating and executing an unattended Windows installation using Windows System Image Manager (SIM) in the correct chronological order.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological sequence for an unattended Windows deployment using Windows SIM is: 1) Open install.wim in Windows SIM to generate a catalog file, 2) Create a new answer file and configure settings across configuration passes, 3) Validate the answer file in Windows SIM, 4) Save the answer file as autounattend.xml in the root folder of the USB installation media, and 5) Boot the target system from the USB drive.
The correct order follows the standard Windows System Image Manager (SIM) deployment workflow: First, generate or load a catalog (.clg) file from install.wim. Second, create the answer file and populate settings in configuration passes. Third, validate the answer file to check for configuration errors. Fourth, save the file as autounattend.xml in the root directory of the boot USB media. Finally, boot the target system from the media to execute the automated installation.

Step-by-Step Solution

1
Generate image catalog
A catalog file (.clg) is created from install.wim
Windows SIM requires a catalog file to index configurable settings for the specific Windows installation image.
2
Configure answer file settings
Components are added to configuration passes such as specialize and oobeSystem
Deployment settings must be populated into appropriate passes to automate setup prompts like user creation and network configuration.
3
Validate answer file
Answer file is checked for syntax errors and missing required elements
Validation confirms that the answer file structure is error-free before saving it to installation media.
4
Save autounattend.xml to media root
The file autounattend.xml is placed at the root level of the bootable USB drive
Windows Setup automatically searches for autounattend.xml at the root level of removable media during system boot.
5
Boot target workstation
Unattended installation executes automatically
Booting from the USB media causes Windows Setup to detect autounattend.xml and perform the installation silently.

Key Concept

Unattended OS Installation with Windows SIM and autounattend.xml
Question 127Question →

A desktop technician needs to increase the User Account Control (UAC) notification level on a Windows workstation to 'Always notify' using the classic interface. What is the correct sequence of steps to complete this configuration?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order begins with opening Control Panel and selecting User Accounts, followed by clicking Change User Account Control settings, moving the slider to 'Always notify' and clicking OK, and concluding by confirming the UAC prompt with Yes.
The correct order follows standard Windows management workflow: opening the User Accounts Control Panel applet, opening the UAC settings dialog, adjusting the slider to the highest security setting and clicking OK, and finally confirming the UAC prompt to apply the system policy change.

Step-by-Step Solution

1
Open Control Panel and choose User Accounts
Accesses the Windows user management applet containing account security settings
Control Panel serves as the central administrative hub for legacy account settings
2
Select Change User Account Control settings link
Launches the User Account Control Settings dialog
This link provides direct access to the UAC slider interface
3
Adjust the slider to 'Always notify' and click OK
Configures the desired security baseline level
Moving the slider alters the security threshold before saving
4
Accept the UAC elevation warning by clicking Yes
Applies the new UAC configuration to the operating system
Modifying UAC behavior is a system-wide administrative action that requires privilege elevation confirmation

Key Concept

Windows User Account Control (UAC) configuration steps
Estimated Time:1m 0s
Question 128Question →

A field technician is troubleshooting an Android tablet where a key enterprise navigation application repeatedly freezes and stops responding during daily routing. The technician needs to follow standard CompTIA troubleshooting methodology by escalating from the least invasive step to the most invasive step. In what order should the technician execute the following remediation actions?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The technician should sequence troubleshooting from least invasive to most invasive: first, force stop the application; second, clear the app cache; third, clear app data; fourth, uninstall and reinstall the application; and finally, perform a full factory reset of the device.
CompTIA troubleshooting best practices require technicians to start with the least invasive remediation to minimize downtime and risk of data loss. Terminating the stuck process (force stop) is non-destructive. Clearing the cache removes temporary files while preserving user configurations. Clearing application data resets local settings and local databases. Uninstalling and reinstalling replaces application binaries and configuration structures. Performing a factory reset wipes the entire operating system and all installed software, making it the final and most invasive option.

Step-by-Step Solution

1
Identify the process termination step as the least invasive action.
Force stopping the process halts execution without removing files or resetting user preferences.
Always attempt to stop non-responsive processes before modifying persistent storage.
2
Identify temporary storage cleanup as the next step.
Clearing cache removes temporary working files while retaining accounts and configuration data.
Corrupted cached data is a common cause of freezing that can be resolved without losing user settings.
3
Select local application state reset as the subsequent step.
Clearing app storage data removes local settings, cached database files, and credential configuration.
If temporary cache clearing fails, corrupt local configuration files must be wiped before re-installing.
4
Select application re-installation.
Uninstalling and reinstalling replaces binary executable files and core application code.
Corrupted application binaries require complete removal and replacement if data clearing does not fix the failure.
5
Designate device wiping as the final, most invasive step.
A factory reset restores the mobile OS to its initial state, requiring full re-provisioning.
System-wide OS resets affect all installed applications and OS settings, making it the absolute last resort.

Key Concept

Least-Invasive Mobile OS Application Troubleshooting Methodology
Question 129Question →

A IT support technician needs to configure a Windows 11 workstation so that a corrective maintenance script automatically runs whenever a specific critical system error occurs. The technician plans to use built-in administrative tools to link the event entry directly to an automated task. Arrange the administrative steps required to accomplish this configuration 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 starts with opening Event Viewer to locate the System log, right-clicking the target event to choose 'Attach Task To This Event...', completing the wizard trigger configuration, specifying 'Start a program' with the script path, and finally saving the task to the Task Scheduler Library.
The proper administrative workflow begins in Event Viewer where the technician identifies the specific event log entry. Using the 'Attach Task To This Event...' context option automatically launches the Create Basic Task Wizard with the log name and Event ID pre-filled as the trigger. The technician then configures the action to 'Start a program', inputs the script path, and completes the wizard to register the task in the Task Scheduler Library.

Step-by-Step Solution

1
Access Event Viewer
Event Viewer opens showing system logs.
You must locate the target event entry before attaching an automated task to it.
2
Initiate Task Attachment
The Create Basic Task Wizard launches with event parameters pre-configured.
Right-clicking the target event and selecting 'Attach Task To This Event...' bridges Event Viewer with Task Scheduler.
3
Configure Task Trigger Details
The event-based trigger settings are specified.
The wizard requires confirming the name and trigger details associated with the selected Event ID.
4
Define Task Action
The action is set to execute the designated script.
Task Scheduler needs the explicit action type ('Start a program') and executable path to run the script.
5
Finalize and Register Task
The task is saved in the Task Scheduler Library.
Finishing the wizard registers the task so Windows monitors the log and runs the script upon event occurrence.

Key Concept

Linking Event Viewer events to automated Task Scheduler actions for system administration automation.
Question 130Question →

A technician is troubleshooting a desktop computer that powers on with active cooling fans but fails to POST, emitting a repeating single-tone beep code associated with memory initialization errors. Place the following diagnostic steps in the correct sequence to systematically isolate the cause, starting with the least intrusive action.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct diagnostic sequence begins by disconnecting non-essential external peripherals, followed by reseating the existing RAM modules, performing a CMOS reset to clear corrupted settings, and lastly testing the motherboard using a single known-good memory module in each slot.
CompTIA hardware troubleshooting methodology dictates moving from the simplest, non-invasive procedures (external peripherals) to basic mechanical fixes (reseating RAM), then firmware resets (CMOS clear), and finally component isolation (single known-good RAM module testing).

Step-by-Step Solution

1
Isolate external variables
External noise, short circuits from peripherals, or improper external power delivery are ruled out.
Always start hardware diagnostics with the least intrusive and fastest checks.
2
Reseat internal memory modules
Restores solid electrical contact across all memory pins if modules were unseated.
Thermal expansion and physical movement can break pin contact without hardware damage.
3
Reset CMOS/NVRAM settings
Clears bad memory XMP profiles, custom timings, or corrupted BIOS configuration data.
Resetting firmware settings ensures incorrect memory parameters are not preventing POST.
4
Perform single module and slot isolation testing
Identifies specifically whether a module is failed or a slot channel on the motherboard is defective.
Using a known-good module eliminates dual-channel variables and pinpoint component failure.

Key Concept

Systematic Component Isolation for POST and RAM Diagnostics
Question 131Question →

A systems administrator needs to restrict administrative elevation behavior on a standalone Windows 11 Pro workstation so that administrators are required to enter credentials on a secure desktop whenever a program requests elevated privileges. What is the correct sequence of steps to configure this policy using the Local Security Policy snap-in?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence begins with launching the snap-in via secpol.msc, navigating to Local Policies -> Security Options, opening the policy 'User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode', and selecting 'Prompt for credentials on the secure desktop'.
To modify detailed UAC prompt requirements for administrator accounts on Windows Pro, a technician must open the Local Security Policy console using secpol.msc, navigate through Local Policies to Security Options, edit 'User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode', and select 'Prompt for credentials on the secure desktop'.

Step-by-Step Solution

1
Launch the MMC Management Snap-in
The Local Security Policy window opens.
Administrative security policies for standalone Windows workstations are managed through secpol.msc.
2
Navigate to the Security Options Policy Node
The right panel populates with granular UAC and account security policies.
UAC security settings are located under Local Policies -> Security Options.
3
Open the Administrative Elevation Behavior Policy
The policy properties dialog box opens.
This specific policy targets administrator elevation prompts specifically.
4
Configure the Security Setting and Apply
The policy is updated to require credentials on the secure desktop.
Configuring 'Prompt for credentials on the secure desktop' ensures credentials must be entered explicitly when privilege escalation occurs.

Key Concept

Configuring User Account Control (UAC) administrative prompt behavior via Windows Local Security Policy (secpol.msc)
Question 132Question →

A desktop technician is performing a clean installation of Windows 11 on a newly assembled workstation equipped with a brand-new, unformatted NVMe solid-state drive. What is the correct sequence of steps the technician must follow from first to last to complete the operating system installation process?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological sequence is: 1) Boot from USB media via UEFI mode, 2) Select unallocated space to create default partitions, 3) Copy files and install features, and 4) Complete the Out-of-Box Experience (OOBE) setup.
Performing a clean operating system installation follows a strict sequence: first, boot the hardware using bootable installation media in UEFI mode; second, initialize and select the unallocated storage drive so Windows Setup can partition it properly; third, allow the setup program to copy and expand installation files onto the drive and perform a system reboot; finally, complete the initial user configuration and customization in the Out-of-Box Experience (OOBE) phase.

Step-by-Step Solution

1
Boot from flash media
The Windows Preinstallation Environment (WinPE) setup interface loads into memory.
The system cannot install an OS onto a blank drive without booting from an external installation source first.
2
Partition target storage
System creates required partition structures (EFI system partition, MSR, and primary NTFS partition).
Windows 11 requires a GUID Partition Table (GPT) disk layout and formatted file system structure before file extraction.
3
Perform file installation and reboot
Core OS binaries are copied to disk and the system reboots into the installed OS image.
Installation files must be expanded and written to local storage before user-level configuration can occur.
4
Configure Out-of-Box Experience (OOBE)
Initial user account, region, internet connection, and system privacy settings are established.
OOBE finalizes the personalization and initial user setup phase after the primary installation phase completes.

Key Concept

Standard Clean OS Installation Workflow
Estimated Time:1m 30s
Question 133Question →

A network technician is troubleshooting a Windows client workstation that lost network and internet access following a local router maintenance task. The technician needs to follow a standard, inside-out command-line diagnostic process to isolate the failure point.

Place the following Windows command-line actions in the correct logical troubleshooting order from first step to last step.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct logical troubleshooting sequence is: 1) Run `ipconfig /all` to inspect local interface configuration, 2) Run `ping 127.0.0.1` to verify internal TCP/IP stack integrity, 3) Run `ping 192.168.1.1` to test local gateway reachability, 4) Run `nslookup www.example.com` to check DNS name resolution, and 5) Run `tracert 8.8.8.8` to trace the external network path.
Systematic network troubleshooting follows an inside-out progression: first verify local adapter configuration details (`ipconfig /all`), validate internal TCP/IP software stack operation (`ping 127.0.0.1`), verify local gateway reachability (`ping 192.168.1.1`), test DNS host resolution (`nslookup`), and finally trace path hops to remote destinations (`tracert`).

Step-by-Step Solution

1
Inspect local client IP configuration
Retrieve IP address, subnet mask, default gateway, and DNS server details using `ipconfig /all`.
You must establish whether the machine has acquired valid networking parameters before generating diagnostic network traffic.
2
Verify internal protocol stack operation
Send ICMP echo requests to `127.0.0.1`.
Confirms that the internal network adapter software stack and protocol drivers are operational.
3
Verify local area network segment reachability
Send ICMP echo requests to the default gateway IP (`192.168.1.1`).
Tests physical cabling/wireless links and local router interface responsiveness.
4
Test domain name resolution service
Query host names using `nslookup www.example.com`.
Determines whether network issues stem from DNS resolution failures versus IP connectivity issues.
5
Isolate external WAN routing failure points
Trace network hops to a public IP using `tracert 8.8.8.8`.
Identifies the exact external gateway or hop where traffic is delayed or dropped.

Key Concept

Command-Line Network Diagnostic Workflow
Question 134Question →

A network technician needs to manually configure a static IPv4 address, subnet mask, default gateway, and primary DNS server on a Windows 11 client workstation using the Command Prompt. Which sequence of steps must the technician perform from first to last to complete and verify this configuration?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with launching an elevated Command Prompt, identifying the target interface name using `netsh interface ipv4 show interfaces`, applying the static IP address and default gateway, assigning the static DNS server address, and finally executing `ipconfig /all` to verify the configuration.
Configuring static IP settings on Windows via netsh requires administrative privileges, which must be obtained first. Next, querying active interfaces ensures the correct adapter name is targeted in netsh syntax. Setting the primary IPv4 address, subnet mask, and default gateway precedes setting the DNS server address. Finally, verification via `ipconfig /all` confirms that all settings have taken effect.

Step-by-Step Solution

1
Elevate Command Prompt permissions
Administrator Command Prompt window opened
Administrative rights are required to write changes to Windows network interface properties.
2
Query network interface names
Target interface name (e.g., 'Ethernet') confirmed
The netsh command requires an explicit interface name parameter.
3
Set static IPv4 address, subnet, and default gateway
IP addressing properties assigned to interface
Establishes basic IP Layer 3 connectivity properties on the client.
4
Set primary static DNS server
DNS server IP assigned to interface
Configures name resolution services for the static adapter profile.
5
Verify applied settings
ipconfig output confirms all configuration parameters
Validates that settings were correctly committed to the Windows networking stack.

Key Concept

Windows Client Netsh IPv4 and DNS Configuration
Question 135Question →

A desktop technician is hardening standalone Windows 11 Pro workstations. The security policy mandates that administrative users must explicitly re-enter their credentials on the Secure Desktop whenever an application requests elevated privileges. In what sequence should the technician perform the steps to configure this behavior via Local Security Policy?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence is to first open the Run dialog box and launch secpol.msc, then navigate to Local Policies > Security Options, next open User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode, and finally select Prompt for credentials on the secure desktop and click OK.
To enforce credential prompting for administrators on the Secure Desktop, the technician must first access the Local Security Policy console via secpol.msc. From there, expanding Local Policies and clicking Security Options brings up UAC policy settings. Opening 'User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode' allows changing the default consent behavior to 'Prompt for credentials on the secure desktop'.

Step-by-Step Solution

1
Launch the Local Security Policy console
The secpol.msc console window opens.
Administrative security options such as UAC elevation behaviors are managed through the Local Security Policy console.
2
Navigate to the Security Options node
The panel displays security policies related to account behavior and UAC settings.
User Account Control policies reside under Local Policies > Security Options in the console hierarchy.
3
Select the administrator elevation policy
The properties dialog window for administrator elevation prompts opens.
The policy named 'User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode' explicitly targets administrator elevation responses.
4
Configure the dropdown option to prompt for credentials on the secure desktop
The policy is updated to require full credential entry on the dimmed Secure Desktop whenever elevation is requested.
This setting enforces re-authentication on the Secure Desktop to prevent automated malware privilege escalation.

Key Concept

Configuring User Account Control elevation policy settings using secpol.msc
Question 136Question →

A field technician is tasked with resolving a corrupt print spooler service issue on a Windows workstation connected to a shared office multifunction printer. Place the following troubleshooting steps in the correct chronological order to clear the print queue and restore normal printing service.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence to clear a stuck Windows print queue is: Stop the Print Spooler service, delete all files in %SystemRoot%\System32\spool\PRINTERS, restart the Print Spooler service, and print a test page to verify functionality.
The proper administrative procedure for resolving a locked or corrupt print queue requires stopping the Print Spooler service first to release OS file locks, deleting the cached spool files (.SHD and .SPL) located in %SystemRoot%\System32\spool\PRINTERS, restarting the service, and sending a test print job to confirm functional recovery.

Step-by-Step Solution

1
Stop the Print Spooler service.
Prevents active locks on spool files.
Windows holds active file handles on documents currently in the queue while the Print Spooler service is running.
2
Delete all files inside the PRINTERS spool folder (%SystemRoot%\System32\spool\PRINTERS).
Purges corrupted shadow (.SHD) and spool (.SPL) files.
Corrupted print jobs remain locked on disk until manually removed from the spooling directory.
3
Start the Print Spooler service.
Initializes a clean print subsystem.
The service must be running to receive and process new print tasks.
4
Send a test print request from the workstation.
Confirms problem resolution.
Verifying functionality ensures the print queue is accepting and transferring jobs to the printer successfully.

Key Concept

Windows Print Spooler Troubleshooting and Queue Remediation
Question 137Question →

A security technician needs to configure a standalone Windows 11 Pro workstation so that standard user accounts are automatically denied elevation requests without displaying a UAC prompt. Place the administrative configuration steps in the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of administrative steps is: 1) Open the Run dialog box, type secpol.msc, and press Enter -> 2) Expand Security Settings > Local Policies and select Security Options -> 3) Double-click User Account Control: Behavior of the elevation prompt for standard users -> 4) Set the local security setting dropdown to Automatically deny elevation requests and click OK.
To enforce auto-denial of elevation requests for standard users on Windows Pro or Enterprise editions, an administrator must launch the Local Security Policy console (secpol.msc), navigate to Security Settings > Local Policies > Security Options, locate 'User Account Control: Behavior of the elevation prompt for standard users', and change its value to 'Automatically deny elevation requests'.

Step-by-Step Solution

1
Launch the Local Security Policy management console using the command secpol.msc.
The Local Security Policy window opens.
Fine-grained UAC behavior rules for distinct account types cannot be set in Control Panel and require the secpol.msc console.
2
Navigate through the policy tree under Security Settings to Local Policies, then select Security Options.
The right pane displays all configurable security option policies.
All administrative User Account Control policies reside within the Security Options folder.
3
Locate and open 'User Account Control: Behavior of the elevation prompt for standard users'.
The policy properties dialog appears.
This specific policy determines whether standard users receive a credential prompt or are blocked directly.
4
Change the security setting to 'Automatically deny elevation requests' and save changes.
Standard users will no longer see UAC prompts when trying to run administrative tasks; requests fail immediately.
Selecting this option fulfills the security requirement to enforce automatic denial without prompt interaction.

Key Concept

Configuring UAC elevation prompt behavior for standard accounts using Local Security Policy (secpol.msc)
Estimated Time:1m 30s
Question 138Question →

A technician is troubleshooting a desktop computer that experiences sudden thermal shutdowns during high CPU processing tasks. The technician suspects improper thermal interface material application and heatsink mounting. Place the following remediation steps in the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct troubleshooting sequence begins with gathering baseline temperature metrics in UEFI/BIOS, discharging flea power after removing power cables, detaching and cleaning the CPU/heatsink surfaces, applying new thermal paste and securing the cooler, and finally stress testing the system to verify thermal stability.
CompTIA hardware troubleshooting methodology requires establishing baseline symptoms first (UEFI hardware monitoring), ensuring safety by cutting power and draining flea power second, performing physical surface preparation and reinstallation third, and finally verifying repair integrity under load.

Step-by-Step Solution

1
Check baseline metrics in UEFI/BIOS
Confirms abnormal idle/load temperatures prior to disassembly.
Establishes a diagnostic baseline according to CompTIA troubleshooting methodology.
2
Disconnect power and drain flea power
Prevents electrical shock and damage to sensitive internal motherboard circuitry.
Safety procedures mandate complete power removal before physical component handling.
3
Unmount cooling unit and clean contact surfaces
Removes old, dried, or improperly applied thermal paste.
Clean metallic surfaces are necessary for optimal thermal transfer.
4
Reapply thermal paste and reinstall heatsink
Restores efficient heat dissipation path from CPU die to heatsink fins.
Correct compound volume and even mounting pressure eliminate thermal gaps.
5
Reboot system and perform load testing
Verifies that CPU temperatures stay within safe operating limits under full load.
Confirming full functionality under stress ensures permanent resolution.

Key Concept

CPU Thermal Management and Safe Component Replacement Procedures
Estimated Time:1m 30s
Question 139Question →

A technician is tasked with removing a malware infection from a workstation. According to the standard CompTIA 7-step malware remediation process, in what sequence should the technician perform the following steps?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence following the CompTIA 7-step malware removal process is: Quarantine the infected system -> Disable System Restore in Windows -> Remediate the infected system by updating anti-malware software and scanning -> Enable System Restore and create a new restore point -> Educate the end user.
The standard CompTIA 7-step malware removal process follows a specific order: 1. Identify malware symptoms, 2. Quarantine infected system, 3. Disable System Restore, 4. Remediate infected systems (update anti-malware / scan and remove), 5. Schedule updates and run scans, 6. Enable System Restore and create a restore point, 7. Educate the end user. Arranging the actions starting with quarantine and ending with user education strictly aligns with this methodology.

Step-by-Step Solution

1
Isolate the compromised computer from the network.
System is quarantined, preventing malware spread.
Quarantine is step 2 of the remediation framework.
2
Disable System Restore.
Prevents Windows from saving infected files in restore points.
Disabling System Restore is step 3 of the remediation framework.
3
Update signatures and perform malware removal.
Infected files are identified, cleaned, or deleted.
Remediation is step 4 of the remediation framework.
4
Re-enable System Restore and create a clean restore point.
Restores system protection capabilities with clean state.
Enabling System Restore is step 6 of the remediation framework.
5
Provide security awareness guidance to the user.
Reduces future infection risks.
User education is step 7 (the final step) of the remediation framework.

Key Concept

CompTIA 7-step Best Practice Methodology for Malware Remediation
Question 140Question →

An IT technician is tasked with decommissioning sensitive magnetic hard drives following standard organizational security procedures. Place the following hardware disposal steps in the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for drive disposal is: 1) Log the hard drive serial numbers in the inventory asset management database, 2) Degauss the magnetic hard drives to neutralize data stored on the platters, 3) Pass the sanitized hard drives through a physical shredder, and 4) Obtain and archive a Certificate of Destruction for regulatory compliance.
The secure decommissioning process begins with administrative logging of serial numbers to maintain audit capability. Magnetic degaussing follows to sanitize data content. Physical shredding then destroys the hardware itself. Finally, obtaining and archiving the Certificate of Destruction validates the completed process for compliance records.

Step-by-Step Solution

1
Identify the initial chain-of-custody administrative requirement.
Documenting serial numbers in the asset database establishes an audit trail before any physical or logical modification.
Tracking must precede destruction so the organization knows which assets are being processed.
2
Perform initial data sanitization on the magnetic media.
Degaussing disrupts the magnetic domains on the platters, sanitizing the stored data.
Sanitizing media prior to physical transport or shredding minimizes data exposure risks.
3
Execute physical destruction of the hardware.
Industrial shredding destroys the physical integrity of the platters and drive electronics.
Physical destruction prevents drive reconstruction.
4
Finalize compliance documentation.
A Certificate of Destruction is generated and logged for legal and regulatory audit purposes.
Final documentation completes the disposal lifecycle and proves compliance.

Key Concept

Chain of Custody and Secure Hardware Disposal Lifecycle
PreviousPage 7 / 22Next
All practice questions — CompTIA A+ (Core 1 & Core 2) | Examkin