Examkin

All practice questions

423 questions

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

A system administrator needs to build a customized Microsoft Management Console (MMC) for junior help desk technicians that consolidates system diagnostic utilities while preventing the technicians from adding or removing snap-ins. What is the correct sequence of steps to create, configure, and save this custom console?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with launching an empty MMC console (mmc.exe), adding the target administrative snap-ins via Add/Remove Snap-in, configuring the console mode to 'User mode - limited access' under Options to lock down modifications, and finally saving the customized file with a .msc extension.
To create a restricted custom administrative tool set, an administrator must first open mmc.exe, add the necessary snap-ins to the console tree, adjust the Console Mode in Options to 'User mode - limited access' to prevent structure modifications, and finally save the file with a .msc extension.

Step-by-Step Solution

1
Launch mmc.exe as administrator.
An empty Microsoft Management Console opens in Author Mode.
Building a custom console requires starting with a baseline MMC executable before adding tools.
2
Select File > Add/Remove Snap-in and add specific management utilities.
The target tools (e.g., Event Viewer, Performance Monitor) are added to the console tree.
Snap-ins provide the actual management capabilities within the custom MMC file.
3
Navigate to File > Options and select 'User mode - limited access'.
The console layout is locked, preventing users from altering snap-in selections or viewing author-mode controls.
Setting user mode ensures junior technicians cannot reconfigure or add unauthorized snap-ins.
4
Select File > Save As and save the file with a .msc extension.
A reusable console file is created for deployment.
Saving as a .msc file allows the customized console to be distributed and launched by help desk personnel.

Key Concept

Microsoft Management Console (MMC) Author Mode vs User Mode Configuration
Estimated Time:1m 30s
Question 102Question →

A technician needs to manually initialize and prepare a secondary unformatted hard drive (Disk 1) with an NTFS volume using the Windows DiskPart command-line utility. Arrange the following DiskPart commands in the correct order to complete this task.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct execution order in DiskPart is: select disk 1, clean, create partition primary, format fs=ntfs quick, and assign.
In DiskPart, task execution requires setting focus first using the selection command for Disk 1. Next, clearing old configuration data prepares the drive. Creating a primary partition establishes the volume boundary, formatting with NTFS writes the file system structures, and assigning a drive letter makes the partition accessible in Windows.

Step-by-Step Solution

1
Set focus to the target physical disk
Disk 1 becomes the active target in DiskPart.
Explicit context selection prevents accidentally modifying the primary operating system disk.
2
Clear existing disk configuration
All partition and volume information is removed from Disk 1.
Wiping the disk structure ensures a clean initialization state.
3
Build a primary partition
An unformatted primary partition is created.
File systems require a partition container to reside on.
4
Format the volume
The partition is formatted with the NTFS file system.
Formatting creates file allocation structures necessary for operating system file storage.
5
Mount the volume with a drive letter
Windows assigns the next available drive letter to the volume.
Assigning a drive letter exposes the drive to Windows File Explorer.

Key Concept

DiskPart command sequence for disk preparation
Question 103Question →

A technician is troubleshooting a high-performance workstation that abruptly shut down during a heavy rendering task. When the power button is pressed, the system power LED blinks briefly and cooling fans turn for a fraction of a second before the system immediately shuts off. Toggling the wall outlet power switch is required before the power button responds again. What is the correct sequential order of troubleshooting steps the technician should perform to isolate this hardware failure?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The technician must first discharge flea power to reset the PSU safety latching circuit, test the power supply independently to verify voltage stability, reduce the computer to a minimal POST configuration inside the case, and finally remove the motherboard to perform a bench test on a non-conductive surface to rule out chassis grounding shorts.
The standard hardware troubleshooting sequence moves from non-invasive resetting to isolated component verification: first discharge residual flea power to clear the PSU safety latch; second, test the standalone PSU outputs; third, reduce internal hardware to a minimal POST configuration; fourth, extract the motherboard to bench-test for chassis grounding shorts.

Step-by-Step Solution

