Examkin

All practice questions

423 questions

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

A systems administrator is responding to an incident where a corporate database server suddenly lost network access to its storage area network (SAN). Place the following administrative actions in the correct sequential order according to the standard CompTIA troubleshooting methodology, from earliest step to latest step.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order follows the standard troubleshooting workflow: first gathering symptoms, followed by formulating a cause theory, testing that theory, and finally documenting the resolution.
The correct sequence adheres strictly to the CompTIA troubleshooting framework: 1. Identify the problem (gathering symptoms and logs), 2. Establish a theory of probable cause (hypothesizing corrupt configurations), 3. Test the theory to determine cause (rolling back settings on a test port), and 6. Document findings, actions, and outcomes (updating the ticketing system).

Step-by-Step Solution

1
Identify the problem by gathering symptoms and questioning users.
System logs and user accounts reveal specific port communication error messages.
Troubleshooting cannot begin effectively without fully identifying the scope and symptoms of the issue.
2
Establish a theory of probable cause.
Corrupt Fibre Channel port configurations from a recent update are hypothesized as the root cause.
Formulating a targeted theory directs testing efforts efficiently.
3
Test the theory to determine the exact cause.
Rolling back settings on a test port confirms the configuration issue was responsible.
Testing validates whether the hypothesis is correct before implementing full-scale changes.
4
Document findings, actions, and outcomes.
The ticketing system and internal wiki are updated with the issue breakdown and fix.
Proper documentation ensures organizational memory and assists future troubleshooting.

Key Concept

CompTIA 6-Step Troubleshooting Methodology
Estimated Time:1m 30s
Question 82Question →

A systems technician needs to log long-term CPU utilization data on a Windows 11 Pro workstation to troubleshoot intermittent slowdowns. Place the steps required to build and run a custom Performance Counter Data Collector Set in Windows Performance Monitor in the correct order.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order is: 1. Open Performance Monitor with administrative privileges. 2. Expand Data Collector Sets, right-click User Defined, and select New > Data Collector Set. 3. Name the set, select Create manually (Advanced), and choose Performance counter data log. 4. Add the Processor \ % Processor Time counter and configure the sample interval. 5. Complete the wizard, right-click the new Data Collector Set, and select Start.
To create a custom performance tracking log in Windows, an administrator must first open Performance Monitor with elevated rights. Next, navigate to Data Collector Sets > User Defined to initiate a new set. Choosing manual creation allows the administrator to specify a Performance counter data log, select the desired counters (such as Processor \ % Processor Time) and sample interval, and finally complete the wizard and start the collector set.

Step-by-Step Solution

1
Launch perfmon.msc with administrative privileges.
Performance Monitor opens with permissions to create administrative logging tasks.
Creating system data collector sets requires elevated permissions.
2
Navigate to Data Collector Sets > User Defined and initiate a new set.
The Create New Data Collector Set Wizard opens.
User Defined is the standard repository for custom administrator-created logs.
3
Select manual creation and set the type to Performance counter data log.
The wizard transitions to the performance counter selection page.
Manual configuration ensures custom counters rather than template defaults are configured.
4
Select the Processor object's % Processor Time counter and define the sampling frequency.
The specific metric and sampling interval are attached to the collector set.
This establishes which system resource metrics will be monitored.
5
Finish the wizard and explicitly start the collector set.
Performance Monitor begins collecting and writing metric data to disk.
Data collection does not start automatically upon finishing wizard creation.

Key Concept

Creating and starting custom Performance Counter Data Collector Sets in Windows Performance Monitor.
Question 83Question →

A network administrator receives an alert indicating that a server hosting a hardware RAID 5 array is operating in a degraded status following a single disk failure. The server platform supports hot-swappable storage drives. Place the standard administrative steps for replacing the failed drive and restoring array redundancy into the correct sequential order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for replacing a failed hot-swappable RAID 5 drive is: 1) Identify the failed drive bay using the controller utility and chassis LED, 2) Remove the failed drive while the system is powered on, 3) Install a replacement drive of equal or greater capacity, 4) Initiate or confirm the rebuild in the RAID management console, and 5) Monitor the rebuild process until optimal array status is restored.
The correct operational sequence begins with identifying the specific failed drive using management tools and physical lights to avoid disturbing working drives. Next, the technician hot-swaps the physical hardware by unlatching the failed disk while online and inserting a replacement drive meeting capacity specifications. Afterward, the technician uses the RAID controller utility to start or confirm the rebuild operation. Finally, monitoring the array confirms that parity reconstruction finishes successfully and array health returns to optimal.

