Examkin

All practice questions

423 questions

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

A technician is configuring a newly deployed network multifunction device (MFD) to enable the Scan-to-SMB (Scan to Network Folder) feature for a department share. Arrange the technician's administrative and configuration steps in the correct operational sequence from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct configuration sequence is: 1) Create the target shared folder on the network file server and assign write permissions to a dedicated scanner service account, 2) Open a web browser on a management workstation and enter the MFD's static IP address to access its Embedded Web Server (EWS), 3) Authenticate to the Embedded Web Server using administrator credentials, 4) Navigate to the digital sending/scan settings menu and input the target UNC path, domain network credentials, and authentication details, and 5) Initiate a test scan directly from the MFD touchscreen control panel to confirm successful file delivery to the network destination.
Configuring Scan-to-SMB requires server-side setup before hardware-side setup. First, the destination folder and access control permissions must be established on the server. Next, the technician accesses the MFD management interface by navigating to its IP address in a browser and authenticates with administrator credentials. After logging in, the technician enters the UNC path and account details into the SMB scan configuration section. Finally, conducting a test scan from the device control panel confirms that all permissions and network connections are correctly configured.

Step-by-Step Solution

1
Provision the destination shared folder and set share/NTFS permissions on the server.
A valid UNC target path and dedicated user account with write permissions are established.
The network endpoint must exist and accept incoming write authentication before configuring the scanner client.
2
Access the MFD EWS web interface via its IP address.
The printer login and status dashboard opens in the web browser.
Printer management features like digital sending destinations are configured via the EWS interface.
3
Log into the printer EWS with administrator rights.
Privileged configuration menus become accessible.
Security controls restrict network share configuration to authorized administrators.
4
Enter UNC path (e.g., \\server\scans) and service account credentials in SMB settings.
The MFD stores the path and authorization credentials for network file transfer.
This links the physical scanning operation to the remote storage target using SMB protocols.
5
Execute a test scan from the printer control panel to validate end-to-end functionality.
The scanned document appears in the target network folder.
End-to-end validation ensures permissions, IP connectivity, and SMB authorization succeed.

Key Concept

Multifunction Device Scan-to-SMB Configuration Workflow
Estimated Time:1m 30s
Question 22Question →

A desktop support technician is assigned to resolve a thermal throttling issue on a high-performance workstation in a laboratory environment. Place the technician's actions in the correct sequential order according to the official CompTIA 6-step troubleshooting methodology.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence follows the standard CompTIA troubleshooting methodology: 1) Identify the problem by gathering information and reviewing logs, 2) Establish a theory of probable cause, 3) Test the theory to determine the root cause, 4) Establish a plan of action and implement the solution, 5) Verify full system functionality and implement preventive measures, and 6) Document findings, actions, and outcomes.
The correct order follows the standard CompTIA 6-step troubleshooting workflow: identifying the problem through user inquiry and event logs, forming a cause hypothesis, testing the theory via load testing tools, establishing a plan of action and replacing the compound, verifying system stability and configuring thermal alerts, and documenting the final outcomes.

Step-by-Step Solution

1
Identify the problem
User symptoms gathered and system event logs inspected.
Troubleshooting must begin by gathering initial information to define the scope of the problem.
2
Establish a theory of probable cause
A plausible cause (thermal compound degradation) is hypothesized.
Formulating a theory provides a structured path for diagnostic testing.
3
Test the theory to determine cause
Stress testing under load confirms thermal throttling occurs as hypothesized.
Testing validates whether the hypothesis is correct before implementing physical changes.
4
Establish a plan of action and implement the solution
A step-by-step repair procedure is created and thermal compound is reapplied.
Planning ensures minimal operational disruption and safe repair execution.
5
Verify full system functionality and implement preventive measures
Post-repair load testing confirms normal operating temperatures, and thermal monitoring alerts are enabled.
Verification ensures the root cause is resolved and preventive steps avoid recurrence.
6
Document findings, actions, and outcomes
All ticket details, diagnostic findings, and resolution steps are finalized in the knowledge base.
Documentation retains institutional knowledge for future incident reference.

Key Concept

CompTIA 6-Step Troubleshooting Methodology
Question 23Question →

A network technician is troubleshooting a desktop computer that has lost network access. Following a bottom-up (physical to application layer) troubleshooting approach, in what order should the technician perform the diagnostic steps?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order follows a bottom-up diagnostic sequence: first verify the physical link light and cable, next check the workstation IP configuration with ipconfig, then ping the default gateway to test local network access, and finally run nslookup to verify DNS name resolution.
The bottom-up OSI troubleshooting model moves sequentially from Layer 1 (Physical) to Layer 7 (Application). Checking the physical cable and NIC link light comes first. Once physical connection is confirmed, verifying the local IP configuration (Layer 3) is next. Testing ICMP connectivity to the default gateway ensures local communication works before finally checking DNS hostname resolution at the application layer.