1
Unplug the AC power cord and press/hold the chassis power button for 15-30 seconds.
Discharges flea power from motherboard capacitors and clears the PSU over-current safety latch.
Modern power supplies latch off when a short or thermal event is detected; this latch must be cleared before re-testing.
2
Disconnect all internal power leads from components and test the PSU with a dedicated power tester or multimeter.
Verifies that the power supply can turn on and maintain correct output voltages without triggering instant shutdown.
Confirming power supply integrity prevents misdiagnosing a dead or out-of-spec power unit as a motherboard issue.
3
Reconnect power connectors only to essential components (motherboard, CPU, single RAM module) while keeping all secondary devices disconnected.
Isolates whether an auxiliary peripheral (such as a graphics card or storage drive) is pulling down a voltage rail.
Minimal boot isolation efficiently identifies faulty add-in hardware without unnecessary teardown.
4
Remove the motherboard from the metal chassis and conduct a bare-bones bench test on a non-conductive mat.
Eliminates chassis contact as a cause of electrical short circuits and allows close visual inspection of power distribution components.
If minimal boot fails inside the case, removing the board isolates grounded standoff shorts and board-level component damage.

Key Concept

CompTIA sequential hardware troubleshooting for power latching and short-circuit isolation
Question 104Question →

A technician boots a non-responsive Windows workstation into the Windows Recovery Environment (WinRE) Command Prompt to repair system file corruption on the main Windows installation volume (drive D:). Place the following administrative command-line steps in the correct chronological order to safely check disk integrity, restore the offline component store, and repair system files.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of operations is: first, identify the OS drive letter in WinRE; second, run chkdsk D: /f to fix filesystem errors; third, execute dism /image:D:\ /cleanup-image /restorehealth to restore the component store; fourth, run sfc /scannow /offbootdir=D:\ /offwindir=D:\windows to repair system binaries.
Systematic offline troubleshooting requires identifying the active OS volume letter, ensuring disk filesystem stability with chkdsk, repairing the servicing repository via dism /image:D:\ /cleanup-image /restorehealth, and finally replacing corrupt system files using sfc with /offbootdir and /offwindir flags.

Step-by-Step Solution

1
Determine drive letter assignment for the Windows installation volume in WinRE.
The target volume is verified as drive D:.
WinRE dynamically assigns partition letters that may differ from standard online drive letters.
2
Run chkdsk D: /f.
Volume sector anomalies and file record errors on drive D: are resolved.
Running image repair tools on a corrupted filesystem can crash utilities or lead to incomplete repairs.
3
Run dism /image:D:\ /cleanup-image /restorehealth.
The offline WinSxS component store on drive D: is scanned and restored to health.
SFC depends on a healthy component store to serve as the reference source for corrupt file replacement.
4
Run sfc /scannow /offbootdir=D:\ /offwindir=D:\windows.
Protected Windows system files on drive D: are scanned and restored using clean files from the component store.
With the reference component store repaired, SFC can successfully replace corrupted system binaries.

Key Concept

Offline Windows Command-Line System Repair Sequence
Question 105Question →

A desktop support technician needs to manually install a new line-of-business application on a user's Windows 11 workstation. What is the correct sequence of steps the technician should follow from initial preparation through final verification?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with checking system architecture and hardware compatibility, followed by launching the installer using elevated administrative credentials, completing the wizard steps to install files, and ending with opening the application to verify operational readiness.
The correct operational sequence follows standard IT support practice: prerequisites are checked first, elevation is requested second, software options are configured and installed third, and functionality is verified last.

Step-by-Step Solution

1
Verify hardware and operating system compatibility.
Ensures the operating system supports the application installer.
Attempting to install incompatible software (such as 64-bit software on a 32-bit OS) will fail.
2
Elevate setup file execution using 'Run as administrator'.
Bypasses standard user restrictions and grants necessary system write permissions.
Standard user privileges cannot modify system registry hives or protected directory trees.
3
Navigate through the setup wizard options.
Copies application binaries to disk and registers system shortcuts.
Application components must be completely extracted and written to target locations before execution.
4
Open the application to verify functionality.
Confirms the application initializes without runtime errors.
Post-installation verification ensures the installation process succeeded end-to-end.

Key Concept

Standard Application Installation and Configuration Workflow
Question 106Question →

