Examkin

All practice questions

423 questions

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

A systems administrator needs to isolate Critical and Error event logs from the Windows System log for rapid review. In what sequence should the administrator perform the steps to create a persistent Custom View in Windows Event Viewer?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence is to open Event Viewer (eventvwr.msc), select 'Create Custom View...' from the Actions pane, configure the System log source with Critical and Error severity levels under the Filter tab, and save the custom view with a unique name.
To create a Custom View in Windows Event Viewer, an administrator must first launch eventvwr.msc, choose 'Create Custom View...' from the Actions pane, specify the log source (System) and event severity checkboxes (Critical/Error) within the Filter tab, and finish by assigning a name and saving the view under Custom Views.

Step-by-Step Solution

1
Launch Event Viewer console
Event Viewer interface opens with access to event logs and navigation trees.
Administrative utilities must be opened first to modify settings or views.
2
Initiate Custom View creation
The Create Custom View dialog box appears.
The Actions pane provides direct access to creation tools for event log filtering.
3
Configure log source and event severity filtering criteria
The custom view filter parameters are specified to display only System Critical and Error events.
Filtering settings determine which specific logged events are aggregated into the custom view.
4
Save and name the custom view configuration
The custom view is added under the Custom Views node in the left pane.
Saving persists the custom filter rule so administrators can quickly revisit filtered event logs.

Key Concept

Creating and managing Custom Views in Windows Event Viewer for system troubleshooting.
Question 42Question →

A computer technician is tasked with replacing a failed hard drive in a degraded hot-swappable RAID 1 array. Which of the following sequence of steps should the technician perform to properly replace the failed drive and restore array redundancy?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with identifying the failed drive, followed by swapping the physical drive, starting the RAID rebuild operation, and finally verifying that the array status has returned to optimal.
The proper troubleshooting procedure for replacing a failed hot-swappable drive in a degraded RAID 1 array begins with identifying the failed drive using diagnostic software or LED indicators. Next, the technician replaces the disk in the bay. Then, the rebuild process is initiated (or allowed to run automatically) to resynchronize mirrored data. Finally, the technician verifies that the array status reports optimal health.

Step-by-Step Solution

1
Identify the failed drive
Determined exact drive location via management software or indicator lights.
Prevents accidental removal of a operational drive.
2
Swap the physical drive
Replaced faulty disk with a working disk in the hot-swap bay.
Provides a healthy disk target for data synchronization.
3
Rebuild the RAID volume
Data mirror resynchronization begins.
Copies mirrored data to restore data redundancy.
4
Confirm array health status
RAID status updates to optimal.
Validates full array recovery.

Key Concept

Hot-swappable RAID 1 drive replacement and array recovery workflow
Question 43Question →

A technician receives an alert indicating that a server using a hardware RAID 5 array has entered a degraded state due to a single drive failure. What is the correct sequence of steps the technician should take to replace the failed drive and restore the array to an optimal state?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The proper procedure begins with verifying backups and identifying the failed drive slot, removing the failed drive from the bay, installing an appropriate replacement drive, starting the RAID array rebuild process, and monitoring the rebuild until optimal status is restored.
The correct sequence prioritizes accurate drive identification and data safety first, followed by physical drive swap, software rebuild initiation, and final verification of array health.

Step-by-Step Solution

1
Identify failed drive and check backup status
Drive slot verified and data protection confirmed
Prevents removing the wrong drive and ensures data safety in case another drive fails during rebuild.
2
Remove faulty drive
Empty hot-swap drive bay
Prepares the chassis for the new drive installation.
3
Install replacement drive
New disk connected to array controller
Provides the physical storage target needed for array reconstruction.
4
Trigger array rebuild
Parity recalculation and data writing begins on new disk
RAID 5 requires parity calculations from surviving disks to reconstruct missing data.
5
Verify completion
Array status returns to Optimal
Confirms full fault tolerance is restored.

Key Concept

RAID 5 Drive Replacement and Array Rebuild Procedure
Question 44Question →

A desktop computer in an office environment suddenly loses network connectivity. Sequence the following troubleshooting actions in the correct bottom-up order, starting with physical layer verification and ending with remote network testing.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct troubleshooting sequence starts with inspecting physical cable connections and NIC link lights, followed by checking IP configuration using ipconfig, testing the TCP/IP stack via loopback ping, and finally pinging the default gateway.
Following the CompTIA OSI bottom-up troubleshooting methodology, a technician first verifies physical Layer 1 connectivity (checking cable connections and NIC status lights). Next, the technician verifies Layer 3 logical IP addressing using `ipconfig`. After addressing is checked, testing the loopback address (127.0.0.1127.0.0.1) verifies the internal network stack. Finally, pinging the default gateway checks local network connectivity beyond the local host.