Step-by-Step Solution

1
Verify physical layer connectivity.
Ensure the physical cable is securely attached and the NIC link light indicates an active connection.
Troubleshooting should start at the physical layer to confirm hardware connectivity before checking software settings.
2
Check protocol layer configuration.
Determine whether the host has a valid IPv4 address assigned via DHCP or a self-assigned 169.254.x.x APIPA address.
Verifying IP addressing ensures the device has valid network configuration settings.
3
Test local network routing.
Confirm whether ICMP packets can reach the default gateway router.
Pinging the gateway verifies local link integrity and subnet routing capabilities.
4
Test application service resolution.
Confirm whether fully qualified domain names (FQDNs) can be resolved to IP addresses.
DNS resolution represents high-level service functionality needed for web browsing and domain communication.

Key Concept

Bottom-Up Network Troubleshooting
Question 24Question →

A storage administrator needs to replace a failed hot-swappable disk in a degraded RAID 5 array on an operational server. Place the standard troubleshooting and recovery steps in the correct order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequential procedure is: first, identify the exact failed drive slot using management tools; second, unlatch and remove the failed drive carrier; third, mount and insert a replacement drive of equal or greater capacity; fourth, initiate or verify the RAID rebuild process in management software.
Correct RAID drive replacement requires precise sequential execution: verifying the failed drive location first, removing the faulty drive from the hot-swap bay, seating a drive of equal or greater capacity, and verifying that the RAID controller starts rebuilding parity data onto the new disk.

Step-by-Step Solution

1
Identify the failed physical disk location.
Prevents accidental removal of an active array disk.
Removing a functional disk from a degraded RAID 5 array causes catastrophic array failure.
2
Extract the faulty drive hardware.
Frees the hot-swap bay for installation.
Hot-swappable hardware allows removal while the system remains powered on.
3
Install the replacement disk drive.
Provides healthy physical storage capacity to the array controller.
The replacement drive must match or exceed the original disk size specification.
4
Start and monitor array reconstruction.
Rebuilds data redundancy across the array.
Parity calculations regenerate missing data onto the newly inserted disk.

Key Concept

Hot-swappable RAID 5 drive replacement and array rebuild workflow
Question 25Question →

A technician is replacing a failed drive in a hot-swappable hardware RAID 5 server array. Place the steps in the correct order to complete the drive replacement and array recovery.

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 software or LEDs, 2) Remove the faulty drive from the bay, 3) Insert the replacement drive into the empty bay, and 4) Initiate or confirm the RAID array rebuild process.
The proper procedure begins by identifying the exact drive bay affected using LED status lights or system utilities. Next, the technician removes the failed drive using the hot-swap bay mechanism. Then, a fresh drive meeting capacity requirements is inserted. Finally, the technician monitors or triggers the RAID rebuild operation to calculate and restore missing data using parity from operational drives.

Step-by-Step Solution

1
Locate the failed drive using enclosure status LEDs or the controller software interface.
The specific physical bay containing the damaged disk is accurately identified.
Prevents accidentally removing a functional drive, which would cause array failure in a degraded state.
2
Safely disengage the latch and pull the failed drive out of the hot-swappable bay.
The failed disk is disconnected from the backplane while keeping server uptime.
Hot-swap architecture supports drive extraction without system power-down.
3
Slide the new disk of matching or higher capacity into the slot until fully seated.
The replacement disk connects to the RAID controller.
The controller requires a target disk with sufficient capacity to receive reconstructed parity data.
4
Verify through the RAID controller utility that the volume rebuild has started.
Parity calculations begin writing lost data onto the new drive, restoring total volume redundancy.
Ensures the storage volume transitions from degraded back to healthy status.

Key Concept

Hot-Swappable RAID 5 Drive Replacement Procedure
Question 26Question →

A server administrator receives an alert indicating that a critical database server's hardware RAID 5 array is operating in a degraded state following a single drive failure. You are assigned to replace the failed physical drive and restore array redundancy while minimizing risk to system data. Arrange the technical recovery steps into the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The proper sequence for replacing a failed hot-swappable drive in a degraded RAID array is: 1) Verify data backups, 2) Identify the failed drive slot via hardware/software indicators, 3) Remove the defective drive, 4) Insert and latch the replacement drive, and 5) Initiate and monitor the array rebuild via the RAID controller console.
The correct sequence ensures maximum data protection and prevents technician error during disk replacement. Verifying backups must occur first to guard against secondary disk failure during high I/O rebuilds. Identifying the specific failed disk using bay LEDs and management logs ensures that healthy drives are not accidentally disconnected. Once identified, removing the failed drive and inserting a properly spec'd replacement allows the hardware RAID controller to initiate parity reconstruction and restore array fault tolerance.

Step-by-Step Solution