Step-by-Step Solution

1
Locate failed drive bay
Identified physical slot containing the failed member disk
Prevents accidental removal of operational drives which would break the RAID 5 array completely.
2
Hot-swap extraction
Failed drive removed from powered-on system
Leverages hot-swappable backplane capability to maintain system uptime during maintenance.
3
Drive installation
New disk physically seated and locked in chassis bay
Provides the necessary raw storage geometry required by the RAID volume.
4
Initiate RAID rebuild
Controller begins recalculating parity data onto the new disk
Reconstructs lost data block parity from remaining operational drives.
5
Verify optimal status
Array status returns to healthy/optimal
Confirms fault tolerance and redundancy are fully restored.

Key Concept

RAID 5 Hot-Swap Drive Replacement and Parity Rebuild Procedure
Question 84Question →

A desktop technician needs to perform a clean operating system installation on a computer that currently holds user files. Arrange the following steps of the OS 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 sequence for a clean OS installation is: first back up user data, next configure BIOS/UEFI to boot installation media, then format/select the target storage partition, followed by completing the Out-of-Box Experience (OOBE), and finally installing hardware drivers and operating system updates.
A clean OS installation must follow a logical sequence: data preservation (backup) occurs first to prevent data loss; firmware configuration (BIOS/UEFI) enables booting the installer; disk partitioning prepares the target drive; the setup wizard (OOBE) builds user accounts; and driver/update installation finalizes system configuration.

Step-by-Step Solution

1
Preserve existing user data
User files are stored safely on external media
Clean installations erase existing storage partitions, making pre-installation backup essential.
2
Modify boot order in system firmware
The system boots directly into the installer wizard from USB/optical media
The computer needs to boot from the installation media instead of the current internal drive.
3
Configure storage drive partitions
A fresh target drive partition is created and ready for file expansion
Clean installation requires selecting an unallocated target partition or wiping existing system partitions.
4
Run through OOBE administrative choices
The operating system user shell and account profile are created
The installer reboots into OOBE where administrative accounts, network configuration, and privacy choices are set.
5
Perform post-installation maintenance
All hardware functions optimally and security vulnerabilities are patched
Fresh installations require updated vendor drivers for graphics/network adapters and current OS updates.

Key Concept

Standard Clean OS Installation Workflow
Question 85Question →

A desktop workstation in an office environment fails to connect to network resources after a desk rearrangement. A technician decides to troubleshoot the issue using a bottom-up approach following the OSI model layers. In what order should the technician perform the following diagnostic steps, starting from Layer 1 (Physical) up through Layer 3 (Network)?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with checking physical cable connections and link lights (Layer 1), followed by verifying switch port settings and MAC/VLAN configurations (Layer 2), inspecting the local host's IP address assignment via `ipconfig` (Layer 3 configuration), and finally testing IP reachability to the gateway using `ping` (Layer 3 communication).
A bottom-up troubleshooting methodology starts at the Physical Layer (Layer 1), verifying cable connections and link lights. It then moves to the Data Link Layer (Layer 2) to check switch port status and VLAN configuration, followed by the Network Layer (Layer 3) to inspect host IP addressing (`ipconfig /all`) and test end-to-end ICMP connectivity (`ping`).

Step-by-Step Solution

1
Check physical layer components (Layer 1).
Confirm Ethernet cable is securely connected and NIC link LEDs illuminate.
Troubleshooting bottom-up requires ensuring physical media and signaling are operational before checking logical configurations.
2
Verify data link layer components (Layer 2).
Check switch port LEDs and VLAN assignment.
Layer 2 framing and VLAN tagging must function properly for frames to reach network services.
3
Inspect local network layer configuration (Layer 3).
Determine if a valid DHCP IP address or an APIPA (169.254.x.x169.254.x.x) address is assigned.
Valid IP addressing is required for host communication beyond the physical/data link layer.
4
Test network layer reachability (Layer 3).
Verify ICMP echo responses from the default gateway.
Pinging the gateway tests active IP routing and confirms packets can leave the local subnet.

Key Concept

Bottom-up troubleshooting methodology follows the OSI model from Physical Layer (Layer 1) to Data Link Layer (Layer 2) and Network Layer (Layer 3).
Estimated Time:1m 30s
Question 86Question →