Step-by-Step Solution

1
Verify physical connection integrity
Ensures Layer 1 physical link is active and cable is plugged in properly.
Troubleshooting should start at the physical layer to avoid diagnosing software issues when a cable is simply unplugged.
2
Check IP configuration with `ipconfig /all`
Determines if DHCP assigned a valid IP address or if the host self-assigned an APIPA address (169.254.x.x169.254.x.x).
Identifying the IP configuration status helps target whether DHCP or addressing is at fault.
3
Ping the loopback address (127.0.0.1127.0.0.1)
Confirms the network interface card software and TCP/IP protocol stack are working.
If loopback fails, the network stack or OS network drivers are corrupted.
4
Ping the default gateway
Confirms whether the local computer can communicate with the local router.
Verifies local network connectivity before attempting to reach external internet resources.

Key Concept

CompTIA Bottom-Up Network Troubleshooting Methodology
Question 45Question →

A network technician is troubleshooting a desktop computer that suddenly lost network connectivity in an enterprise environment. The technician decides to follow a systematic bottom-up troubleshooting methodology starting at the Physical layer (OSI Layer 1) and proceeding toward the Network layer (OSI Layer 3). In what sequence should the technician execute the following diagnostic steps?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with inspecting physical cable connections and NIC link lights, followed by checking local IP address configuration with ipconfig /all, then pinging the local default gateway, and finally testing remote network reachability using ping and tracert to an external address.
In a bottom-up troubleshooting methodology, technicians isolate issues sequentially from OSI Layer 1 up through higher layers. Step 1 inspects physical media and link lights (Physical layer). Step 2 verifies local IP settings using ipconfig /all (Data Link/Network interface). Step 3 tests local subnet communication by pinging the default gateway. Step 4 assesses internet and remote path reachability using ping and tracert.

Step-by-Step Solution

1
Inspect Physical layer (OSI Layer 1) infrastructure.
Confirm physical cable integrity and hardware link status.
Bottom-up troubleshooting requires verifying medium presence and link lights before checking software configurations.
2
Examine network adapter protocol configuration (OSI Layer 2/3).
Determine if DHCP assigned a valid IP address or if APIPA (169.254.x.x) is present.
Identifying the workstation's local address configuration helps pinpoint DHCP issues or static misconfigurations.
3
Test local subnet network reachability.
Verify ICMP echo response from the local router (default gateway).
Pinging the default gateway establishes whether the workstation can communicate with its local switch and router interface.
4
Test remote network reachability and routing paths.
Verify ICMP echo responses from an external public IP and identify where traffic drops using traceroute.
Testing beyond the gateway isolates local issues from wider area network (WAN) or external ISP routing issues.

Key Concept

Bottom-up network troubleshooting methodology (OSI Layer 1 to Layer 3)
Question 46Question →

An IT technician is using the Command Prompt within the Windows Recovery Environment (WinRE) to repair a non-booting Windows 11 system suffering from drive errors, component store corruption, missing boot entries, and damaged system files. Place the troubleshooting and command-line repair steps in the correct chronological order to restore system bootability.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for offline command-line system repair is: 1) Identify the assigned OS drive letter, 2) Run chkdsk /r to repair underlying disk surface errors, 3) Run DISM restorehealth to fix the component store, 4) Run offline SFC to replace corrupted protected system files, and 5) Run bootrec /rebuildbcd to reconstruct the boot configuration.
The proper troubleshooting order requires moving from foundational disk structure repairs to higher-level OS and boot repairs. First, verify drive lettering within the WinRE environment. Next, fix physical and file system errors using chkdsk /r. Then, repair the Component Store using DISM offline syntax. After restoring the component store, run SFC with offline parameters (/offbootdir and /offwindir) to fix corrupted system binaries. Finally, rebuild the Boot Configuration Data using bootrec /rebuildbcd so the system bootloader correctly references the fully repaired OS installation.

Step-by-Step Solution

1
Determine the offline drive letter using diskpart or directory listing.
The target volume is accurately identified.
WinRE assigns letters dynamically, so executing commands on the default drive letter without checking risks modifying the RAM disk or system reserved partition.
2
Run chkdsk C: /r on the identified volume.
File system allocation errors and bad physical disk sectors are fixed.
Physical disk corruption invalidates file writes attempted by repair tools later in the process.
3
Run dism /image:C:\ /cleanup-image /restorehealth.
The offline WinSxS store is verified and restored.
System File Checker relies on a healthy Component Store as its repository for replacing corrupt system files.
4
Run sfc /scannow /offbootdir=C:\ /offwindir=C:\windows.
Protected Windows system binaries are scanned and repaired.
Essential operating system binaries must be restored before boot configuration can successfully initialize the kernel.
5
Run bootrec /rebuildbcd.
The Boot Configuration Data file is reconstructed to point to the repaired installation.
Rebuilding boot entries requires a stable file system and intact boot binaries to function reliably.