1
Verify backup availability
Protects data integrity against unexpected total array loss during disk rebuild.
RAID 5 rebuilds place high read stress on remaining disks; confirming backups is mandatory prior to hardware changes.
2
Identify failed drive location
Pinpoints the exact slot ID and status light (e.g., solid amber/red).
Removing a functional drive from a degraded RAID 5 array results in immediate volume offline status and data loss.
3
Remove failed drive module
Frees the drive bay for replacement.
Safe removal of the malfunctioning hardware module.
4
Install replacement drive
Establishes physical link for the new drive in the enclosure.
The replacement drive must meet or exceed the capacity and performance characteristics of the failed disk.
5
Initiate RAID rebuild
Restores array redundancy and returns status from degraded to optimal.
The RAID controller requires manual assignment or automatic hot-spare detection to begin parity reconstruction.

Key Concept

RAID 5 Degraded State Hot-Swap Drive Replacement Procedure
Question 27Question →

A workstation experiencing severely degraded storage performance features a motherboard-based UEFI firmware RAID 1 array configured with two internal M.2 NVMe SSDs. Diagnostics confirm that Drive 1 has failed due to unrecoverable S.M.A.R.T. read errors. Because internal M.2 PCIe slots on this motherboard do not support hot-swapping, place the recovery and rebuild steps in the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct troubleshooting sequence begins with shutting down and disconnecting system power, followed by ESD-safe physical replacement of the failed M.2 NVMe drive, entering the UEFI RAID utility at system startup, assigning the replacement drive to rebuild the degraded RAID 1 array, and finally validating array health inside the operating system.
The process follows CompTIA troubleshooting methodology for non-hot-swappable storage arrays: isolate electrical power, replace hardware using ESD protection, configure array assignment in UEFI RAID firmware, initiate rebuild, and verify healthy volume status in the host OS.

Step-by-Step Solution

1
Initiate system power-down and disconnect AC power.
System is safe for internal hardware manipulation.
Motherboard M.2 NVMe slots lack hot-swap support, making power removal mandatory to prevent electrical damage.
2
Use ESD precautions to swap the failed M.2 SSD.
Defective drive removed and new SSD installed.
Physical installation must occur while the system is powered off and grounded.
3
Boot into the motherboard UEFI RAID controller utility.
Firmware interface displays degraded array and unassigned replacement drive.
The hardware/firmware RAID controller must detect the newly added storage device before the OS loads.
4
Assign the new drive to the degraded RAID 1 array and start the rebuild.
Mirroring process is initialized.
The RAID controller requires explicit configuration instructions to copy mirror data to the new drive.
5
Boot into the OS and confirm volume status.
RAID 1 array status transitions from degraded to normal/healthy.
Final validation ensures storage redundancy is verified at the operating system level.

Key Concept

RAID 1 Firmware Array Rebuild for Non-Hot-Swappable Storage
Question 28Question →

A desktop computer in an office environment suddenly loses network connectivity. A technician decides to follow the bottom-up OSI troubleshooting approach to diagnose the problem. In which order should the technician perform these steps to systematically isolate the issue?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order begins with inspecting the physical link light, followed by checking the local IP configuration with `ipconfig`, then pinging the default gateway, and finally pinging a remote IP address.
In a bottom-up troubleshooting methodology, technicians start at the Physical layer (Layer 1) by inspecting the NIC link light. Next, they verify host Layer 3 configurations using `ipconfig`. They then test local router reachability by pinging the default gateway, and lastly, test end-to-end WAN routing by pinging a remote public IP address.

Step-by-Step Solution

1
Check physical layer connectivity.
Inspect the NIC link light to confirm hardware connection.
Bottom-up troubleshooting always begins at Layer 1 (Physical).
2
Verify IP configuration.
Run `ipconfig` to view assigned IP address, subnet mask, and gateway.
Ensures the host is configured correctly on Layer 3.
3
Test local network segment.
Ping the default gateway router.
Confirms local network reachability before attempting external connections.
4
Test external network connectivity.
Ping a public remote IP address.
Validates routing through the gateway to outside networks.

Key Concept

Bottom-up OSI network troubleshooting methodology
Question 29Question →

A system administrator needs to create a custom Microsoft Management Console (MMC) interface that combines Performance Monitor and Services into a single view on a Windows 11 workstation. Arrange the steps in the correct order to successfully create and save this custom management console.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct procedural order to create a custom Microsoft Management Console is: 1) Open the Run dialog and launch `mmc.exe`, 2) Access the File menu and choose Add/Remove Snap-in..., 3) Select Performance Monitor and Services, click Add, and set them to manage the local computer, and 4) Click File, select Save As, and save the console as an `.msc` file.
Building a custom Windows management interface requires starting the bare Microsoft Management Console (`mmc.exe`), opening the snap-in selection window via File > Add/Remove Snap-in..., adding the specific snap-ins (Performance Monitor and Services) to the local computer context, and saving the result as a custom `.msc` file for future access.

Step-by-Step Solution