A systems administrator is configuring a new computer to install Windows 11 across a local network using Preboot Execution Environment (PXE). Place the steps of the PXE network boot sequence 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 the client broadcasting a DHCP DISCOVER request with PXE extensions, receiving network parameters along with TFTP server location (Option 66) and bootfile name (Option 67) from DHCP, downloading the bootloader via TFTP, and finally executing the bootloader to launch WinPE.
The PXE boot protocol relies on standard sequential network operations: broadcasting a network discovery request with PXE options, receiving addressing along with DHCP Options 66 (TFTP server) and 67 (bootfile name), establishing a TFTP connection to download the bootloader, and executing the bootloader to start the Windows Preinstallation Environment (WinPE).

Step-by-Step Solution

1
Initiate network discovery
The client broadcasts a DHCP DISCOVER frame flagged with PXE options.
Without an operating system installed on local media, the NIC firmware must broadcast to find network configuration and boot server locations.
2
Receive boot server configuration
The DHCP server responds with an IP address offer including Option 66 (TFTP Server Hostname/IP) and Option 67 (Bootfile Name).
The client needs to know where the boot files reside and which specific filename to request.
3
Retrieve bootloader file
The client establishes a TFTP session with the specified boot server and downloads the network bootloader (such as bootmgr.efi).
Trivial File Transfer Protocol (TFTP) is used because of its minimal protocol overhead suitable for firmware-level execution.
4
Launch pre-installation environment
The downloaded bootloader executes and loads the WinPE image into memory.
WinPE provides the minimal Windows engine, storage drivers, and networking support required to execute automated or manual OS installation scripts.

Key Concept

PXE Network Installation Sequence
Estimated Time:1m 30s
Question 87Question →

A help desk technician needs to assign a static IPv4 address, subnet mask, default gateway, and preferred DNS server to a Windows 11 client using the legacy Control Panel interface. What is the correct sequence of steps the technician should take to apply these networking settings?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence begins with launching ncpa.cpl, opening adapter properties, navigating into IPv4 properties, toggling static address radio buttons to input IP data, and populating static DNS details before clicking OK.
Configuring static client IPv4 parameters in Windows via ncpa.cpl demands a top-down administrative workflow: invoking the network connections applet, opening the network adapter properties, opening the TCP/IPv4 properties item, selecting the static addressing radio button, and completing the IP and DNS field entries before saving.

Step-by-Step Solution

1
Launch ncpa.cpl using the Run dialog.
The Network Connections window opens displaying all physical and virtual network adapters.
Shortcuts like ncpa.cpl bypass modern Settings menus to directly access legacy network interface tools.
2
Open properties for the Ethernet interface.
The Ethernet Properties window appears, displaying client protocols and services.
Adapter-level properties must be opened to edit protocol configurations bound to that physical NIC.
3
Access Internet Protocol Version 4 (TCP/IPv4) properties.
The TCP/IPv4 configuration dialog box displays current DHCP or static addressing settings.
IPv4 network configuration settings are contained within this specific protocol layer item.
4
Enable and populate static IP address fields.
Text fields for IP address, Subnet mask, and Default gateway become active and receive input values.
By default, Windows uses dynamic allocation; selecting the static radio button un-greys the entry fields.
5
Specify primary DNS server settings and save.
DNS address is saved and the entire IPv4 configuration is committed to the interface.
Saving the dialog commits all configured static parameters to the active adapter context.

Key Concept

Windows Network Adapter IPv4 GUI Configuration Sequence
Question 88Question →

A help desk technician is investigating a network connection failure on a Windows client workstation. Place the following network diagnostic troubleshooting steps in the correct order to systematically isolate the failure from the local protocol stack out to DNS name resolution.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of network diagnostic steps is: 1) Ping the loopback address (127.0.0.1), 2) Ping the default gateway IP address, 3) Ping a public IP address, 4) Ping a fully qualified domain name.
Systematic network troubleshooting follows a bottom-up sequence starting at the local host and moving outward: 1) Loopback address (127.0.0.1) tests the local TCP/IP software stack, 2) Default gateway IP tests local physical switch and router link connectivity, 3) Public numerical IP address tests external WAN routing while bypassing DNS, 4) Domain name tests the DNS resolution service.

Step-by-Step Solution