Key Concept

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

A system administrator is replacing a failed M.2 NVMe SSD in a degraded RAID 5 volume on a server motherboard whose M.2 PCIe slots do not support hot-swapping. Place the troubleshooting and drive replacement steps in the correct sequential order from first to last to safely restore volume redundancy.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of actions is: 1) Perform a full data backup of the degraded RAID volume, 2) Gracefully shut down the operating system and disconnect main power, 3) Physically replace the defective M.2 NVMe SSD with a drive of equal or greater capacity, 4) Power on the system, access RAID management, and initiate the rebuild, 5) Execute a RAID volume consistency check.
The correct procedural order ensures data safety first by taking a backup of the degraded array, respects hardware limitations by powering off before handling non-hot-swappable M.2 slots, re-establishes logical redundancy via the RAID manager, and validates array health with a final parity consistency scan.

Step-by-Step Solution

1
Back up all critical files from the degraded array immediately.
Protects existing data against array destruction if an unrecoverable read error or secondary disk failure occurs during maintenance.
RAID 5 offers single-drive fault tolerance; operating in a degraded state leaves zero room for additional drive errors.
2
Shut down the server cleanly and unplug the electrical connection.
Safely removes voltage from non-hot-swappable M.2 PCIe slots on the system board.
Standard desktop and server motherboard M.2 slots require cold-swapping.
3
Remove the failed M.2 drive and install a functioning replacement drive.
Provides the physical disk capacity required to re-establish the RAID array parity structure.
The replacement disk must meet or exceed the capacity of the original member disk to be accepted into the array.
4
Boot into the system RAID configuration software and assign the new drive to begin array rebuilding.
Triggers the RAID controller to compute missing parity data and populate the replacement drive.
Hardware array controllers require manual assignment or initialization when non-hot-swapped drives are added.
5
Run a full parity consistency check across the newly rebuilt array.
Validates overall volume health and confirms no underlying disk read errors remain.
Verifies array integrity before returning the server volume to active production workloads.

Key Concept

Cold-swap M.2 drive replacement procedures and RAID parity rebuild workflow.
Question 48Question →

A system administrator is diagnosing severe packet loss and degraded throughput on a critical database server following an upgrade to a 10GBASE-SR fiber network interface card (NIC). According to the OSI bottom-up troubleshooting methodology, in what sequence should the administrator perform the following diagnostic steps to isolate the issue?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts at Layer 1 (checking fiber optical power and physical cable connectors), proceeds to Layer 2 (checking NIC interface counters for FCS/CRC framing errors), moves up to Layer 3 (verifying IP layer MTU and ICMP packet fragmentation), and finishes at Layer 4 (testing TCP transport performance with iperf).
The standard OSI bottom-up troubleshooting methodology dictates verifying physical Layer 1 media (fiber optics/power levels) first. Next, Layer 2 data link integrity is assessed by inspecting NIC frame counters for CRC/FCS errors. Following frame verification, Layer 3 network layer metrics (IP fragmentation and path MTU) are diagnosed using ICMP. Finally, Layer 4 transport layer socket bandwidth and TCP windowing are benchmarked.

Step-by-Step Solution

1
Examine Physical Layer (Layer 1) optical links.
Optical attenuation and connector contamination are measured using a fiber scope and power meter.
Bottom-up troubleshooting requires verifying physical signal transmission integrity before analyzing data link framing or IP traffic.
2
Examine Data Link Layer (Layer 2) Ethernet framing statistics.
NIC error counters are checked for CRC or FCS corruption.
If Layer 1 is physical, Layer 2 checks confirm whether physical signals are successfully parsed into valid Ethernet frames without framing errors.
3
Examine Network Layer (Layer 3) IP configurations and packet sizes.
ICMP ping tests with the Don't Fragment flag identify path MTU mismatches.
Once frame delivery is established without CRC errors, network layer IP routing and fragmentation characteristics are tested.
4
Examine Transport Layer (Layer 4) throughput performance.
Tools like iperf measure TCP/UDP port throughput and window negotiation.
Higher-layer protocol performance is validated last after all lower protocol layers (Layers 1-3) are proven fully functional.

Key Concept

OSI Model Bottom-Up Troubleshooting Methodology
Estimated Time:2m 0s
Question 49Question →