1
Launch the base Microsoft Management Console application.
An empty console shell opens with Console Root in the navigation pane.
The base executable `mmc.exe` must be running before custom snap-ins can be added.
2
Open the snap-in configuration dialogue box.
The Add or Remove Snap-ins management window opens.
This dialogue presents all registered Windows administrative snap-ins for selection.
3
Add Performance Monitor and Services to the Console Root.
The selected management utilities appear under the Console Root node.
Individual snap-ins must be selected and configured (e.g., set to local or remote computer) to establish console functionality.
4
Save the tailored console file.
A custom file with an `.msc` extension is saved to the chosen folder.
Saving the layout preserves the custom view so the administrator can launch it directly in the future.

Key Concept

Creating Custom Microsoft Management Consoles (MMC)
Estimated Time:1m 0s
Question 30Question →

A desktop workstation used for heavy video rendering unexpectedly powers down due to CPU overheating. Arrange the following actions in the correct sequence according to the official CompTIA 6-step troubleshooting methodology, starting with the first step to take.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order follows the standard CompTIA methodology sequence: first, identify the problem by interviewing the user and duplicating the thermal shutdown; second, establish a theory of pump failure based on log readings; third, test the pump on a known-good header to confirm failure; fourth, replace the liquid cooler with fresh thermal paste; fifth, verify system stability with a stress test and set up BIOS alerts; and sixth, document the root cause, parts used, and baseline test results in the ticketing system.
The standard CompTIA troubleshooting methodology follows six sequential steps: 1) Identify the problem, 2) Establish a theory of probable cause, 3) Test the theory to determine cause, 4) Establish a plan of action to resolve the problem and implement the solution, 5) Verify full system functionality and implement preventive measures, and 6) Document findings, actions, and outcomes. The correct order strictly respects these six phases in chronological order.

Step-by-Step Solution

1
Interview user and duplicate the unexpected shutdown during a benchmark stress test.
The issue is confirmed to be thermal throttling causing protective shutdown (Identify the problem).
Troubleshooting must always begin with gathering information and identifying symptoms before forming conclusions.
2
Develop a theory that zero pump RPM indicates liquid cooler pump motor failure.
A testable probable cause hypothesis is established (Establish a theory of probable cause).
A technician must form a logical hypothesis before taking diagnostic measurements.
3
Test pump power connections and verify pump operation on a known-good motherboard header.
The pump remains inoperative, confirming the hypothesis (Test the theory to determine cause).
Testing confirms or disproves the cause so that unnecessary component replacements are avoided.
4
Install a new liquid CPU cooler and apply new thermal paste.
The physical repair is completed (Establish a plan of action and implement the solution).
Once the theory is confirmed, the technician plans and executes the repair.
5
Perform a prolonged stress test and configure motherboard thermal alerts.
System thermal stability is verified and future monitoring is enabled (Verify full system functionality and implement preventive measures).
Verification ensures the issue is resolved and preventive measures minimize recurrence.
6
Record the ticket summary including root cause, part numbers, and thermal baseline.
Incident documentation is complete (Document findings, actions, and outcomes).
Final documentation ensures organizational knowledge transfer and historical baseline tracking.

Key Concept

CompTIA 6-Step Troubleshooting Methodology
Question 31Question →

A workstation in an office environment experiences intermittent network disconnection. A network technician decides to troubleshoot the issue using the bottom-up OSI model methodology, starting at Layer 1. Arrange the following diagnostic steps in the correct order from first (bottom layer) to last (top layer).

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order follows the bottom-up OSI model approach: first, inspect the physical RJ-45 connection and link lights (Layer 1); second, check adapter properties for frame errors and duplex settings (Layer 2); third, run ipconfig /all to verify IP configuration (Layer 3); fourth, perform a port test to confirm TCP connection capability (Layer 4); and fifth, open a web browser to test overall application access (Layer 7).
The bottom-up OSI troubleshooting approach systematically moves from Layer 1 through Layer 7. Physical connection checks (Layer 1) precede Data Link frame error checks (Layer 2), which are followed by Network IP address verification (Layer 3), Transport port connectivity testing (Layer 4), and finally Application software validation (Layer 7).

Step-by-Step Solution

1
Perform Physical Layer (Layer 1) verification.
Confirm physical cable connection and link light activity.
Troubleshooting starts at Layer 1 in a bottom-up methodology to rule out physical media defects or disconnected cabling.
2
Perform Data Link Layer (Layer 2) verification.
Verify framing, CRC error counts, and duplex settings on the NIC.
Once physical connectivity is confirmed, check for data link errors or speed/duplex mismatches.
3
Perform Network Layer (Layer 3) verification.
Verify valid IP addressing, subnet mask, and gateway settings using ipconfig.
Layer 3 troubleshooting confirms logical IP configuration and routing paths.
4
Perform Transport Layer (Layer 4) verification.
Test TCP/UDP port responsiveness.
Layer 4 confirms that end-to-end transport communication and specific port services are functioning.
5
Perform Application Layer (Layer 7) verification.
Test final user application functionality in the web browser.
Layer 7 validates that end-user applications can transmit and receive data normally across the entire network stack.