1
Test internal protocol stack
Pinging 127.0.0.1 sends ICMP traffic internal to the operating system TCP/IP stack without placing packets on the physical network cable.
If the loopback test fails, local protocol software or network drivers are corrupt, making external network testing invalid.
2
Verify local network connection
Pinging the local default gateway tests connectivity between the workstation, local switch, and router interface.
This step confirms that the workstation has valid local IP configuration parameters and physical network link integrity.
3
Verify external WAN routing
Pinging a known public numerical IP address tests routing through the default gateway out to the Internet.
Using a numerical IP address isolates WAN routing functionality without relying on DNS name resolution.
4
Verify DNS name resolution
Pinging a domain name forces Windows to resolve the FQDN to an IP address via configured DNS servers before sending the ICMP request.
If numerical IP pings succeed but domain name pings fail, the failure is specifically isolated to DNS configuration or DNS server availability.

Key Concept

Layered Network Diagnostic Isolation
Question 89Question →

A desktop workstation utilized for high-resolution video rendering abruptly powers off without warning after approximately 10 minutes of heavy processing. The technician suspects either CPU thermal runaway or a power delivery protection trip. Place the following troubleshooting and remediation steps in the correct chronological order according to standard hardware troubleshooting methodology, starting from initial diagnostic entry to final system validation.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of troubleshooting steps begins with inspecting BIOS/UEFI health monitor logs, followed by establishing a theory of thermal throttling, performing thermal interface material replacement and cooler re-seating, conducting a targeted CPU stress test, and concluding with a full-system workload verification test.
Structured hardware troubleshooting follows a logical progression: gathering information from system hardware monitors, establishing a theory of probable cause, implementing the physical solution (clearing degraded thermal paste and reseating the cooler), verifying component-level resolution via targeted testing, and finally validating comprehensive system stability under maximum full-system load.

Step-by-Step Solution

1
Gather empirical diagnostic data
Obtained historical thermal metrics and voltage regulation data from BIOS/UEFI hardware monitoring.
Troubleshooting must always begin with non-invasive information gathering to understand system state.
2
Develop a theory of probable cause
Identified CPU thermal trip as the likely cause due to peak temperature logs exceeding maximum TDP limits.
Analyzing collected data allows the technician to form a testable hypothesis before altering hardware.
3
Implement the action plan and solution
Restored optimal thermal transfer between the CPU integrated heat spreader and heatsink.
Corrective action (clearing old thermal compound and reseating the cooler) directly addresses the root cause.
4
Verify single-component resolution
Confirmed processor core temperatures remain within safe operating parameters under direct CPU load.
Verifying the specific affected component ensures the primary repair was effective.
5
Perform full system verification and stress testing
Validated system-wide thermal and power stability under maximum combined load.
Comprehensive validation ensures the system can handle full workload demands without secondary failures.

Key Concept

CompTIA Hardware Troubleshooting Methodology for Thermal and Power Systems
Question 90Question →

A system administrator needs to resolve system instability on a Windows workstation suspected of having corrupted operating system files. Place the command-line remediation 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 starts with opening an elevated Command Prompt, followed by scanning the Windows image health with DISM /scanhealth, repairing the Windows component store image with DISM /restorehealth, and finally running SFC /scannow to replace corrupted protected system files.
The proper sequence for repairing Windows OS corruption requires administrative rights first. Next, DISM /scanhealth verifies if the Windows component store is corrupted. DISM /restorehealth then fixes the component store using Windows Update or local repair sources. Finally, SFC /scannow uses the repaired component store to replace corrupted protected system files.

Step-by-Step Solution

1
Open Command Prompt as Administrator.
Grants elevated permissions required for servicing system files and Windows image stores.
DISM and SFC commands will fail if executed without administrative privileges.
2
Run `dism /online /cleanup-image /scanhealth`.
Scans the component store for corruption and reports whether the image is healthy or repairable.
Verifies image integrity prior to initiating repairs.
3
Run `dism /online /cleanup-image /restorehealth`.
Downloads clean files from Windows Update to fix corruption within the local component store.
SFC relies on a healthy component store to pull replacement system files.
4
Run `sfc /scannow`.
Scans protected system files and replaces damaged ones with cached copies from the repaired component store.
Completes the system file repair using a verified healthy Windows image store.

Key Concept

Windows Image and System File Repair Workflow (DISM and SFC)
Question 91Question →