A network technician is troubleshooting a wired desktop client that has completely lost network access. Sequence the following diagnostic and troubleshooting steps according to the standard bottom-up OSI model methodology.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct troubleshooting sequence follows the standard bottom-up approach: first inspect physical Ethernet cables and NIC link lights, second execute `ipconfig /all` to check IP addressing, third ping the local default gateway, and fourth ping an external FQDN to test DNS resolution.
Following the standard bottom-up OSI troubleshooting approach requires inspecting physical layer components (cables and link status lights) first, verifying local IP configuration settings (`ipconfig`), confirming local gateway reachability (`ping gateway`), and lastly testing higher-level services like DNS name resolution (`ping FQDN`).

Step-by-Step Solution

1
Inspect physical connections and LED indicators
Verifies Layer 1 physical media connectivity.
Physical layer issues (such as unplugged cables or unlit link lights) must be identified and resolved prior to higher-layer testing.
2
Execute `ipconfig /all`
Displays network configuration parameters.
Determines if the client holds a valid static/DHCP IP address or an automatic private IP address (APIPA).
3
Ping the default gateway
Tests local network ICMP reachability.
Confirms that the workstation can successfully communicate across the local network switch to the router.
4
Ping external domain name (FQDN)
Verifies name resolution (DNS) and WAN connectivity.
Validates that high-level network services and Internet routing functions operate properly.

Key Concept

Bottom-up network troubleshooting methodology for wired network issues.
Question 107Question →

A network technician needs to manually assign a static IPv4 address, subnet mask, and default gateway on a Windows client workstation using the classic Network Connections applet. Place the configuration 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 sequence to manually configure a static IPv4 address using Network Connections is: 1) Open the Run dialog box, enter ncpa.cpl, and press Enter; 2) Right-click the active network interface card (NIC) and select Properties; 3) Select Internet Protocol Version 4 (TCP/IPv4) from the list of components and click Properties; 4) Select the 'Use the following IP address' option and type the assigned IPv4 address, subnet mask, and default gateway.
Configuring a static IPv4 address requires opening the Network Connections management interface via ncpa.cpl, accessing the properties of the active adapter, opening the Internet Protocol Version 4 (TCP/IPv4) properties, and selecting the option to manually enter the IP address, subnet mask, and default gateway.

Step-by-Step Solution

1
Launch the Network Connections applet by running ncpa.cpl in the Run dialog.
The Network Connections window opens displaying available physical and virtual adapters.
Executing ncpa.cpl directly opens the adapter control panel menu.
2
Open the configuration properties of the specific network adapter.
The Ethernet Properties dialog box appears.
Protocol bindings and network settings are managed on a per-adapter basis.
3
Locate and open the properties for the IPv4 protocol stack.
The Internet Protocol Version 4 (TCP/IPv4) Properties window opens.
Static IP addresses, subnet masks, and default gateways are configured within IPv4 properties.
4
Enable manual IP assignment and populate the network fields.
The workstation is assigned a static IPv4 configuration.
By default, Windows uses dynamic addressing (DHCP); selecting 'Use the following IP address' enables manual parameter entry.

Key Concept

Windows Client Static IPv4 Address Configuration
Question 108Question →

A system technician receives an automated alert indicating that a single drive has failed within a server's hot-swappable hardware RAID 5 array, causing the array to operate in a degraded state. Place the necessary steps for replacing the faulty drive and restoring array redundancy in the correct sequential order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The proper sequence begins with identifying the specific faulty drive via the controller software and chassis lights, followed by removing the failed drive, inserting a replacement drive of equal or greater capacity, and finally verifying that the automated RAID rebuild completes.
Correct RAID servicing requires identifying the exact failed disk first to prevent removing an active member disk. Once confirmed, the hot-swappable drive carrier is unlatched and removed. Inserting a qualified replacement drive triggers the hardware controller's automated parity reconstruction, which must be monitored until completion to confirm full redundancy has been restored.

Step-by-Step Solution

1
Locate the specific failed disk drive using status LEDs and hardware controller software.
The exact physical bay containing the faulted drive is verified without disrupting healthy operational drives.
Removing an active healthy drive from a degraded RAID 5 array will result in total array failure and data loss.
2
Disengage the drive latch mechanism and extract the failed disk from the hot-swap enclosure.
The failed physical media is separated from the backplane connector.
Hot-swappable hardware allows disengaging drive carriers while the system remains powered on.
3
Slide the replacement drive into the empty bay and lock the retention lever.
The new drive establishes physical and electrical connection with the RAID controller backplane.
The controller requires a functional physical disk of equal or greater storage capacity to write reconstructed parity data.
4
Access the RAID controller management interface to check rebuilding status.
The controller parity reconstruction process completes, returning the volume state from Degraded to Optimal.
Verifying completion ensures full fault tolerance is successfully restored.