Key Concept

Bottom-up troubleshooting methodology follows OSI layer order from Physical (Layer 1) up to Application (Layer 7).
Question 32Question →

A systems technician responds to an incident where an enterprise database server's NVMe storage array suddenly enters a degraded state accompanied by severe I/O latency spikes during business hours. Place the technician's necessary actions in the correct chronological order according to the CompTIA troubleshooting methodology, starting from the first step to the final step.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct troubleshooting sequence follows the standard CompTIA six-step framework: 1) Interview the database administrator and inspect system logs (Identify the problem), 2) Analyze log entries to hypothesize a failing HBA port (Establish a theory of probable cause), 3) Relocate the connection in a test lab to verify the fault (Test the theory to determine cause), 4) Draft a change ticket, schedule maintenance, and swap the adapter (Establish a plan of action and implement the solution), 5) Run synthetic benchmark tests and configure automated monitoring (Verify full system functionality and implement preventive measures), and 6) Log the root cause and replacement details in the ticketing system (Document findings, actions, and outcomes).
The correct order strictly adheres to the official CompTIA 6-step troubleshooting methodology: Step 1 involves identifying the problem by questioning users and reviewing logs; Step 2 requires establishing a theory of probable cause based on the gathered evidence; Step 3 dictates testing the theory to confirm the root cause; Step 4 involves establishing a plan of action and implementing the solution; Step 5 verifies full system functionality and implements preventive measures; and Step 6 concludes the process by documenting findings, actions, and outcomes.

Step-by-Step Solution

1
Gather information and identify symptoms
System logs and user accounts reveal recent environment details, establishing Step 1: Identify the problem.
Troubleshooting must begin by gathering initial information and defining the scope of the issue.
2
Develop a theory of probable cause
Data points point toward a specific failing component (the PCIe HBA port), completing Step 2: Establish a theory of probable cause.
Technicians must establish a plausible theory after understanding the symptoms and system history.
3
Test the established theory
Testing the connection in a staging environment isolates the hardware defect, fulfilling Step 3: Test the theory to determine cause.
A theory must be empirically tested before making major production changes.
4
Plan and execute the solution
A plan of action is established, scheduled, and implemented, completing Step 4: Establish a plan of action and implement the solution.
Replacing parts or making structural changes requires a structured plan of action to avoid collateral outage.
5
Verify functionality and apply preventive steps
System performance is tested under load and monitoring is configured, fulfilling Step 5: Verify full system functionality and implement preventive measures.
Verification ensures the issue is completely fixed, while preventive steps minimize future occurrences.
6
Document the entire process
Full documentation is recorded in the ticketing system, completing Step 6: Document findings, actions, and outcomes.
Final documentation retains corporate knowledge and establishes historical record for future issues.

Key Concept

CompTIA 6-Step Troubleshooting Methodology Sequence
Estimated Time:2m 0s
Question 33Question →

A network technician is responding to an outage where multiple IP phones and workstations on a newly segmented VLAN lost network connectivity following a scheduled switch firmware upgrade. Place the following troubleshooting tasks in the correct sequential order according to the standard CompTIA troubleshooting methodology, starting from the first step to the final step.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence follows the CompTIA 6-step troubleshooting methodology: (1) Interview staff and inspect logs to identify the problem, (2) Analyze potential root causes to establish a theory, (3) Connect a protocol analyzer to test the theory, (4) Formulate and execute a plan of action, (5) Confirm phone/workstation functionality and configure automated config backups as a preventive measure, and (6) Update IT service management records to document findings.
The correct order strictly follows CompTIA's six troubleshooting stages: 1) Identify the problem (gathering symptoms via user interviews and logs), 2) Establish a theory of probable cause (analyzing potential causes like DHCP helper missing), 3) Test the theory (capturing traffic with a protocol analyzer), 4) Establish a plan of action and implement the solution (formulating and applying the patch), 5) Verify full system functionality and implement preventive measures (confirming client IP renewal and setting up automated backups), and 6) Document findings, actions, and outcomes (recording resolution in ITSM).

Step-by-Step Solution

1
Identify the problem
Gather information by interviewing affected personnel and examining system/switch logs.
Troubleshooting must begin with clear symptom identification and information gathering before forming hypotheses.
2
Establish a theory of probable cause
Consider potential root causes such as missing VLAN tagging or erased DHCP helper addresses post-firmware update.
Formulating theories based on gathered facts helps narrow down potential causes before performing tests.
3
Test the theory to determine cause
Use a protocol analyzer on the switch trunk port to test if DHCP traffic is properly forwarded.
Testing confirms or disproves the theory. If confirmed, proceed to planning; if disproved, establish a new theory.
4
Establish a plan of action to resolve the problem and implement the solution
Write and apply the configuration patch to restore missing relay settings.
A structured plan ensures safety and minimizes downtime during implementation.
5
Verify full system functionality and implement preventive measures
Verify that phones register and clients obtain IP addresses, then implement automated configuration backups.
Verification ensures the issue is resolved without negative side effects, and preventive measures reduce future recurrence.
6
Document findings, actions, and outcomes
Log all details, root cause analysis, and resolution steps in the ticketing system.
Documentation creates a knowledge base for future reference and organizational learning.