A network technician is investigating a report where a newly installed VoIP desk phone continuously reboots whenever it is plugged into a managed switch port with Power over Ethernet (PoE) enabled. Arrange the technician's actions in the correct chronological order according to the CompTIA 6-step troubleshooting methodology, starting with the initial step at the top.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence follows the standard CompTIA troubleshooting framework: 1) Interview the user and check switch logs to identify the problem, 2) Formulate a theory regarding incorrect PoE power allocation, 3) Test the theory using a standalone PoE injector, 4) Reconfigure the switch port power profile to implement the solution, and 5) Verify full functionality with a test call and document the findings.
The correct order strictly follows the standard CompTIA 6-step troubleshooting methodology: first gather information and check logs to identify symptoms, second establish a theory of cause regarding PoE power limits, third test that theory using an external power source, fourth implement the switch port re-configuration, and finally verify phone operation while documenting the resolution.

Step-by-Step Solution

1
Identify the problem
Information gathered from user interview and switch log files detailing power errors.
Troubleshooting must begin with gathering symptom details and questioning users.
2
Establish a theory of probable cause
Formulated hypothesis that power class allocation on the switch port is insufficient.
After understanding symptoms, the technician questions the obvious and establishes a cause theory.
3
Test the theory to determine cause
Connecting the phone to an external PoE injector stabilizes the phone, confirming the theory.
The theory must be confirmed via diagnostic testing before permanent configuration changes are applied.
4
Establish a plan of action and implement the solution
Switch port configuration is modified to allocate adequate wattage class.
Once the cause is proven, the technician plans and carries out the permanent fix.
5
Verify full functionality and document findings
Test call successful; root cause and configuration changes documented in the system.
Ensures the system is fully operational and records knowledge for future incident reference.

Key Concept

CompTIA 6-Step Troubleshooting Methodology
Question 50Question →

A network technician is responding to a ticket reporting that a high-availability database server lost network connectivity immediately following a firmware update on a core network switch. Place the technical troubleshooting steps in the correct order according to the standard CompTIA troubleshooting methodology, from first to last step.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order follows the 6-step CompTIA troubleshooting methodology: 1) Gather symptom details and interview the database administrator to identify the problem; 2) Formulate a hypothesis regarding erased VLAN tags to establish a theory of cause; 3) Inspect the switch interface configuration console to test the theory; 4) Re-apply the VLAN trunking parameters to implement the solution; 5) Confirm remote query access and schedule automated configuration backups to verify functionality and add preventive measures; 6) Record all findings and corrective actions in the ticketing system.
The standard CompTIA troubleshooting process requires performing steps sequentially: Step 1 (Identify the problem by gathering logs/symptoms), Step 2 (Establish a theory of probable cause), Step 3 (Test the theory by inspecting configuration parameters), Step 4 (Establish a plan of action and implement the solution), Step 5 (Verify full system functionality and implement preventive measures), and Step 6 (Document findings, actions, and outcomes).

Step-by-Step Solution

1
Identify the Problem
Symptom details and log entries gathered after interviewing affected personnel.
CompTIA methodology requires gathering information, questioning users, and identifying symptoms before taking diagnostic or corrective actions.
2
Establish a Theory of Probable Cause
Hypothesis established that VLAN trunk settings were cleared during firmware flashing.
After identifying the problem, the technician must consider obvious and probable causes to form a testable theory.
3
Test the Theory to Determine Cause
Switch console checked; confirmed that VLAN tags were indeed missing.
Testing the theory determines whether the hypothesis is correct before implementing any changes.
4
Establish a Plan of Action & Implement Solution
VLAN trunking parameters restored on the switch interface.
Once the theory is confirmed, the technician creates and executes a plan of action to resolve the issue.
5
Verify System Functionality & Implement Preventive Measures
Remote database access verified and automated config backups enabled.
After implementing the fix, full system operation must be verified, followed by preventive measures to avoid recurrence.
6
Document Findings, Actions, and Outcomes
Ticket updated with root cause analysis and step-by-step remediation history.
Documentation must always occur as the final step in the CompTIA troubleshooting process.

Key Concept

CompTIA 6-Step Troubleshooting Methodology Sequence
Question 51Question →

A system administrator is investigating a malfunctioning background application on a Windows workstation that is consuming excessive CPU resources and maintaining unauthorized network connections. Arrange the command-line actions in the correct sequential order to identify, inspect, terminate, and verify the removal of the problematic process.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of operations is: 1) Run `tasklist` to obtain the PID, 2) Run `netstat -ano` to inspect network sockets for that PID, 3) Run `taskkill /pid <PID> /t /f` to forcefully stop the process tree, and 4) Run `tasklist /fi "IMAGENAME eq executable.exe"` to verify complete termination.
The correct troubleshooting sequence begins with process identification via `tasklist`, followed by network socket inspection using `netstat -ano` to confirm connection ownership, forceful process tree termination via `taskkill /pid <PID> /t /f`, and concluding with filter verification via `tasklist /fi`.