Key Concept

Hot-Swappable RAID 5 Failed Drive Replacement Sequence
Question 109Question →

A technician is preparing to perform an operating system upgrade on a user's desktop computer. Place the following installation 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 is verifying system hardware requirements, backing up critical user files, executing the operating system setup wizard, and finally installing missing drivers and operating system updates.
The standard deployment procedure requires checking hardware prerequisites first, ensuring data safety via backups second, executing the OS setup program third, and finalizing the system with updated drivers and security updates fourth.

Step-by-Step Solution

1
Check hardware specs against minimum OS requirements.
Confirms system meets memory, processor speed, disk space, and firmware/TPM prerequisites.
Starting an installation on incompatible hardware leads to installation failures.
2
Perform a complete data backup.
Protects user files against corruption or accidental erasure during the upgrade process.
Data protection is mandatory before making changes to drive partitions or system files.
3
Execute the OS installation media.
Installs operating system core files onto the target disk.
The main installation phase replaces or upgrades system files on the host computer.
4
Perform post-installation configuration, driver updates, and OS patching.
Ensures all hardware components function correctly and the OS is secure.
Base OS installations often lack recent device drivers or cumulative security patches.

Key Concept

Sequential best-practice steps for OS installation and upgrade preparation
Question 110Question →

A field technician is assigned a support ticket regarding a shared departmental laser printer that produces output where the black toner easily wipes off the paper when touched. Place the following troubleshooting steps in the correct order according to the standard CompTIA troubleshooting methodology, from first step to last step.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence follows the standard six-step CompTIA troubleshooting methodology: (1) Identify the problem by gathering symptoms and user input, (2) Establish a theory of probable cause, (3) Test the theory to confirm the fuser defect, (4) Establish a plan of action and implement the solution by replacing the fuser assembly, (5) Verify full system functionality by printing test pages, and (6) Document findings, actions, and outcomes in the support ticket.
The correct order reflects the CompTIA troubleshooting framework: Step 1 (Identify the problem), Step 2 (Establish a theory of probable cause), Step 3 (Test the theory to determine cause), Step 4 (Establish a plan of action and implement the solution), Step 5 (Verify full system functionality), and Step 6 (Document findings, actions, and outcomes).

Step-by-Step Solution

1
Gather symptom information and review user observations.
Identified that toner fails to permanently fuse to paper media.
CompTIA methodology requires identifying the problem first through symptom analysis and user questioning.
2
Develop a plausible root-cause hypothesis.
Attributed the issue to a failing fuser heating element.
CompTIA methodology requires establishing a theory of probable cause after symptom identification.
3
Run targeted hardware diagnostic tests.
Confirmed the fuser unit fails to reach operational temperature.
CompTIA methodology requires testing the theory to verify the true cause before performing hardware replacement.
4
Perform component replacement.
Installed a functional fuser assembly.
CompTIA methodology requires establishing a plan of action and implementing the solution.
5
Run test pages and obtain user confirmation.
Verified toner adheres properly without smudging.
CompTIA methodology requires verifying full system functionality after implementing a fix.
6
Complete technical ticket documentation.
Entered complete incident data into the service desk system.
CompTIA methodology requires documenting findings, actions, and outcomes as the final step.

Key Concept

CompTIA 6-Step Troubleshooting Methodology applied to Printer Hardware Issues
Question 111Question →

An IT technician is preparing to perform an in-place upgrade on a corporate workstation from Windows 10 Pro to Windows 11 Pro. The upgrade must preserve all existing user files, system settings, and installed applications. In what chronological sequence should the technician execute the steps for this upgrade process?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence begins with assessing hardware compatibility (TPM 2.0 and Secure Boot), performing a full data backup, launching setup.exe from inside the running operating system, choosing the option to retain files and applications in the setup wizard, and finishing with post-installation system updates and driver checks.
The correct sequence followsCompTIA IT deployment best practices for in-place OS upgrades: first assess system hardware readiness (such as TPM 2.0 and Secure Boot), second back up user data to external storage, third execute setup.exe from within the running desktop environment, fourth configure setup options to keep files and applications, and fifth perform post-installation validation including Windows Update and driver checks.