Key Concept

CompTIA 6-step Troubleshooting Methodology
Question 34Question →

A technician needs to replace a failed hot-swappable drive in a server's RAID 5 array. Place the recovery steps in the correct order from first to last to safely restore full array redundancy.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The proper sequence to replace a failed drive in a hot-swappable RAID 5 array is: verify a valid data backup exists, identify the failed drive using software and LEDs, replace the faulty drive with a compatible unit, and monitor the RAID rebuild process until completion.
Standard CompTIA troubleshooting methodology requires prioritizing data safety first (verifying backups), correctly isolating the failed hardware component using diagnostic tools and status LEDs, physically replacing the failed component with compatible hardware, and confirming complete operational recovery by monitoring the rebuild process.

Step-by-Step Solution

1
Verify current data backups
Protects against catastrophic data loss during array recovery operations.
RAID 5 can only sustain a single drive failure; if a second drive encounters errors during replacement, unbacked-up data will be unrecoverable.
2
Identify the faulty drive bay
Confirms the exact physical drive that has failed.
Pulling a functional drive from a degraded RAID 5 array breaks the array and causes total data loss.
3
Swap the failed drive
Replaces the dead hardware with a functional, equal-or-larger disk.
A healthy disk of appropriate size is required to store the reconstructed data blocks and parity.
4
Monitor array rebuilding
Verifies that parity reconstruction completes successfully.
The system remains degraded until the RAID controller completes recalculating parity onto the replacement disk.

Key Concept

RAID 5 Drive Replacement and Rebuild Sequence
Question 35Question →

A technician is servicing a server configured with a hardware RAID 5 storage array where a single hard drive has failed, leaving the volume operating in a degraded state. Arrange the standard recovery steps in the correct sequential order from first step to last step.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for recovering the degraded RAID 5 array is: 1) Identify the physical location of the failed disk, 2) Verify or execute a system data backup, 3) Remove the failed drive and insert a compatible replacement, 4) Initiate the array rebuild process, and 5) Monitor the rebuild progress until the status returns to Optimal.
The standard recovery procedure starts by identifying the specific failed physical disk to prevent removing an active disk. Next, performing or verifying a backup guards against catastrophic data loss if another disk fails while fault tolerance is down. After securing backups, hot-swapping the bad drive with a compatible unit prepares the array for data reconstruction. Initiating the rebuild recalculates parity data across the remaining drives onto the new disk. Finally, monitoring the array until its health status shows Optimal verifies that redundancy has been completely restored.

Step-by-Step Solution

1
Identify the failed physical drive slot
Pinpoints the faulty disk without interrupting active drives
Prevents human error during physical maintenance.
2
Verify or create an array data backup
Secures data integrity against secondary drive failure
A degraded RAID 5 array has zero fault tolerance until rebuilt.
3
Replace the physical drive
Places functional hardware in the server bay
Physical installation must occur before parity data can be written.
4
Start the RAID rebuild operation
Parity recalculation begins writing to the new drive
The array controller must mathematically restore missing data chunks onto the target disk.
5
Verify final array status
Array health status changes from Degraded to Optimal
Confirms fault tolerance is re-established for normal operations.

Key Concept

RAID 5 Degraded Array Drive Replacement Sequence
Question 36Question →

A system technician is servicing an enterprise server configured with a hardware RAID 5 array that has generated a 'Degraded' status alert due to a single drive failure. In what chronological sequence should the technician perform the following steps to safely replace the failed drive and restore fault tolerance?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of operations is: 1) Identify the specific faulty drive slot using the RAID management console and drive bay LED status indicators. 2) Verify the presence of a complete current backup of the array volume data. 3) Remove the failed drive from the hot-swap enclosure and install a replacement drive of equal or greater capacity. 4) Assign the new drive to the logical volume or trigger the array rebuild process in the RAID controller interface. 5) Monitor the rebuilding status until the RAID utility reports an Operational/Optimal state.
The correct procedural order ensures data safety and system integrity. First, identifying the failed drive bay via management software or physical LEDs prevents pulling an operational drive from a degraded array. Second, verifying or making a backup protects against catastrophic data loss if a secondary drive fails during the high-stress rebuild phase. Third, replacing the faulty drive with an appropriately sized spare physically fixes the broken hardware component. Fourth, assigning the new drive or triggering the rebuild in the RAID controller starts parity recalculation. Finally, monitoring the rebuild until completion guarantees that fault tolerance is restored.