Step-by-Step Solution

1
Identify the Process ID (PID) using `tasklist`
Obtain the specific numeric PID associated with the target application.
Process management utilities like netstat and taskkill require the target PID for detailed socket mapping and targeted termination.
2
Correlate network activity using `netstat -ano`
Confirm active network socket connections owned by the target PID.
The `-o` switch displays the owning PID for each active socket, enabling verification of the process's network activity.
3
Forcefully terminate the process tree using `taskkill /pid <PID> /t /f`
The target process and all child processes spawned by it are stopped immediately.
The `/f` switch forces termination of non-responsive applications, while `/t` ensures child processes in the process tree are also halted.
4
Verify process termination using `tasklist /fi "IMAGENAME eq executable.exe"`
Confirm that zero running instances match the target executable image name.
Post-remediation filter verification ensures that no remaining instances or child processes are running in system memory.

Key Concept

Windows Command-Line Process Management and Network Diagnostic Sequence
Question 52Question →

A systems administrator needs to configure a newly deployed Windows background application. The application must start automatically upon system boot, run under a designated service account, and automatically attempt to restart if the service process crashes unexpectedly. What is the correct sequence of administrative steps to configure these settings within the Services console (`services.msc`)?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with opening the Services snap-in (`services.msc`) and accessing the service properties, followed by setting the Startup type to Automatic on the General tab, assigning the service account credentials on the Log On tab, setting the First failure action to 'Restart the Service' on the Recovery tab, and finally applying changes and starting the service.
To properly configure a Windows service, a technician must open the Services console (`services.msc`) and open the service properties dialog. First, the General tab is used to configure the Startup type (e.g., Automatic). Second, the Log On tab allows configuring the user account identity under which the service runs. Third, the Recovery tab allows configuring automated actions (such as restarting the service) when failures occur. Finally, applying the settings commits the changes so the service can be safely started under the new configuration.

Step-by-Step Solution

1
Launch `services.msc` as administrator and double-click the target service.
The target service's multi-tabbed Properties dialog window opens.
Administrative access is necessary to view and modify system service configurations.
2
Select the General tab and set Startup type to Automatic.
The service is configured to launch during Windows startup.
The General tab controls basic operational states and automatic boot initialization.
3
Switch to the Log On tab, choose 'This account', and input the credentials.
The service is bound to run under a specific security identity.
Service account assignment is controlled specifically within the Log On tab.
4
Navigate to the Recovery tab and change First failure to 'Restart the Service'.
Windows is configured to automatically attempt service restoration upon process failure.
Automated recovery parameters upon crashes are defined under the Recovery tab.
5
Click Apply and select Start.
All properties are saved to the Windows Service Control Manager database and the service starts.
Changes must be committed before initiating active execution of the service.

Key Concept

Configuring Windows background service startup types, authentication identities, and automated failure recovery using the Services console (`services.msc`).
Question 53Question →

A network administrator receives an automated alert indicating that a hard drive in a server's hot-swappable hardware RAID 5 array has failed, leaving the volume in a degraded state. Arrange the troubleshooting and recovery steps below in the correct sequential order to safely replace the drive and restore array fault tolerance.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of steps is: 1) Identify the exact physical slot of the failed disk using controller tools and status LEDs; 2) Perform a complete data backup of the degraded RAID volume; 3) Remove the failed drive and install a replacement drive of equal or greater capacity; 4) Initiate the array rebuild process in the RAID management interface; 5) Monitor the rebuild progress until the array status returns to optimal.
The correct procedural order ensures data safety and array integrity. First, the technician identifies the specific failed disk using management software and LEDs to avoid pulling a healthy drive. Second, backing up the degraded volume secures data in case a second drive fails during heavy read operations. Third, the failed drive is physically swapped out for a new one. Fourth, the rebuild operation is started in the controller interface. Finally, monitoring the process until optimal status is reached verifies that parity synchronization completed successfully.

Step-by-Step Solution

1
Locate and confirm the failed disk using controller tools and status LEDs.
Prevents accidental removal of an operational drive from a degraded array.
Pulling a healthy drive from a degraded RAID 5 array causes immediate total array failure and data loss.
2
Backup all data on the degraded RAID array immediately.
Protects array data against potential secondary drive failure.
Rebuilding RAID parity puts intensive read stress on remaining disks, increasing the risk of secondary drive failure.
3
Hot-swap the faulty hard drive with a healthy drive of matching or larger capacity.
Provides the necessary physical storage for parity reconstruction.
A functional target drive must be physically connected to allow parity data sync.
4
Start or confirm the parity rebuild operation via the RAID utility.
Begins reconstructing parity data across the array onto the replacement disk.
Hardware RAID controllers require initiation or auto-detection to begin writing parity data.
5
Monitor the progress until array status reports optimal health.
Confirms array fault tolerance is restored.
Ensures that the rebuild completed without unrecoverable read errors or interruptions.