A desktop technician receives a helpdesk ticket stating that a Windows workstation is not reflecting newly assigned domain Group Policy Objects (GPOs). The technician needs to manually enforce policy updates using the command line, verify applied GPOs in the terminal, and output a detailed HTML report for compliance audit. In what order should the technician execute the steps below to complete this administrative workflow?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The technician must first open an elevated Command Prompt ('Run as administrator'), then execute 'gpupdate /force' to apply the updated policy settings, followed by 'gpresult /r' to inspect summary output in the console, and finally execute 'gpresult /h gpreport.html' to create the detailed HTML audit report.
The workflow begins with opening an elevated Command Prompt, as updating computer-level policies and extracting full RSoP details requires elevated administrative permissions. Next, 'gpupdate /force' must be run to pull down and re-apply all current GPOs from Active Directory. Once the refresh completes, 'gpresult /r' is executed to quickly verify in the command prompt console that the expected GPOs have taken effect. Finally, 'gpresult /h gpreport.html' exports the complete, verified RSoP report to an HTML document for official audit logging.

Step-by-Step Solution

1
Launch elevated Command Prompt
Obtains Administrator security token required for machine policy enforcement
Machine-level policy updates and full RSoP querying fail without administrative privileges.
2
Run 'gpupdate /force'
Contacts Active Directory and refreshes all user and computer policy settings
New domain policy settings must be pulled and applied before their active state can be verified or documented.
3
Run 'gpresult /r'
Outputs summary RSoP data, security group memberships, and applied GPO names in the terminal
Allows quick interactive verification to ensure the newly assigned GPOs applied successfully.
4
Run 'gpresult /h gpreport.html'
Creates an HTML file containing comprehensive GPO configuration details
Generates the permanent visual documentation artifact required for audit compliance after confirming successful policy update.

Key Concept

Group Policy Command-Line Administration (gpupdate and gpresult)
Question 92Question →

A systems administrator is developing a standardized automated script to deploy a legacy line-of-business application across a enterprise network of 64-bit Windows workstations. Place the following installation and 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 for automated application deployment is: 1) Verify architecture compatibility and install prerequisite runtimes, 2) Execute installer with elevated admin privileges, 3) Pass silent switches for unattended setup, 4) Modify global registry keys in HKLM for baseline config, and 5) Restrict NTFS folder permissions to enforce least privilege.
The correct order follows the standard technical workflow for automated software deployment: first, ensure environment dependencies and runtime compatibility (32-bit runtimes on 64-bit OS via WOW64); second, launch the installer with elevated administrative rights to ensure write access to protected areas; third, include silent command-line switches to suppress interactive prompts; fourth, write post-installation configurations to global registry locations; and finally, harden the target folder with proper NTFS least-privilege permissions.

Step-by-Step Solution

1
Audit architecture requirements and deploy runtime dependencies
System meets software dependencies and includes necessary 32-bit runtime support (WOW64).
Installers will fail immediately or produce runtime errors if required supporting libraries are absent prior to execution.
2
Invoke installer with administrative rights
Installer process runs under an elevated token.
Writing to protected areas like C:\Program Files (x86) and system registry hives requires administrative authorization.
3
Apply unattended command-line parameters
Installation runs silently without requiring interactive user input.
Automated deployment pipelines require silent switches to prevent setup wizard prompts from blocking automated script execution.
4
Configure global registry keys post-install
Application default settings are established under HKEY_LOCAL_MACHINE.
Post-installation settings depend on the application registry structure being populated by the installer first.
5
Enforce security permissions on binaries
Standard users are restricted to Read & Execute NTFS permissions on the installation directory.
Hardening software directory permissions must take place after all binaries and config files have been created.

Key Concept

Application Installation and Configuration Concepts
Estimated Time:3m 0s
Question 93Question →

A network technician is responding to a sudden loss of connectivity between a workstation and an optical storage array following server rack maintenance. In what sequential order should the technician perform the following actions according to the standard CompTIA 6-step troubleshooting methodology?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence follows the CompTIA troubleshooting methodology: 1. Gather information and visually inspect physical fiber links (Identify the problem); 2. Hypothesize that excessive bending caused attenuation (Establish a theory of probable cause); 3. Measure optical signal loss with a power meter (Test the theory); 4. Plan and swap the damaged patch cable (Establish a plan of action & implement solution); 5. Test transfer speeds and install strain-relief clips (Verify full system functionality & implement preventive measures); 6. Log the root cause and repair metrics in the ticketing system (Document findings, actions, and outcomes).
The CompTIA 6-step troubleshooting methodology dictates a sequential progression: 1. Identify the problem by gathering user reports and inspecting physical symptoms; 2. Establish a theory of probable cause based on evidence; 3. Test the theory using diagnostic tools to confirm the cause; 4. Establish a plan of action and implement the solution; 5. Verify full system functionality and implement preventive measures; 6. Document findings, actions, and outcomes.