Step-by-Step Solution

1
Diagnose and locate the faulty disk drive.
The technician confirms the exact physical bay location of the failed disk.
Accurate identification prevents accidental removal of a functional drive, which would cause immediate catastrophic failure of a degraded RAID 5 array.
2
Verify or create a full volume data backup.
Critical data is safeguarded prior to heavy hardware rebuild operations.
Rebuilding parity subjects remaining operational disks to extensive read stress, elevating the likelihood of an unrecoverable read error (URE) or secondary drive failure.
3
Perform physical drive replacement.
The defective disk is replaced with a functional drive meeting hardware specifications.
The system requires a compatible, fully functioning disk with equal or greater storage capacity to restore array structure.
4
Initiate RAID array rebuild procedure.
The RAID controller software registers the replacement disk and begins background parity recalculation.
Physical replacement alone does not always start reconstruction unless assigned manually or configured as a hot spare.
5
Confirm complete rebuild and system redundancy.
The storage array status transitions from Degraded back to Optimal.
Ongoing verification ensures parity synchronization completes without error before returning the server to full production use.

Key Concept

RAID 5 Degraded State Recovery & Sequential Drive Replacement Procedure
Question 37Question →

A system administrator receives a predictive failure alert on Disk 2 of a four-drive hardware RAID 5 array hosting an active file share. To replace the failing disk while protecting data integrity and restoring array redundancy, in what sequential order should the administrator perform the following steps?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct procedural order is: first, perform a verified backup of the current RAID volume data; second, set the failing physical drive to an offline status using the RAID management utility; third, remove the failing drive from the drive bay and seat the compatible replacement drive; fourth, initiate the RAID volume rebuild process through the controller interface; fifth, monitor the rebuild progress until the volume status transitions back to Optimal.
The standard technician workflow for addressing predictive drive failures in hardware RAID arrays demands data protection prior to physical hardware manipulation. Creating a fresh backup protects against secondary drive failure. Taking the disk offline logically ensures clean separation from the controller. Physical drive replacement follows, after which initiating and monitoring the rebuild until status reaches Optimal completes the restoration of fault tolerance.

Step-by-Step Solution

1
Execute a full, verified backup of the RAID 5 array.
Recent volume state is safely preserved on secondary storage.
RAID 5 can only sustain a single drive failure; backing up first mitigates catastrophic data loss if another disk encounters unrecoverable read errors during the rebuild.
2
Log into the RAID controller utility and set the predictive failure disk offline.
The controller logically unmounts the drive from the array.
Prevents OS/controller I/O hangs or data corruption during physical extraction.
3
Hot-swap the failing physical disk with a new disk of equal or greater capacity.
New blank drive is physically installed in the target bay.
Provides the physical medium required to accept parity reconstruction.
4
Assign the new drive as a hot spare or manually start the rebuild process in the utility.
The controller begins calculating parity and writing missing block data to the new drive.
Parity recalculation is necessary to reconstruct the data of the replaced drive.
5
Track rebuild logs until the array health returns to Optimal.
Volume redundancy is fully restored.
Ensures the rebuild process finishes without write failures or bad sectors.

Key Concept

RAID 5 Predictive Failure and Hot-Swap Rebuild Procedure
Question 38Question →

An IT support technician is tasked with resolving an issue where a interactive digital signage kiosk in a corporate lobby unexpectedly reboots during operation. Place the following technician actions in the correct sequential order according to the CompTIA 6-step troubleshooting methodology, starting with the first action.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence follows the standard CompTIA troubleshooting framework: 1. Gather information and review logs (Identify the problem), 2. Develop a thermal overheating hypothesis (Establish a theory of probable cause), 3. Monitor CPU temperatures with diagnostic tools (Test the theory), 4. Clean heat sinks and reapply thermal paste (Implement the solution), 5. Run continuous telemetry checks and set up a monthly maintenance schedule (Verify functionality and implement preventive measures).
The standard CompTIA troubleshooting model follows a strict linear sequence: 1. Identify the problem (interviewing staff and checking logs), 2. Establish a theory of probable cause (hypothesizing thermal throttling from dust), 3. Test the theory (monitoring temperatures in diagnostics), 4. Implement the solution (cleaning components and replacing thermal paste), 5. Verify system functionality and implement preventive measures (testing telemetry and scheduling recurring maintenance), and 6. Document findings.

Step-by-Step Solution

1
Identify the problem by gathering details.
Discovered thermal error logs and user reports of sudden reboots.
Troubleshooting must always start by collecting symptoms and identifying what has changed.
2
Establish a theory of probable cause.
Formulated a theory that dust buildup is causing CPU thermal shutdowns.
A technician must consider potential root causes after identifying problem symptoms.
3
Test the theory to confirm the cause.
Diagnostic tools verified CPU temperatures exceeded safe operational thresholds.
Testing the theory confirms whether the hypothesis is correct before implementing changes.
4
Plan and implement the solution.
Cleaned heat sink assembly and refreshed thermal compound.
Once the cause is verified, physical maintenance and repairs are carried out.
5
Verify full functionality and implement preventive measures.
Confirmed stable operating temperatures under load and scheduled monthly maintenance.
Verification ensures the fix resolved the issue without secondary failures, while preventive measures guard against recurrence.