Key Concept

Hot-Swap RAID 5 Drive Replacement and Parity Rebuild Procedure
Estimated Time:1m 30s
Question 54Question →

A server technician receives a system monitoring notification indicating that a database server's hardware RAID 10 array is operating in a degraded state due to a total disk failure in slot 3. The server chassis utilizes hot-swappable drive bays, and an identical replacement hard drive is readily available. What is the correct chronological sequence of steps the technician should perform to safely replace the drive and restore redundancy to the RAID volume?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with identifying the failed disk in the RAID management software, creating a fresh data backup, physically swapping out the damaged drive with a new one in the hot-swap bay, and finally starting and verifying the RAID rebuild process in the controller utility.
When responding to a degraded RAID array alert on a hot-swappable enterprise system, the technician must follow a strict logical sequence to prevent data loss. First, verifying the drive's software identification prevents pulling the wrong physical disk. Second, taking an immediate backup safeguards data because the array is vulnerable while running without full redundancy. Third and fourth, the physical hot-swap of the disk is conducted. Finally, the rebuild process must be initiated or confirmed in the controller utility to re-establish full data mirroring and striping redundancy.

Step-by-Step Solution

1
Locate and confirm disk failure details in the RAID software.
Discovered drive in slot 3 is offline, preventing accidental extraction of operational drives in slots 0, 1, or 2.
Accidentally pulling an operational drive from a degraded array will crash the entire volume.
2
Execute a full backup of array contents to secondary storage.
Current data state is safely backed up outside the array.
Degraded arrays experience high read stress during rebuilds; backing up beforehand secures critical data against dual-drive failure.
3
Remove the failed drive from hot-swap bay slot 3.
The faulty hardware is safely disconnected from the backplane.
The system supports hot-swapping, allowing physical removal without interrupting host power.
4
Insert the new, matching replacement drive into slot 3.
The replacement disk is physically connected and detected by the storage controller.
The controller requires a functional physical target of equivalent or greater capacity to begin data sync.
5
Start and monitor the array rebuild task via the controller interface.
Parity and mirrored data are reconstructed across the array until status returns to Optimal.
Rebuilding recalculates data parity and restores full fault tolerance to the RAID 10 volume.

Key Concept

Hot-Swap RAID Maintenance and Disaster Prevention Workflow
Estimated Time:2m 0s
Question 55Question →

A technician receives a support request for a departmental laser printer that outputs text that easily smudges when touched. According to the CompTIA troubleshooting methodology, in what order should the technician perform the following actions?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order follows the CompTIA troubleshooting methodology: (1) Gather details from the user and examine smudged pages, (2) Formulate a theory of probable cause suspecting a malfunctioning fuser, (3) Install a new replacement fuser assembly, and (4) Log the root cause and outcome in the ticketing system.
The correct order strictly adheres to the standard CompTIA troubleshooting process: first gather symptoms to identify the problem, second establish a theory of probable cause, third implement the repair plan by replacing the fuser, and finally document all findings and outcomes.

Step-by-Step Solution

1
Identify the problem
Symptoms are observed and confirmed from user input and printout inspection.
CompTIA methodology requires gathering information and identifying symptoms before forming theories or taking action.
2
Establish a theory of probable cause
The technician identifies the fuser as the primary suspect for unfused/smudged toner.
After identifying symptoms, a hypothesis regarding the underlying cause must be established.
3
Implement the solution
The faulty fuser assembly is replaced with a working component.
Corrective action must be executed after establishing the cause and plan.
4
Document findings, actions, and outcomes
The ticket is updated with complete repair details.
Documentation is always the final step in the CompTIA troubleshooting methodology.

Key Concept

CompTIA Troubleshooting Methodology applied to Printer Issues
Estimated Time:1m 0s
Question 56Question →

A technician is troubleshooting network connectivity on a Windows workstation that currently has an Automatic Private IP Addressing (APIPA) address assigned. The technician wants to release the existing address, request a new lease from the DHCP server, and inspect the updated configuration parameters. Place the following troubleshooting 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 is: Open the Command Prompt with administrator privileges, execute ipconfig /release, execute ipconfig /renew, and finally execute ipconfig /all.
Refreshing a DHCP configuration using Windows command-line tools requires an elevated Command Prompt window so that network adapter settings can be modified. Executing 'ipconfig /release' drops the existing APIPA or invalid IP settings. Next, 'ipconfig /renew' prompts the workstation to request a new IP address lease from the DHCP server. Finally, 'ipconfig /all' displays comprehensive network interface details, allowing the technician to confirm that a valid IP address, subnet mask, default gateway, and DNS servers were obtained.