Step-by-Step Solution

1
Perform pre-upgrade compatibility assessment
Confirms the workstation meets mandatory hardware requirements such as TPM 2.0, Secure Boot, and supported CPU models.
Verifying compatibility early avoids starting an upgrade that will fail mid-installation due to unverified hardware requirements.
2
Back up critical user data and system state
Creates a secure restore point on secondary storage.
Standard operational procedures mandate securing user data before executing major system changes.
3
Execute setup.exe from within the host OS
Launches the Windows 11 setup wizard while maintaining the current user session.
An in-place upgrade requires running installer binaries inside the running OS; booting directly from installation media would default to a clean or custom installation.
4
Select data retention configuration in the wizard
Instructs setup to migrate user profiles, configurations, and installed applications to the new OS.
Preserving existing user state defines an in-place upgrade as opposed to a destructive clean install.
5
Perform post-installation validation and patching
Verifies hardware driver functionality and installs current security patches.
Post-install update execution ensures full driver compatibility and system stability following an OS upgrade.

Key Concept

In-Place OS Upgrade Workflow and Readiness Procedures
Question 112Question →

A Windows 11 client workstation is unable to access an internal corporate web application by its domain name. A tier 2 support technician needs to isolate the root cause by following a systematic bottom-up network diagnostic methodology using standard Windows command-line tools. Place the diagnostic actions in the correct logical sequence, starting from verifying the local system protocol stack up to testing domain name resolution.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with testing the local loopback address (ping 127.0.0.1), followed by testing the local adapter IP address, pinging the local default gateway, pinging the destination server's IP address directly, and finally testing DNS name resolution using nslookup.
Systematic bottom-up troubleshooting requires testing local host components before moving outward across network boundaries. The sequence starts internally with the loopback adapter (127.0.0.1), progresses to the local assigned IP, verifies the local default gateway, checks IP routing to the destination IP address, and concludes by validating DNS host name resolution using nslookup.

Step-by-Step Solution

1
Verify local TCP/IP stack initialization
ping 127.0.0.1 confirms software protocol stack integrity.
Eliminates local OS network stack corruption as the issue before testing hardware or physical links.
2
Verify local network adapter binding and driver
pinging the local IPv4 address (192.168.1.105) checks NIC driver response.
Confirms the local network interface card hardware and protocol bindings are operating properly.
3
Verify local subnet default gateway connection
pinging 192.168.1.1 tests local switch and router interface communication.
Ensures the host can communicate across the local broadcast domain/VLAN.
4
Verify layer 3 inter-subnet routing to target destination
pinging the remote server IP (10.20.4.50) tests IP packet transport across routers.
Isolates network transport and routing issues while bypassing application-layer name resolution.
5
Verify DNS host name resolution service
nslookup intranet.company.local tests FQDN resolution to IP address mapping.
Determines if name resolution or DNS client configuration is failing after network transport connectivity is confirmed.

Key Concept

Bottom-up TCP/IP network troubleshooting methodology on Windows clients
Question 113Question →

A systems engineer is preparing a automated enterprise network deployment of Windows to 200 new workstations. Place the steps for image preparation, network service configuration, and client deployment 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 image-based network deployment is: 1) Run 'sysprep.exe /generalize /oobe /shutdown' on the reference OS -> 2) Boot reference machine into WinPE and capture the volume using DISM -> 3) Upload the .wim file to WDS and configure DHCP Options 66 and 67 -> 4) Set target client UEFI firmware boot order to network/PXE -> 5) Execute target client PXE boot to retrieve WinPE via TFTP and apply unattend.xml.
The deployment process strictly follows a prepare-capture-host-configure-deploy workflow: First, the reference OS must be generalized using sysprep.exe /generalize to remove unique SIDs and driver bindings. Second, the offline partition is captured into a .wim file using DISM in WinPE. Third, the .wim file is loaded onto WDS while DHCP Options 66 (boot server IP) and 67 (bootfile name) are configured to direct clients. Fourth, target client devices are set to PXE boot in UEFI. Finally, the target machines boot via PXE, receive boot parameters from DHCP/TFTP, load WinPE, and execute the unattended installation file.

Step-by-Step Solution