Step-by-Step Solution

1
Identify the Problem
Interviewed users and conducted visual inspection of fiber link status LEDs.
Troubleshooting always begins by gathering symptoms and establishing recent environment changes.
2
Establish a Theory of Probable Cause
Hypothesized that fiber cable bend radius violation caused optical attenuation.
Developing a theory guides directed diagnostic testing.
3
Test the Theory to Determine Cause
Confirmed physical cable degradation using an optical power meter.
Testing verifies whether the theoretical cause is correct prior to taking action.
4
Establish a Plan of Action and Implement the Solution
Created a replacement plan and installed a new fiber patch cable.
Executing an authorized plan addresses the root cause systematically.
5
Verify Full System Functionality and Implement Preventive Measures
Verified sustained data transfer speeds and added strain-relief clips.
Ensures the fix restored operation and prevents future recurrence.
6
Document Findings, Actions, and Outcomes
Recorded problem details and resolution steps in the ticketing system.
Provides documentation for future reference and knowledge sharing.

Key Concept

CompTIA 6-Step Troubleshooting Methodology
Estimated Time:1m 30s
Question 94Question →

A technician receives an alert that a server's hot-swappable hardware RAID 5 volume is operating in a degraded state due to a single drive failure. What is the correct sequence of steps the technician should follow to replace the drive and restore full array redundancy?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The technician must first identify the failed drive using software and LED indicators, remove the faulty disk from the hot-swap bay, insert a replacement drive of equal or larger capacity, verify or initiate the rebuild process, and finally confirm that the array status returns to Optimal.
When recovering a degraded RAID 5 array on a hot-swappable server, the technician must accurately identify the failed disk to prevent pulling a working drive. Removing the failed unit, inserting a replacement with equal or greater storage capacity, monitoring the rebuild operation, and verifying optimal status in the management console is the standard sequential procedure for maintaining data integrity.

Step-by-Step Solution

1
Locate the specific drive experiencing failure
Confirmed physical slot position via controller software and amber indicator light on the drive bay
Prevents accidental removal of a functional drive, which would cause complete array failure in RAID 5
2
Remove the damaged physical drive from the hot-swap bay
Failed drive safely extracted without powering down the server
Hot-swappable backplanes allow drive replacement while maintaining system uptime
3
Install an qualified replacement disk of matching or higher capacity
New disk locked securely into place inside the drive caddy
RAID rebuilds require a drive with sufficient capacity to match the existing array block layout
4
Monitor or trigger the RAID array rebuild phase
RAID controller begins recalculating parity data across existing disks and writing to the new drive
Rebuilding recreates lost data blocks onto the fresh disk
5
Verify overall volume health following sync completion
RAID volume transitions from Degraded state to Optimal/Healthy state
Ensures full fault tolerance has been successfully re-established

Key Concept

Hot-swappable RAID 5 drive replacement and rebuild procedure
Estimated Time:1m 30s
Question 95Question →

A desktop administrator is creating a master reference image to deploy Windows across an enterprise network. In what order should the administrator execute the following steps to build, generalize, and capture the image?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence to build and capture a generalized master image is: Boot into Audit Mode, install required applications and updates, run Sysprep with /generalize and /oobe options, boot into WinPE, and run DISM to capture the system volume.
The standard process for creating a deployment image requires entering Audit Mode to configure software, running Sysprep with /generalize to strip system-specific details, booting into an offline WinPE environment, and using DISM to capture the volume.

Step-by-Step Solution

1
Boot into Audit Mode during initial setup.
Bypasses the default Out-of-Box Experience (OOBE) setup wizard.
Audit Mode enables pre-configuration of system settings and software without creating temporary user profiles.
2
Install applications, drivers, and updates.
The reference OS contains all baseline software needed for deployment.
Software customization must take place on the reference system before sealing the operating system.
3
Run Sysprep with the /generalize switch.
Strips unique SIDs, computer names, and driver bindings from the installation.
Generalization prevents security account identifier collisions when the image is deployed to multiple target computers.
4
Boot the system into WinPE.
Unmounts the primary OS partition and renders system files idle.
An active Windows partition cannot be cleanly captured while the operating system kernel is running.
5
Execute DISM /Capture-Image.
Saves the system partition to a Windows Imaging (.wim) file.
DISM captures the offline, generalized Windows volume into a standard deployment image.

Key Concept

Sysprep and Master Image Capture Workflow
Question 96Question →