Step-by-Step Solution

1
Launch the Command Prompt as an Administrator.
An elevated CLI window opens with administrative rights.
Network configuration changes require administrative privileges on Windows workstations.
2
Run the command ipconfig /release.
The current IP configuration (APIPA address) is cleared from the adapter.
The existing bound IP parameters must be dropped before asking for a new DHCP lease.
3
Run the command ipconfig /renew.
The network interface issues a DHCP broadcast and receives a new valid IP address lease.
This command forces the operating system to request fresh network parameters from the DHCP server.
4
Run the command ipconfig /all.
Full interface configuration settings (MAC address, IP address, Subnet Mask, Default Gateway, DNS Servers) are displayed.
Viewing the detailed output confirms that valid IP parameters were assigned properly.

Key Concept

Windows Command-Line Network Troubleshooting Utilities
Estimated Time:1m 0s
Question 57Question →

A network technician is investigating a desktop computer experiencing severe network throughput degradation and high late-collision rates when communicating with local servers. In what order should the technician perform the following steps to troubleshoot and resolve this wired network issue using a bottom-up approach?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with checking physical link lights on the NIC and wall jack, followed by running ipconfig /all to verify local IP settings, pinging the default gateway to isolate throughput issues to the local segment, inspecting the NIC and switch port properties for a duplex mismatch, and finally setting both ends to auto-negotiation and clearing collision counters.
Under standard bottom-up troubleshooting methodology, physical connectivity (link lights) must be confirmed first. Next, inspecting local IP configuration via ipconfig ensures basic protocol stack integrity. Testing reachability to the default gateway with ping isolates performance issues locally. Checking speed and duplex settings identifies the root cause of collisions, and aligning both sides to auto-negotiation completes the resolution.

Step-by-Step Solution

1
Inspect physical layer indicators.
Confirmed physical connection and LED activity on the NIC and jack.
Troubleshooting begins at Layer 1 to ensure hardware and cabling are functioning.
2
Check local host IP configuration.
Verified valid IPv4 address assignment and recorded gateway IP.
Ensures Layer 3 configuration parameters are present before initiating network diagnostics.
3
Perform ICMP diagnostic test to the local gateway.
Observed significant packet degradation and latency under traffic.
Isolates the performance fault to the local link segment rather than remote routing paths.
4
Inspect interface operational parameters on the host and network switch.
Discovered one endpoint forced to full-duplex while the other was set to auto-negotiate.
Duplex mismatches allow simultaneous transmission attempts that cause high collision rates.
5
Synchronize port configurations and verify resolution.
Eliminated packet collisions and restored standard throughput speeds.
Setting both interfaces to auto-negotiate ensures matching operational modes.

Key Concept

Standard CompTIA bottom-up troubleshooting methodology applied to wired Ethernet speed/duplex mismatch identification.
Question 58Question →

An IT technician is assigned to resolve an issue where network print jobs fail across subnets immediately following a gateway firewall firmware update. Place the technician's actions in the correct sequential order according to the standard CompTIA troubleshooting methodology.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological sequence according to the CompTIA troubleshooting methodology is: 1) Interview affected users and review print server event logs; 2) Develop a hypothesis that the updated firewall configuration is blocking cross-subnet TCP port 9100 traffic; 3) Perform a port scan from a remote client workstation to check if TCP port 9100 on the print server is filtered; 4) Modify the gateway security policy to explicitly permit TCP port 9100 communication across VLANs; 5) Send test print jobs from workstations on all affected subnets and record the rule change in the ticketing system.
The standard CompTIA troubleshooting framework dictates a strict 6-step logical workflow: 1. Identify the problem (gather user feedback and review print server logs), 2. Establish a theory of probable cause (hypothesize port 9100 blocking), 3. Test the theory to determine the cause (run a targeted port scan), 4. Establish a plan of action and implement the solution (update firewall policy), 5. Verify full system functionality and document findings (confirm test prints across subnets and log changes in ticket system).

Step-by-Step Solution

1
Gather symptoms and define the problem scope through user interviews and log review.
Problem is identified as cross-subnet network printing failure occurring post-update.
CompTIA Step 1 (Identify the problem) requires defining symptoms and environment before forming hypotheses.
2
Establish a probable cause theory regarding blocked network printer ports.
A focused hypothesis is established targeting TCP port 9100 filtering at the gateway.
CompTIA Step 2 (Establish a theory of probable cause) requires formulating a testable explanation.
3
Test the port filtering hypothesis using diagnostic scanning tools.
Port scan results confirm traffic on port 9100 is filtered by the gateway firewall.
CompTIA Step 3 (Test the theory to determine the cause) verifies the theory before applying changes.
4
Formulate a plan and implement the firewall policy adjustment.
Port 9100 traffic is re-enabled across subnets.
CompTIA Step 4 (Establish a plan of action and implement the solution) executes the corrective action.
5
Verify end-to-end printing functionality and complete ticket documentation.
Printing works across all subnets and change details are recorded in IT records.
CompTIA Steps 5 and 6 ensure full verification and final administrative closure.