1
Prepare the reference operating system image.
System SIDs and hardware-specific configurations are stripped using Sysprep /generalize.
Capturing an un-generalized system will cause SID duplication errors across domain clients.
2
Capture the reference disk image.
A standardized .wim file is generated via DISM from WinPE.
DISM requires the reference volume to be offline or booted into WinPE to safely capture file structures.
3
Configure distribution infrastructure.
WDS holds the install image and DHCP directs clients via Options 66 and 67.
PXE network clients depend on DHCP option tags to locate the TFTP server IP address and boot file name.
4
Prepare client hardware.
Target devices are set to attempt network boot via PXE.
UEFI must send a PXE broadcast request during early POST before attempting local storage boot.
5
Execute unattended deployment.
Target machines download WinPE and silently install the customized image.
The unattended file automates OS customization passes (specialize and oobeSystem) without technician intervention.

Key Concept

Automated Network Deployment Sequence (Sysprep -> DISM Capture -> WDS/DHCP PXE -> Client Unattended Install)
Question 114Question →

A technician is troubleshooting an office desktop computer that fails to complete POST following a brief electrical surge. The system fans spin and power LEDs illuminate, but the monitor displays no image and no diagnostic beep codes are emitted. In what sequence should the technician perform these diagnostic steps to isolate the fault according to CompTIA hardware troubleshooting methodology?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The technician should first disconnect all non-essential internal and external components to create a minimal boot configuration. Next, clear the CMOS memory to resolve corrupted BIOS/UEFI settings. Following that, isolate memory issues by testing a single RAM module in the primary slot. Finally, perform an invasive physical inspection of the CPU and motherboard socket pins if the POST failure persists.
Effective hardware troubleshooting progresses from least-invasive to most-invasive steps: establishing a bare-bones state by removing peripherals and extra drives, resetting BIOS settings via CMOS, testing RAM configurations individually, and lastly removing the CPU cooler to inspect socket pins directly.

Step-by-Step Solution

1
Disconnect peripherals, storage drives, and non-essential expansion cards.
Isolates the boot environment to core components (motherboard, CPU, RAM, power supply).
Standard diagnostic methodology dictates removing external variables and secondary hardware first.
2
Perform a CMOS reset via onboard jumper or RTC battery removal.
Clears invalid hardware configuration parameters or firmware corruption in NVRAM.
Power events frequently corrupt transient system settings without causing physical hardware destruction.
3
Test system boot with a single memory module in the primary channel slot.
Determines whether a specific RAM module or DIMM slot is preventing memory training during POST.
RAM testing is non-invasive and systematically pinpoints memory-channel faults.
4
Remove the heatsink and CPU to inspect socket pins and pads.
Verifies structural and electrical pin integrity on the socket grid array.
Reseating or inspecting the CPU requires thermal compound cleanup and component disassembly, so it is performed last.

Key Concept

Methodological order of isolation for core hardware component failures during POST diagnostics
Estimated Time:1m 30s
Question 115Question →

A technician needs to manually install a desktop application on a Windows workstation. Place the standard steps of the application installation workflow 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 begins with verifying system requirements and architecture compatibility, followed by running the installer with administrative privileges, completing the setup wizard configuration, and finally testing application functionality.
The standard application installation process begins by verifying system requirements and operating system architecture (32-bit vs 64-bit) to ensure compatibility. Next, the setup executable is launched using administrative privileges (Run as Administrator) to grant write access to system directories. After elevation, the technician configures settings within the installation wizard. Finally, the application is launched post-install to verify functional integrity.

Step-by-Step Solution

1
Check software prerequisites against system specifications.
System compatibility is confirmed prior to installation attempt.
Prevents installation failures caused by architecture mismatches or inadequate system resources.
2
Elevate permissions to execute the setup package.
Installer gains administrative permissions to modify Program Files and the Windows Registry.
Standard user context lacks permission to modify protected system locations.
3
Proceed through wizard customization prompts.
Application files are copied to specified directories.
Defines installation parameters such as destination path and shortcut options.
4
Launch and test the installed program.
Application opens successfully and verifies deployment.
Ensures the application operates properly before turning the workstation over to the user.

Key Concept

Standard Manual Application Installation Sequence
Estimated Time:1m 0s
Question 116Question →