A system technician is tasked with performing an in-place upgrade from Windows 10 Pro to Windows 11 Pro on a domain-joined corporate laptop that has BitLocker Drive Encryption active. Place the following operational steps in the correct chronological order from first to last to complete the upgrade without data loss or boot failures.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence from first to last is: 1) Perform a complete backup of user files and system configuration data, 2) Suspend BitLocker protection on the operating system volume, 3) Run the Windows 11 setup wizard to execute the in-place upgrade, 4) Log in and verify network connectivity and domain authentication, 5) Resume BitLocker encryption protection on the system drive.
The sequence follows mandatory IT maintenance procedures: backing up user data first guarantees recovery capability, suspending BitLocker second prevents setup reboots from locking the drive, executing the setup third performs the actual upgrade, validating network and domain settings fourth confirms operational readiness, and resuming BitLocker fifth restores volume security.

Step-by-Step Solution

1
Protect critical system data
User data and system state are safely backed up
Creating a backup prior to OS modification provides a fallback recovery point if the upgrade process encounters fatal errors.
2
Prepare volume encryption for installer reboots
BitLocker protection is suspended temporarily
Suspending BitLocker prevents the system from locking the drive or prompting for recovery keys when boot files are updated during upgrade restarts.
3
Perform the operating system upgrade installer
In-place upgrade process executes to completion
Running setup applies Windows 11 updates directly over the existing OS while preserving installed applications and user settings.
4
Validate post-installation operating environment
Domain trust, network access, and application stability are confirmed
Verification confirms that the workstation operates correctly within the corporate network context before re-enforcing security policies.
5
Restore volume security controls
BitLocker protection is resumed
Re-enabling BitLocker ensures the host volume remains encrypted and protected against unauthorized offline access.

Key Concept

In-Place OS Upgrade Workflow with Encrypted Volume Management
Question 97Question →

A desktop support technician is tasked with upgrading an existing workstation running 64-bit Windows 10 Pro to Windows 11 Pro. The system currently uses Legacy BIOS boot mode with a Master Boot Record (MBR) disk layout. To meet Windows 11 system requirements, the technician must convert the system disk to GUID Partition Table (GPT) and enable UEFI mode with Secure Boot before performing an in-place upgrade, all while preserving user files and applications. Place the required 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 begins with validating the disk layout using `mbr2gpt /validate`, followed by executing the disk conversion with `mbr2gpt /convert`, updating system firmware from Legacy BIOS to UEFI with Secure Boot enabled, and finally executing the Windows 11 installation setup to complete the in-place upgrade.
The disk must first be validated using `mbr2gpt /validate /allowFullOS` to verify layout compliance. Next, `mbr2gpt /convert /allowFullOS` changes the partition table from MBR to GPT. Immediately after conversion, the system must be rebooted into firmware to switch from Legacy BIOS/CSM mode to native UEFI with Secure Boot. Finally, with UEFI mode active and GPT established, the technician boots Windows and launches Windows 11 setup to perform the in-place upgrade.

Step-by-Step Solution

1
Run validation tool in Windows
The `mbr2gpt /validate /allowFullOS` command checks the disk layout and confirms system eligibility without modifying data.
Validation prevents failed conversion attempts that could corrupt partition structures.
2
Convert partition table to GPT
The `mbr2gpt /convert /allowFullOS` command reconfigures the partition structure to GPT and creates the required EFI System Partition.
Windows 11 mandates a GPT disk layout to boot under UEFI mode.
3
Reconfigure system firmware
Restarting into system setup, turning off Compatibility Support Module (CSM)/Legacy mode, and turning on UEFI Boot and Secure Boot aligns hardware settings with the new disk partition layout.
The converted disk can no longer boot under Legacy BIOS mode; it requires UEFI mode.
4
Run Windows 11 Setup
Launching the Windows 11 installer allows the system to verify TPM 2.0, Secure Boot, and UEFI requirements, completing the in-place upgrade.
The OS upgrade can only proceed once all hardware and partition prerequisites are satisfied.

Key Concept

Converting MBR to GPT using `mbr2gpt.exe` before enabling UEFI and performing a Windows 11 upgrade
Question 98Question →

A technician is preparing to perform a clean operating system installation on a user's workstation. In what order should the technician execute the following steps to ensure a successful deployment without data loss?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for a clean OS installation is: Back up critical user files, configure UEFI/BIOS boot settings, partition and format the target drive, complete OOBE account setup, and install system drivers and updates.
A clean OS installation must begin with backing up data to protect user files. Next, configuring the boot order in UEFI/BIOS ensures the system starts from installer media. Partitioning and formatting disk space prepares the drive to receive OS files. Completing OOBE establishes initial login credentials and preferences. Finally, updating hardware drivers and applying security patches ensures full operational readiness.