Key Concept

CompTIA 6-Step Troubleshooting Methodology Sequence
Question 59Question →

A field service technician is dispatched to address a high-volume departmental laser printer that consistently jams when feeding paper from Tray 2, while manual feed Tray 1 functions without issue. Physical inspection shows media crumpling right before reaching the registration roller assembly. What is the correct sequence of steps the technician should take to diagnose and resolve this issue in accordance with the CompTIA troubleshooting methodology?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The proper troubleshooting sequence follows CompTIA's standard 6-step model: 1) Identify the problem through observation and log analysis, 2) Establish a theory of probable cause regarding the Tray 2 feed mechanism, 3) Test the theory by inspecting components, 4) Establish a plan of action and implement the solution by replacing worn rollers, 5) Verify full functionality by running test prints and performing preventive cleaning, and 6) Document all findings, actions, and outcomes.
CompTIA defines a strict 6-step troubleshooting methodology: 1. Identify the problem (gather information, duplicate problem, examine logs), 2. Establish a theory of probable cause (question the obvious), 3. Test the theory to determine cause (confirm hypothesis), 4. Establish a plan of action to resolve the problem and implement the solution, 5. Verify full system functionality and, if applicable, implement preventive measures, and 6. Document findings, actions, and outcomes.

Step-by-Step Solution

1
Identify the problem
Technician gathers logs and inspects physical symptoms of paper crumpling at Tray 2.
Troubleshooting must begin by gathering empirical evidence and user reports.
2
Establish a theory of probable cause
Technician hypothesizes worn Tray 2 pickup rollers or solenoid timing failure.
Formulating a targeted hypothesis narrows down potential hardware faults.
3
Test the theory to determine cause
Technician inspects roller friction pads and runs hardware diagnostics on solenoids.
Theory testing validates whether the physical cause is indeed worn rollers before ordering or replacing parts.
4
Establish a plan of action and implement the solution
Technician replaces the Tray 2 pickup roller assembly and feed rollers.
Replacing verified worn parts resolves the underlying mechanical failure.
5
Verify full system functionality and implement preventive measures
Technician prints test pages from Tray 2 and cleans optical feed path sensors.
Functional verification confirms complete repair and preventive measures minimize future failures.
6
Document findings, actions, and outcomes
Technician logs the work details and replaced part numbers in the ticketing database.
Documentation provides historical context and reference knowledge for future support calls.

Key Concept

CompTIA 6-Step Troubleshooting Methodology Applied to Hardware/Printer Diagnostics
Question 60Question →

A server administrator receives a S.M.A.R.T. predictive failure alert for Disk 2 in a hot-swappable hardware RAID 5 array on a production database server. To maintain system uptime and ensure data integrity, place the administrative steps for replacing the failing drive 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 begins with backing up volume data, followed by logically taking the failing drive offline via RAID management tools, physically replacing the drive in the hot-swap bay, and finally initiating or verifying the array rebuild process.
The proper sequence prioritizes data protection before hardware operations. Creating a full backup ensures recovery options if another disk experiences read errors during rebuilding. Next, taking the drive offline via management utilities disengages controller tasks and identifies the target bay indicator. Then, swapping the physical drive provides new storage media. Finally, monitoring or starting the rebuild confirms the RAID set returns to a healthy state.

Step-by-Step Solution

1
Back up critical data
Ensures data safety if a secondary disk failure occurs during array maintenance.
Array rebuilds place heavy read stress on remaining drives; securing an updated backup first mitigates potential catastrophic data loss.
2
Logically take the drive offline using RAID software
Prepares the disk for removal and highlights the disk bay LED indicator.
Prevents drive removal while active read/write commands are in-flight and avoids pulling the wrong disk.
3
Physically swap the degraded drive
Installs a functional blank drive into the active enclosure bay.
Physical replacement is required so the controller has target media to write parity and missing data blocks.
4
Verify and monitor the RAID rebuild
Restores array redundancy and optimal performance status.
Confirms the controller successfully accepted the new drive and is rebuilding data from parity blocks across the remaining healthy drives.

Key Concept

Hot-swappable RAID disk replacement workflow and predictive failure handling
PreviousPage 3 / 22Next
All practice questions — CompTIA A+ (Core 1 & Core 2) | Examkin