An IT technician is tasked with setting up an automated USB-based deployment process to perform unattended Windows installations on offline workstations. Place the steps required to prepare the answer file and execute the unattended installation 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 starts by opening install.wim in Windows SIM to create a catalog file, followed by configuring the answer file settings, validating the answer file for errors, saving it as autounattend.xml to the root of the USB drive, and finally booting the target computer from the USB drive to execute setup.
The correct sequence follows the standard Windows System Image Manager (SIM) workflow for creating an unattended deployment media: catalog generation from the WIM image file, answer file configuration, syntax validation, saving as autounattend.xml on the root directory of the installation media, and finally booting the target workstation to execute the automated installation.

Step-by-Step Solution

1
Load install.wim into Windows System Image Manager (SIM) to generate the image catalog file (.clg).
The component list and configurable settings for the OS image become available for selection.
Windows SIM requires a catalog file to display configurable OS options and validate dependencies.
2
Build a new answer file by configuring settings across deployment passes (e.g., windowsPE, oobeSystem).
The custom answer file populated with automated deployment instructions is created.
Component settings define automated actions such as disk partitioning, administrator account creation, and regional preferences.
3
Run validation check on the answer file within Windows SIM.
Any syntax errors, invalid values, or missing mandatory settings are identified and fixed.
Unvalidated answer files can cause Windows Setup to fail or prompt for manual input mid-installation.
4
Save the file named autounattend.xml to the root directory of a bootable installation USB drive.
The answer file is positioned in the exact path monitored by the Windows Setup engine during startup.
Windows Setup scans the root directory of removable storage devices specifically for the file name autounattend.xml.
5
Insert the USB drive into the target computer and boot to the installation media.
Windows Setup detects autounattend.xml and runs the complete installation without requiring user interaction.
Executing the setup from media triggers automated script processing defined in the answer file.

Key Concept

Unattended OS Installation and Answer File (autounattend.xml) Workflow
Question 117Question →

A desktop support technician is deploying a specialized line-of-business financial application onto a newly provisioned Windows 11 workstation. The application requires elevated administrator privileges to write to system directories during installation, creates shared configuration files in C:\ProgramData\FinanceApp, and requires database connection string settings to be established before standard domain users can operate it. Place the following installation and post-installation 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 sequence starts with verifying system hardware and OS architecture compatibility, followed by executing the installer using administrative elevation, completing the installation wizard, configuring ProgramData file settings and NTFS access permissions, and finally testing application launching under a non-administrative standard user profile.
Proper deployment procedures dictate validating requirements first, installing binaries with elevated rights second, configuring custom data paths and security permissions third, and performing final user verification last under normal user security contexts.

Step-by-Step Solution

1
Perform initial pre-installation check of system hardware and OS architecture.
Ensures the workstation meets minimum CPU, RAM, disk space, and 64-bit environment requirements.
Installing software without validating minimum requirements can corrupt software state or cause immediate runtime failures.
2
Run installer package with administrative elevation.
Satisfies UAC prompts and provides necessary write tokens for system directories.
Standard user accounts lack rights to write to System32 or Program Files directories.
3
Complete core installation wizard.
Extracts application binaries and creates folder paths including C:\ProgramData\FinanceApp.
Application configuration files cannot be edited until the installer creates the destination folders and configuration templates.
4
Modify configuration files in ProgramData and update security access control lists (NTFS permissions).
Database parameters are stored and standard users are granted necessary permissions to read/write operational data.
Without adjusting default NTFS permissions on shared ProgramData folders, standard users will encounter Access Denied errors upon opening the application.
5
Log in as standard user and test application functionality.
Validates that the software functions correctly without requiring permanent administrative elevation.
Final validation confirms least privilege principles and ensures complete deployment success for end users.

Key Concept

Application Installation and Configuration Workflow
Estimated Time:2m 0s
Question 118Question →

A systems administrator needs to create a restricted, customized administration tool for a junior technician that contains only the Event Viewer and Device Manager snap-ins. The technician should be able to view these utilities but prevented from modifying the console layout. Sequence the administrative steps required to configure and deploy this custom Microsoft Management Console (MMC).

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts by opening a blank console using mmc.exe, adding Event Viewer and Device Manager via Add/Remove Snap-in, changing the Console mode to User mode - limited access under Options, and saving the result as an .msc file.
Building a restricted MMC custom console requires initializing the blank MMC executable (mmc.exe), adding the target snap-ins (Event Viewer and Device Manager), configuring the Console mode under Options to User mode (limited access) to lock the layout, and finally saving the customized workspace as an .msc file.