Key Concept

CompTIA 6-Step Troubleshooting Methodology Sequence
Question 39Question →

A field technician is troubleshooting an enterprise workstation that experiences intermittent PCIe bus resets during hardware-accelerated batch operations. According to the CompTIA 6-step troubleshooting methodology, in what sequence should the technician perform the following diagnostic and remediation steps from first to last?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological order follows the standard 6-step CompTIA methodology: (1) Interview the workstation user and examine event logs, (2) Formulate a hypothesis regarding UEFI firmware issues, (3) Install the card in a controlled test system to verify the cause, (4) Schedule a maintenance window to flash the UEFI and adjust PCIe settings, (5) Perform multi-hour DMA load testing and set up automated monitoring alerts, and (6) Log the firmware versions and test results in the ticketing system.
The standard CompTIA troubleshooting framework requires executing steps in strict sequence: Step 1 (Identify the problem), Step 2 (Establish a theory of probable cause), Step 3 (Test the theory to determine cause), Step 4 (Establish a plan of action to resolve the problem and implement the solution), Step 5 (Verify full system functionality and, if applicable, implement preventive measures), and Step 6 (Document findings, actions, and outcomes). The correct order directly aligns each action item with these consecutive stages.

Step-by-Step Solution

1
Identify the problem
Information gathered from user questioning and event log examination.
Troubleshooting must always start by gathering symptoms and establishing baseline information.
2
Establish a theory of probable cause
Plausible theory formulated regarding UEFI firmware bus allocation conflicts.
Technicians must establish a theory before attempting disruptive hardware or firmware changes.
3
Test the theory to determine cause
Theory validated via isolated synthetic bench testing.
Testing confirms or refutes the theory without risking production data or altering production configurations prematurely.
4
Establish a plan of action and implement the solution
Plan created for maintenance window and UEFI update successfully applied.
Once the cause is proven, a controlled plan of action is designed and executed.
5
Verify full system functionality and implement preventive measures
Continuous load testing confirms stability; automated bus alerts configured.
Verification ensures the fix resolved the issue, while monitoring prevents future unobserved recurrences.
6
Document findings, actions, and outcomes
Ticketing system updated with resolution details and benchmark data.
Final documentation creates a historical knowledge base for future incident resolution.

Key Concept

CompTIA 6-Step Troubleshooting Methodology
Question 40Question →

A desktop technician is assigned to troubleshoot a high-end graphics workstation that unexpectantly shuts down during intensive 3D rendering tasks. Place the technician's diagnostic and remedial actions in the correct sequential order according to the CompTIA 6-step troubleshooting methodology, from first action to last action.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order follows the standard CompTIA troubleshooting process: first interview the user and review event logs (Identify the problem), second formulate a hypothesis regarding thermal failure (Establish a theory), third run a stress test while monitoring hardware sensors (Test the theory), fourth clean the cooling components and reapply thermal paste (Implement the solution), and fifth perform a stress test to confirm fix and document findings (Verify system functionality and Document).
The correct sequence strictly adheres to the standard 6-step CompTIA troubleshooting methodology: 1. Identify the problem (gather user reports and logs), 2. Establish a theory of probable cause (hypothesize thermal throttling), 3. Test the theory (stress-test with temperature monitoring), 4. Implement the solution (clean heatsink and reapply thermal paste), and 5. Verify full system functionality and document findings (stress-test validation and ticket documentation).

Step-by-Step Solution

1
Gather diagnostic details from user reports and event logs.
Identified symptoms and error logs indicating thermal emergency shutdowns.
CompTIA Step 1 requires identifying the problem before forming theories or taking action.
2
Develop a theory regarding heat dissipation failure.
Targeted clogged heatsink fins and old thermal compound as probable cause.
CompTIA Step 2 requires establishing a theory of probable cause based on collected data.
3
Test the thermal theory using diagnostic software under load.
Confirmed CPU thermal limits were breached under stress.
CompTIA Step 3 requires testing the theory to confirm the cause before modifying physical components.
4
Clean heatsink fins, reapply thermal paste, and reassemble cooling.
Physical solution implemented successfully.
CompTIA Step 4 requires establishing a plan of action and implementing the solution.
5
Run extended workload test to confirm stability and record resolution notes.
System validated under load and ticketing record completed.
CompTIA Steps 5 & 6 require verifying full system functionality and documenting the outcome.

Key Concept

CompTIA 6-Step Troubleshooting Methodology
PreviousPage 2 / 22Next
All practice questions — CompTIA A+ (Core 1 & Core 2) | Examkin