Step-by-Step Solution

1
Preserve existing user data.
User files are safely backed up to an external medium.
Prevents permanent data destruction during storage formatting.
2
Adjust system boot sequence in firmware.
Computer boots directly from the installation USB or optical disc.
Allows the installation wizard to launch instead of booting into the primary storage drive.
3
Prepare target storage drive in setup program.
Target disk is partitioned and formatted with the designated file system.
Creates a clean structure for the operating system system files.
4
Configure Out-of-Box Experience (OOBE).
Initial user accounts, network connectivity, and privacy settings are established.
Finalizes the initial interactive setup sequence of the new OS environment.
5
Perform post-installation system servicing.
All hardware components operate properly with official vendor drivers and patches.
Ensures system security, hardware stability, and full functionality.

Key Concept

Clean OS Installation Sequence
Estimated Time:1m 0s
Question 99Question →

A network technician needs to reset a Windows workstation's dynamic IP address assignment and verify the updated network configuration using the command line. In what order should the technician execute the following steps?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with opening an elevated Command Prompt, executing 'ipconfig /release' to release the active IP lease, running 'ipconfig /renew' to acquire a new IP configuration from the DHCP server, and finally executing 'ipconfig /all' to verify the new settings.
To reset and verify a Windows client's DHCP configuration, an elevated Command Prompt must first be opened. Next, executing 'ipconfig /release' releases the current IP address. Following that, 'ipconfig /renew' requests a new IP configuration from the DHCP server. Finally, running 'ipconfig /all' confirms that the client received valid network settings.

Step-by-Step Solution

1
Open an elevated Command Prompt window
Access to administrative network utilities is granted.
Administrative rights are necessary to modify network adapter settings via command line.
2
Release existing DHCP lease
The current IP address configuration is cleared from the network adapter.
Clearing the existing IP configuration allows the interface to request fresh addressing parameters.
3
Request a new DHCP lease
A new IP address, subnet mask, default gateway, and DNS configuration are provided by the DHCP server.
Running the renewal switch broadcasts a request for a fresh IP lease.
4
Verify settings using ipconfig /all
Detailed TCP/IP configuration parameters are displayed in the command output.
Inspecting the full network details confirms the workstation successfully obtained valid addressing parameters.

Key Concept

DHCP Release and Renewal Command Sequence
Question 100Question →

A user's custom database client application on a Windows 11 workstation has become completely unresponsive. A systems administrator needs to determine if the application is experiencing a thread deadlock, terminate the blocking process, and inspect the system logs for the application hang event. In what chronological order should the administrator perform the steps below?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins by launching Resource Monitor and selecting the CPU tab, right-clicking the hung process to Analyze Wait Chain, terminating the identified blocking process thread, and finally checking the Application log in Event Viewer for event details.
The correct workflow starts by opening Resource Monitor (resmon.exe) to evaluate live CPU processes. Using 'Analyze Wait Chain' on the frozen process allows the administrator to pinpoint the exact blocking PID causing the deadlock. Ending that specific blocking process clears the lock. Finally, opening Event Viewer (eventvwr.msc) to examine the Application log allows the administrator to review the Application Hang event for underlying faulting modules.

Step-by-Step Solution

1
Open Resource Monitor and navigate to CPU process listings.
Active processes and thread data are displayed.
Resource Monitor provides advanced process interaction, including thread wait chain diagnostics that standard Task Manager views do not offer.
2
Execute the Analyze Wait Chain feature on the target process.
A window opens illustrating which child or external thread is delaying execution.
This identifies whether the application is waiting on another process PID or an external resource.
3
Terminate the blocking PID listed in the Wait Chain view.
The resource lock is released, restoring application responsiveness.
Ending only the blocking thread clears the deadlock without needing a full system reboot.
4
Open Event Viewer and check the Application log.
Event ID details regarding the Application Hang are retrieved.
Event Viewer records official system events and error codes essential for root-cause analysis and documentation.

Key Concept

Windows Resource Monitor Analyze Wait Chain and Event Viewer Application Log Diagnostics
Estimated Time:1m 30s
PreviousPage 5 / 22Next
All practice questions — CompTIA A+ (Core 1 & Core 2) | Examkin