Step-by-Step Solution

1
Launch the Microsoft Management Console shell.
An empty MMC shell opens in Author mode by default.
Custom snap-in consoles must be constructed from an unconfigured MMC root.
2
Add Event Viewer and Device Manager snap-ins.
The specified administrative utilities are populated in the console tree.
Administrative utilities must be added before locking down the user interface.
3
Configure the console security and mode settings.
The Console mode is changed from Author mode to User mode - limited access.
This mode prevents users from adding/removing snap-ins or saving layout modifications.
4
Save and deploy the customized console file.
A standalone .msc file is created for distribution.
Saving finalizing the configuration so the junior technician can launch the pre-configured environment directly.

Key Concept

Microsoft Management Console (MMC) Author vs. User Mode configuration and .msc file creation.
Question 119Question →

A technician is assigned to service a desktop workstation whose hardware RAID 1 array is operating in a degraded state due to a drive fault. The system hardware does not support hot-swapping. What is the correct order of steps the technician should take to replace the faulty drive and restore full redundancy to the array?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The proper sequence to replace a non-hot-swappable drive in a degraded RAID 1 array is to first identify the faulty drive using the RAID management utility, shut down the system and disconnect power, swap out the bad drive for a healthy replacement, power on the system and configure the controller to begin the rebuild, and finally verify that the rebuild finishes with an optimal array status.
When dealing with a non-hot-swappable system, procedures must be strictly ordered to preserve data integrity and system safety. First, diagnose and identify the exact drive that failed within the array controller management tool. Second, perform a clean shutdown and power removal to enable safe hardware access. Third, physically replace the failed disk with a compatible replacement. Fourth, power on and access the RAID utility to add the new disk to the array and trigger the sync/rebuild process. Finally, verify that the rebuild operation completes and the array transitions back to an optimal status.

Step-by-Step Solution

1
Identify the specific failed disk slot in the software console
Confirmed physical identity of the faulty drive
Prevents accidental removal of the surviving healthy drive, which would cause complete array failure.
2
Safely shut down the workstation and disconnect main power
System powered down safely for internal servicing
Cold-swap systems require complete power interruption before disconnecting internal data and power cables.
3
Unmount the failed drive and install the replacement drive
Fresh drive installed in the designated drive slot
Provides a functional disk of appropriate capacity to accept mirrored data.
4
Boot into the RAID controller utility and set the new drive to rebuild
Data rebuild process starts automatically or manually
The RAID controller must be commanded to copy existing data from the surviving drive to the new drive.
5
Verify that the rebuild process finishes completely
Array status changes from degraded to optimal
Confirms fault tolerance has been fully restored to the storage volume.

Key Concept

Cold-swappable RAID drive replacement and volume rebuild procedure
Question 120Question →

A technician is performing a clean installation of Windows on a computer using a bootable USB flash drive. Place the following installation 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 installation sequence begins with configuring UEFI/BIOS boot priority to load the USB drive, followed by choosing regional settings in Windows Setup, selecting a Custom installation to target unallocated storage, and concluding with Out-of-Box Experience (OOBE) configuration.
A standard clean OS installation follows a linear progression: first, system firmware (UEFI/BIOS) must boot from the installation media; second, initial installer options like language and keyboard layout are selected; third, a custom installation path is chosen to format/select the target storage partition; and finally, post-install account and privacy setup occurs in the Out-of-Box Experience (OOBE).

Step-by-Step Solution

1
Configure UEFI/BIOS boot order.
The computer boots directly into the USB installer media.
The computer cannot run the installer until the firmware is instructed to boot from the flash drive.
2
Specify localization preferences.
Language and keyboard settings are initialized for the setup environment.
This is the first interactive prompt after booting into the installer.
3
Choose Custom installation and target storage.
Windows setup copies system files onto the clean target drive.
Clean installations require selecting the custom pathway to select unallocated space.
4
Configure Out-of-Box Experience settings.
User accounts, network connections, and privacy preferences are established.
OOBE runs automatically after system files finish copying and the machine reboots.

Key Concept

OS Clean Installation Procedure
PreviousPage 6 / 22Next
All practice questions — CompTIA A+ (Core 1 & Core 2) | Examkin