Examkin

All practice questions

423 questions

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

A desktop workstation brought to the IT bench turns on when the power button is pressed, but the system fails to complete the Power-On Self-Test (POST) and emits a continuous sequence of beeps. The technician needs to isolate whether the root cause stems from a power delivery issue, motherboard failure, or memory module corruption. In what order should the technician perform the diagnostic and isolation steps below, from first to last, according to standard hardware troubleshooting methodology?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of steps is: 1) Visually inspect the motherboard and power connections, 2) Clear CMOS settings to restore defaults, 3) Strip the system down to a bare-bones configuration, and 4) Swap memory modules with known-good RAM or test alternate slots.
Effective CompTIA troubleshooting moves from the least invasive and simplest steps to more complex hardware isolation. First, perform a visual inspection for physical motherboard damage and cable seating. Next, clear CMOS settings to rule out invalid BIOS configurations. Then, establish a minimal boot configuration by disconnecting non-essential hardware. Finally, swap RAM modules or test alternate slots to isolate specific component defects.

Step-by-Step Solution

1
Inspect hardware physically and verify power connections.
Rules out physical motherboard damage (distended capacitors, burnt traces) and loose power cables.
Always begin with non-invasive visual checks before changing hardware configurations.
2
Reset CMOS/RTC configuration.
Clears bad firmware settings or corrupted RAM timings that interfere with POST.
Eliminates software/firmware misconfigurations quickly before removing physical hardware components.
3
Establish minimal boot hardware configuration.
Isolates failures caused by shorted add-in cards or overloaded power rails from non-essential devices.
Simplifies the diagnostic domain to only core essential components necessary for POST.
4
Isolate memory using known-good components or alternate slots.
Differentiates between a faulty RAM stick and a defective motherboard memory slot.
Hardware replacement and slot rotation are definitive isolation tests used when core components are isolated.

Key Concept

Standard Hardware Troubleshooting Methodology for POST and Power Isolation
Question 62Question →

A security administrator needs to audit unauthorized file access attempts on a confidential folder stored on a Windows 11 Pro workstation. The administrator must enable system-wide object access auditing, configure the target folder's access control list, and verify that failed attempts generate entries in the Security log. Place the administrative steps in the correct order required to accomplish this configuration.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with opening Local Security Policy (secpol.msc), enabling Failure auditing under Local Policies > Audit Policy > Audit object access, navigating to the folder's Advanced Security settings Auditing tab in File Explorer, defining a SACL entry for 'Everyone' with Fail permissions, and finally verifying generated Audit Failure records within Event Viewer's Security log.
Configuring object access auditing in Windows requires a top-down administrative workflow. First, the administrator must enable the global auditing engine by launching Local Security Policy (secpol.msc) and enabling Failure auditing under Local Policies > Audit Policy > Audit object access. Second, the administrator must target the specific file system resource by opening the folder properties in File Explorer, accessing Advanced Security settings, and creating a System Access Control List (SACL) entry for the target group (e.g., Everyone) with Type set to Fail for Read/Execute permissions. Third, the administrator validates the implementation by checking Event Viewer (eventvwr.msc) under Windows Logs > Security to inspect generated Audit Failure events.

Step-by-Step Solution

1
Launch the Local Security Policy console (secpol.msc).
The Local Security Policy management window opens.
Global auditing capabilities in Windows are managed centrally through local security policies.
2
Navigate to Security Settings > Local Policies > Audit Policy, open 'Audit object access', and enable the 'Failure' checkbox.
The OS is instructed to track failed attempts to access objects that possess SACL auditing entries.
Without enabling global object access auditing, configuring auditing on individual folders will have no effect.
3
Open File Explorer, right-click the target folder, choose Properties, select the Security tab, and click Advanced.
The Advanced Security Settings dialog box for the folder opens.
NTFS object auditing requires configuring the object's System Access Control List (SACL) via the Auditing tab.
4
Switch to the Auditing tab, click Add, specify the principal 'Everyone', set Type to 'Fail', and check Read & execute permissions.
A SACL rule is attached to the folder monitoring failed access attempts.
This specific rule links user access failures on this folder to the system audit mechanism.
5
Launch Event Viewer (eventvwr.msc) and navigate to Windows Logs > Security.
The Security log presents generated audit entries including Event ID 4656/4663 Audit Failures.
Event Viewer allows administrators to review and verify that security event logs are actively recording access failures.

Key Concept

Configuring Object Access Auditing in Windows via Local Security Policy (secpol.msc), File Explorer SACL Properties, and Event Viewer (eventvwr.msc)
Estimated Time:2m 0s
Question 63Question →

A systems administrator needs to collect baseline metrics on a Windows 11 Pro workstation experiencing intermittent memory pressure. The administrator decides to create a custom log using Performance Monitor to sample available memory every 15 seconds. In what sequential order should the administrator perform the following steps to configure this Data Collector Set?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for configuring a Performance Monitor custom log is: 1) Open Performance Monitor and expand Data Collector Sets, 2) Right-click User Defined and select New > Data Collector Set, 3) Name the set, choose 'Create manually (Advanced)', and select 'Performance counter', 4) Add the \Memory\Available MBytes counter and set the sample interval to 15 seconds, and 5) Specify the output directory and execution credentials to finish.
To create a custom performance log, the administrator must first open Performance Monitor (perfmon.msc) and locate Data Collector Sets. Right-clicking User Defined and choosing New > Data Collector Set starts the configuration wizard. In the wizard, naming the set and selecting 'Create manually (Advanced)' allows specifying 'Performance counter' data. Next, the administrator adds the target metric (\Memory\Available MBytes) and sets the sample interval to 15 seconds. Finally, specifying the storage location and execution account commits the Data Collector Set.

Step-by-Step Solution

1
Launch Performance Monitor (perfmon.msc)
Access the Performance Monitor management console hierarchy.
Administrative tasks in Performance Monitor require accessing the console tree.
2
Navigate to Data Collector Sets > User Defined and initiate a new set
Opens the Create New Data Collector Set Wizard.
User Defined sets allow creation of custom log files tailored to specific troubleshooting needs.
3
Configure wizard settings for manual performance counter collection
Sets the log type to Performance counter.
Manual creation is required to select specific individual counters instead of system default templates.
4
Add \Memory\Available MBytes and set sample rate to 15 seconds
Defines what metric is logged and how frequently data points are sampled.
Specific counters and sample rates fulfill the metric collection requirement.
5
Define file location and run-as permissions, then finish
Saves the Data Collector Set under User Defined ready to be started.
Logs require a target disk directory and appropriate user context to run continuously in the background.

Key Concept

Configuring User Defined Data Collector Sets in Windows Performance Monitor
Estimated Time:1m 30s
Question 64Question →

A technician needs to refresh the IPv4 configuration on a Windows client workstation using the command line. Place the steps in the correct order from first to last to properly release, renew, and verify the network configuration.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order is: Open the Windows Command Prompt, run `ipconfig /release` to drop the current IP lease, run `ipconfig /renew` to request a new lease from the DHCP server, and run `ipconfig /all` to verify the assigned configuration.
To refresh a DHCP lease on Windows, a technician must first open the command-line interface, release the existing lease using `ipconfig /release`, request a new lease using `ipconfig /renew`, and finally inspect the resulting setup with `ipconfig /all`.

Step-by-Step Solution

1
Open Command Prompt
Command-line environment is available for administrative networking tasks.
CLI commands must be executed within an active shell environment.
2
Execute `ipconfig /release`
Sends a DHCPRELEASE message to the DHCP server and clears local IPv4 configuration.
The existing IP address must be released before requesting a fresh lease.
3
Execute `ipconfig /renew`
Sends a DHCPREQUEST message to obtain a new IP address, subnet mask, default gateway, and DNS configuration.
Obtaining a new configuration establishes functional network parameters.
4
Execute `ipconfig /all`
Displays detailed IP settings to confirm successful lease assignment.
Verification confirms that proper IP parameters were received and applied.

Key Concept

Windows Command-Line DHCP Renewal Procedure
Question 65Question →

A systems administrator needs to configure an automated system recovery workflow on a Windows 11 Pro workstation. Whenever a critical system service unexpectedly terminates and generates Event ID 7031 in the System event log, a custom remediation script must automatically execute with elevated administrative privileges. Place the steps in the correct chronological order to complete this configuration using Windows administrative tools.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence begins by selecting the target event in Event Viewer, invoking 'Attach Task To This Event...', confirming the pre-filled event trigger parameters, specifying 'Start a program' with the script path, and finally enabling 'Run with highest privileges' in the task properties.
To automate recovery upon a specific Windows event, the administrator must first isolate the event in Event Viewer to use the 'Attach Task To This Event...' shortcut. This transfers the event filter attributes directly to Task Scheduler. After confirming the trigger criteria and setting the action to run the recovery script, the administrator must access the task's full properties to enable 'Run with highest privileges.' Without elevation, the automated script would fail due to insufficient User Account Control (UAC) permissions when attempting to restart system services.

Step-by-Step Solution

1
Locate the target log entry in Event Viewer
Event metadata for Event ID 7031 is selected in the System log view.
Event Viewer requires highlighting an existing log entry to pass its log source and event ID into the task wizard.
2
Invoke the context menu action 'Attach Task To This Event...'
The Create Basic Task Wizard opens with event parameters pre-configured.
This shortcut links Event Viewer directly to Task Scheduler, streamlining event-triggered task creation.
3
Confirm trigger parameters
Event log, source, and Event ID settings are validated.
Verifying pre-populated data ensures the task fires only when Event ID 7031 is generated.
4
Configure the task action
'Start a program' is selected and pointed to the script location.
Task Scheduler requires an explicit action definition (program/script execution) to carry out remediation.
5
Set execution privileges in Task Scheduler properties
'Run with highest privileges' is selected under administrative credentials.
Standard user context cannot restart Windows services; elevated privileges are necessary for system service management.

Key Concept

Event-Triggered Administrative Tasks and Privilege Elevation
Question 66Question →

A Tier 1 desktop support technician needs to reconfigure a Windows workstation network adapter that failed to update its network settings after a router restart. Arrange the following steps in the correct order to open the command interface, release the existing lease, acquire a new IP address assignment, and verify the updated networking details.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence is: Launch Command Prompt with elevated administrative privileges, run ipconfig /release to drop the current IP configuration, run ipconfig /renew to request new settings from the DHCP server, and run ipconfig /all to confirm the newly assigned IP address and subnet mask.
Proper IP address reassignment using Windows command-line tools follows a strict chronological workflow: first, elevated administrative privileges must be obtained by opening Command Prompt as Administrator; second, the existing invalid DHCP configuration is unassigned using ipconfig /release; third, a new IP lease is solicited using ipconfig /renew; and finally, verification of all configuration settings is performed using ipconfig /all.

Step-by-Step Solution

1
Launch the command line interpreter with administrative rights.
Command Prompt window opens in Administrator mode.
Administrative rights are necessary to modify local system network interface settings.
2
Execute the lease release command.
The current IP address configuration bound to the network adapter is cleared.
The client must notify the DHCP server that it is releasing its current binding before asking for new parameters.
3
Execute the lease renewal command.
The workstation receives a fresh IP address, subnet mask, and default gateway.
The renewal command broadcasts a DHCP DISCOVER/REQUEST sequence to obtain active network configuration details.
4
Execute the full configuration output command.
Complete TCP/IP configuration information for all adapters is output to the console.
Inspecting the full output confirms that the network settings match the target subnet requirements.

Key Concept

Windows Network Adapter Command Line Management (ipconfig)
Question 67Question →

A technician is dispatched to replace an empty paper roll in a direct thermal point-of-sale (POS) receipt printer. In what order should the technician perform the following steps to ensure proper installation and test the printer?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with opening the top cover, clearing the old roll core, inserting the new roll with the thermal coating oriented correctly toward the printhead, closing the cover over a short leader of paper, and ending with a feed test to confirm output.
The proper maintenance workflow for a direct thermal printer requires unlatching the cover, removing the spent paper core, placing the new roll with the heat-sensitive side facing the printhead, closing and latching the lid over a small extension of paper, and finally conducting a feed/self-test to verify legibility.

Step-by-Step Solution

1
Open the printer cover
Gains physical access to the internal paper bay.
The cover must be unlatched first before old materials can be removed.
2
Remove the old core
Frees up space in the compartment for new media.
The leftover spool will block proper seating of a new roll if not removed.
3
Orient and place the thermal roll into the bay
Ensures the chemically coated side of the paper faces the thermal printhead.
Direct thermal printers use heat-sensitive paper; if loaded upside down, the heat cannot react with the chemically treated side, causing blank prints.
4
Extend a paper leader and close the lid securely
Engages the platen roller and paper sensor assembly.
Proper tension and roller contact are required to prevent paper jams.
5
Perform a paper feed and test print operation
Verifies mechanical traction and legible text rendering.
Testing confirms the replacement was successful before placing the device back into service.

Key Concept

Direct Thermal Printer Paper Loading Procedure
Question 68Question →

A network technician is dispatched to troubleshoot a workstation that suddenly lost all network connectivity after an office redesign. Following the standard CompTIA bottom-up (Layer 1 through Layer 7) network troubleshooting methodology, in what sequence should the technician perform the diagnostic actions below?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The proper bottom-up diagnostic sequence begins with verifying physical link lights and cables (Layer 1), checking local IP configuration with ipconfig (Layer 2/3), testing the loopback address (127.0.0.1) for stack integrity, pinging the default gateway for subnet connectivity, and finally testing DNS domain name resolution with nslookup.
Following the standard CompTIA bottom-up troubleshooting methodology, technicians work sequentially from Layer 1 up to Layer 7. The process starts by checking cables and link lights (Physical), reviewing local adapter configuration with ipconfig, verifying the internal TCP/IP stack with loopback ping (127.0.0.1), testing subnet routing by pinging the default gateway, and lastly verifying higher-layer services like DNS hostname resolution with nslookup.

Step-by-Step Solution

1
Verify Layer 1 Physical Layer connectivity
Ensure patch cable is connected securely and physical link lights are lit on both the host NIC and wall jack.
Troubleshooting higher layers is ineffective if physical connectivity is broken.
2
Inspect local IP configuration using ipconfig /all
Determine if the host has a valid DHCP configuration, static IP, or an APIPA address.
Identifies whether the NIC has established a link and communicated with local network services.
3
Test local TCP/IP protocol stack using ping 127.0.0.1
Verify that the local operating system protocol drivers are installed and processing packets.
Confirms the host software stack can send and receive ICMP traffic internally.
4
Test local subnet network pathway by pinging the default gateway
Confirm connectivity between the local workstation and the subnet router interface.
Validates that frames and packets travel across the local network segment successfully.
5
Test Application/Name Resolution services using nslookup
Confirm DNS servers resolve human-readable domain names to destination IP addresses.
Verifies end-to-end high-level application functionality and name resolution services.

Key Concept

OSI Model Bottom-Up Network Troubleshooting
Question 69Question →

A systems administrator needs to reconfigure a single-partition disk on a Windows 11 workstation to establish a dedicated data volume using command-line tools. The administrator launches an elevated Command Prompt and starts the DiskPart utility. In what order should the administrator execute the DiskPart sub-commands to reduce the OS partition size and initialize the new formatted data volume?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence in DiskPart is: 1) select volume 1, 2) shrink desired=50000, 3) create partition primary, 4) format fs=ntfs quick, 5) assign letter=D.
The sequence follows the standard DiskPart workflow for non-destructive volume splitting: target selection (`select volume`), releasing unallocated space (`shrink`), building the partition metadata (`create partition`), file system initialization (`format`), and OS drive mounting (`assign`).

Step-by-Step Solution

1
Execute `select volume 1`
Sets the focus of the DiskPart session to the existing primary system/data volume.
DiskPart requires a target volume context before performing volume modification actions.
2
Execute `shrink desired=50000`
Reduces the size of Volume 1 by 50,000 MB (approx. 50 GB) and creates contiguous unallocated space.
Unallocated space is required on the disk before a secondary partition can be established.
3
Execute `create partition primary`
Allocates the unallocated space into a new primary partition structure.
DiskPart must define the partition boundaries on the disk prior to file system creation.
4
Execute `format fs=ntfs quick`
Initializes the NTFS file system metadata structures on the new partition.
Raw partition space cannot store files until it is formatted with a compatible file system.
5
Execute `assign letter=D`
Mounts the formatted partition under drive letter D: in the operating system.
Assigning a letter completes the disk configuration and makes the volume available to users and services.

Key Concept

DiskPart command-line partition management workflow
Estimated Time:2m 0s
Question 70Question →

A network technician needs to resolve an IP configuration conflict and clear cached name resolution issues on a Windows 11 client computer configured for dynamic addressing. Place the steps in the correct sequential order to release the existing DHCP lease, clear the DNS cache, request a new IP address configuration, and verify the updated network adapter settings using the Command Prompt.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct troubleshooting sequence is: first, execute `ipconfig /release` to drop the current dynamic IP lease; second, run `ipconfig /flushdns` to purge stale cached DNS resolution records; third, execute `ipconfig /renew` to request updated network parameters from the DHCP server; and finally, execute `ipconfig /all` to verify that all adapter configuration details have been successfully updated.
The proper network refresh procedure requires unbinding the current IP address first (`ipconfig /release`), clearing cached DNS lookups (`ipconfig /flushdns`), requesting a fresh set of IP settings from the DHCP server (`ipconfig /renew`), and validating the final active configuration (`ipconfig /all`).

Step-by-Step Solution

1
Release the active IPv4 lease using `ipconfig /release`.
The network interface card relinquishes its currently assigned IP address.
Releasing the existing configuration clears potential lease conflicts prior to requesting updated parameters.
2
Clear the local DNS resolver cache using `ipconfig /flushdns`.
All cached DNS host-to-IP lookup entries are deleted from memory.
Purging stale or incorrect DNS entries prevents ongoing name resolution errors.
3
Obtain a new DHCP lease using `ipconfig /renew`.
The network interface obtains a fresh IP address, subnet mask, gateway, and DNS server addresses from DHCP.
Renewing prompts the client to negotiate a new lease with the DHCP server.
4
Verify the resulting network configuration using `ipconfig /all`.
A full readout of all active adapter parameters, including DHCP server and lease times, is presented.
Inspecting the full configuration validates that all network parameters were correctly received and applied.

Key Concept

Windows Command-Line Network Configuration and DHCP/DNS Troubleshooting Sequence
Question 71Question →

A network technician needs to manually assign static network settings and verify connectivity on a Windows 11 client workstation using command-line tools after a local DHCP server failure. In what sequence should the technician perform the following steps to assign the static IP address, subnet mask, default gateway, and primary DNS server, and then verify hostname resolution?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with opening an elevated Command Prompt, followed by setting the static IP address, subnet mask, and gateway using netsh, configuring the static DNS server address via netsh, verifying applied settings with ipconfig /all, and finally testing DNS name resolution using nslookup.
The proper sequence requires securing elevated Command Prompt privileges first. Next, the static IP, subnet mask, and default gateway are assigned using 'netsh interface ipv4 set address'. Then, the static DNS server is configured using 'netsh interface ipv4 set dnsservers'. After configuring the adapter, local settings must be verified using 'ipconfig /all'. Finally, end-to-end DNS name resolution is tested using 'nslookup'.

Step-by-Step Solution

1
Open Command Prompt with Run as Administrator permissions
Elevated CLI session ready for system configuration commands
Modifying Windows network adapter settings via netsh requires administrative privileges.
2
Execute netsh interface ipv4 set address command
Static IPv4 address, subnet mask, and default gateway configured on the specified network adapter
Basic TCP/IP addressing and routing infrastructure must be established prior to higher-layer service setup.
3
Execute netsh interface ipv4 set dnsservers command
Primary DNS server IP address bound to the interface
DNS settings require the dnsservers option context in netsh after IP address assignment.
4
Run ipconfig /all to display detailed configuration output
Active IPv4, gateway, and DNS settings displayed for verification
Confirms local operating system recognition of applied static parameters.
5
Run nslookup to query a target domain name
DNS server responds with the mapped IP address
Validates functional domain name resolution through the newly configured network adapter.

Key Concept

Windows Client Network Configuration using Netsh and Diagnostic Utilities
Question 72Question →

A desktop support technician is assigned to resolve an issue on a workstation used by a financial analyst. The computer powers on and internal fans spin, but the system fails to complete the Power-On Self-Test (POST) and emits a repeating sequence of three long beeps.

Place the technician's troubleshooting actions in the correct chronological order according to the standard CompTIA 6-step troubleshooting methodology, starting with the initial step.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order follows the standard 6-step CompTIA Troubleshooting Methodology: 1) Interview the user and observe startup symptoms (Identify the problem), 2) Cross-reference the beep code to hypothesize memory failure (Establish a theory of probable cause), 3) Test RAM modules individually to confirm the fault (Test the theory to determine cause), 4) Draft a plan and install the replacement RAM module (Establish a plan of action and implement the solution), 5) Run memory diagnostics and verify normal OS boot (Verify full system functionality), and 6) Log all findings and resolution details in the ticketing system (Document findings, actions, and outcomes).
The correct sequence adheres strictly to the official CompTIA troubleshooting methodology: Step 1 (Identify the problem) precedes Step 2 (Establish a theory of probable cause), which must be followed by Step 3 (Test the theory to determine cause). Once the cause is confirmed, Step 4 (Establish a plan of action and implement the solution) takes place, followed by Step 5 (Verify full system functionality), and finishes with Step 6 (Document findings, actions, and outcomes).

Step-by-Step Solution

1
Identify the problem
Information gathered from user inquiry and physical observation of the system failure.
CompTIA methodology requires gathering symptoms and questioning users before attempting any diagnostic tests or changes.
2
Establish a theory of probable cause
Formulated hypothesis pointing to a failed memory module.
Analyzing symptoms against technical documentation helps isolate potential points of failure.
3
Test the theory to determine cause
Confirmed that a specific RAM module is defective through isolation testing.
Testing confirms or disproves the theory before time or money is spent on unnecessary parts or repairs.
4
Establish a plan of action to resolve the problem and implement the solution
Obtained and installed a functional replacement RAM module.
Fixing the problem requires a planned implementation strategy after the cause is verified.
5
Verify full system functionality
System successfully passes POST and memory diagnostics without errors.
System verification ensures that the repair fixed the original issue without introducing new problems.
6
Document findings, actions, and outcomes
Ticket closed with complete details recorded.
Documentation builds an organizational knowledge base for future troubleshooting.

Key Concept

CompTIA 6-Step Troubleshooting Methodology
Question 73Question →

A technician is servicing a production workstation configured with a hardware RAID 1 array. The RAID controller management console displays a status of 'Degraded' due to a disk failure in drive slot 1. The workstation uses hot-swappable drive bays. In what order should the technician perform the following steps to replace the faulty drive and restore array redundancy?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The proper sequence begins by verifying system backups and confirming the target drive ID, removing the failed hot-swappable disk from slot 1, inserting a compatible replacement drive, and finally initiating and monitoring the RAID array rebuild in the controller management software.
The correct procedural order ensures data safety and system integrity. First, verifying a current backup and confirming the target drive identifier prevents accidental removal of a healthy drive. Second, removing the faulty hot-swappable disk clears slot 1. Third, installing a new drive with equal or greater capacity provides the hardware base for rebuilding. Finally, triggering or confirming the automatic rebuild process synchronizes the mirrored data to restore full RAID 1 fault tolerance.

Step-by-Step Solution

1
Verify backup integrity and identify target disk
Confirmed valid backup and precise identification of drive slot 1.
Prevents catastrophic data loss in case of secondary failure and avoids removing the wrong drive.
2
Remove the failed hot-swappable drive
Slot 1 is empty and ready for a replacement drive.
Hot-swappable hardware allows physical removal without shutting down the active workstation.
3
Install the replacement disk
New disk is physically seated and recognized by the bus/controller.
The replacement disk must meet or exceed the capacity of the original member disk.
4
Rebuild and verify array redundancy
The array status changes from Degraded back to Optimal upon 100% completion.
Data from the remaining drive must be synchronized to restore fault tolerance.

Key Concept

RAID 1 Drive Replacement and Array Synchronization
Question 74Question →

A network administrator is performing command-line network configuration on a Windows 11 workstation where the graphical interface is unresponsive. The workstation requires static IPv4 configuration and complete connectivity verification. Place the administrative command-line steps in the correct chronological order required to identify the adapter name, apply IPv4 parameters, configure the primary DNS server, confirm local TCP/IP stack functionality, and test domain name resolution.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of administrative CLI commands is: 1) Execute `netsh interface ipv4 show interfaces` to identify the interface name. 2) Execute `netsh interface ipv4 set address ...` to configure static IP, subnet mask, and default gateway. 3) Execute `netsh interface ipv4 set dnsservers ...` to assign the primary DNS server. 4) Execute `ping 127.0.0.1` to verify local TCP/IP protocol stack initialization. 5) Execute `nslookup server1.domain.local` to validate DNS name resolution.
The correct sequence starts with discovering the exact interface identifier using `netsh interface ipv4 show interfaces`. Next, static IP, subnet mask, and default gateway settings are applied using `netsh interface ipv4 set address`. Once base IP configuration is set, `netsh interface ipv4 set dnsservers` assigns the target DNS server. Testing begins locally with `ping 127.0.0.1` to confirm TCP/IP stack binding, and concludes with `nslookup` to confirm end-to-end host name resolution.

Step-by-Step Solution

1
Identify the target network interface identifier.
Obtained the exact interface string (e.g., "Ethernet").
Netsh context commands require an accurate interface name parameter to modify specific network adapters.
2
Configure static IPv4 parameters on the interface.
Static IP, subnet mask, and default gateway are assigned to the network interface.
Layer 3 addressing must be configured before higher-level services or DNS server settings can be assigned.
3
Assign the primary static DNS server address.
The client network adapter is updated with the static DNS server IP.
DNS server configuration relies on valid local interface IP addressing to send outbound queries.
4
Test local TCP/IP loopback connectivity.
Successful echo requests from 127.0.0.1.
Pinging the loopback address verifies that the Windows TCP/IP protocol stack is active and properly initialized.
5
Verify domain name resolution using nslookup.
Hostname is resolved to an IP address by the configured DNS server.
Validates that DNS resolution works over the newly configured static network parameters.

Key Concept

Command-Line Windows Network Configuration and Troubleshooting Sequence
Question 75Question →

A technician is troubleshooting a server workstation that powers on but fails to complete the Power-On Self-Test (POST), emitting a repeating continuous beep pattern. According to CompTIA hardware troubleshooting methodology, in what sequence should the technician perform the following isolation steps to determine the root cause?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence to isolate the No-POST issue is: 1) Disconnect non-essential external peripherals and internal expansion cards; 2) Test power supply output voltages using a multimeter or PSU tester; 3) Perform a CMOS clear operation to reset BIOS parameters; 4) Isolate memory channels using a single known-good RAM module sequentially across DIMM slots.
The correct order strictly follows standard diagnostic isolation rules: strip down the machine to minimum boot requirements first, verify power delivery stability second, reset system configuration state third, and perform single-component swapped testing fourth. This prevents secondary devices or bad power from generating misleading memory beep codes.

Step-by-Step Solution

1
Strip system to minimal boot configuration
Eliminates secondary devices as potential causes of POST failure.
Removing unnecessary expansion cards and peripherals prevents secondary short circuits or bus contention from masking the core failure.
2
Measure power supply voltage rails
Verifies that +12V, +5V, and +3.3V power rails are operating within standard tolerance levels.
Unstable power delivery can cause random memory corruption or improper POST beep indications.
3
Clear motherboard CMOS settings
Resets UEFI/BIOS parameters to default factory values.
Eliminates bad memory frequency settings or invalid overclocking profiles that trigger POST memory beep codes.
4
Test individual RAM modules and DIMM slots
Pinpoints the exact faulty component between DIMM modules and motherboard memory channels.
Testing a single known-good module systematically isolates whether a RAM stick or motherboard slot has failed.

Key Concept

Standardized CompTIA hardware diagnostic isolation methodology for motherboard, power, and memory POST failures.
Question 76Question →

An IT technician is dispatched to address a ticket regarding a corporate laser printer that produces persistent vertical dark lines across all printed pages. The technician has already identified the problem by interviewing users and reviewing sample printouts. According to the CompTIA troubleshooting methodology, in what sequence should the technician execute the remaining steps to resolve the issue?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence follows the CompTIA troubleshooting methodology: 1) Test the theory by inspecting the drum and performing a halfway stop test, 2) Establish a plan of action to replace the drum assembly, 3) Implement the solution by installing the new drum cartridge and cleaning internal components, 4) Verify full system functionality and configure drum life monitoring alerts, and 5) Document findings, actions, and outcomes in the ticketing system.
The CompTIA troubleshooting methodology follows six strict sequential steps: 1) Identify the problem (already completed in the stem context), 2) Establish a theory of probable cause, 3) Test the theory to determine the cause, 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. Placing drum inspection and halfway stop testing first properly tests the theory. Creating a repair plan comes next, followed by performing the physical replacement. Verifying print output and setting up drum alerts satisfies verification and prevention. Finally, logging tickets completes the documentation stage.

Step-by-Step Solution

1
Test the theory of probable cause
Confirming whether physical drum damage or toner buildup causes the vertical streaks via inspection and a halfway stop test.
Before replacing hardware, the technician must test the theory to confirm the root cause.
2
Establish a plan of action
Outlining the specific repair steps, required replacement components, and safety procedures.
A structured plan ensures all necessary safety steps and replacement components are prepared before starting work.
3
Implement the solution
Replacing the photosensitive drum cartridge and clearing stray toner from internal rollers.
Executing the planned repair physically resolves the identified hardware fault.
4
Verify full system functionality and implement preventive measures
Printing test documents to confirm defect resolution and configuring automated maintenance alerts.
Ensures the system functions properly without side effects and helps prevent future unmonitored component failures.
5
Document findings, actions, and outcomes
Recording complete service history and component serial numbers in the IT help desk system.
Provides historical documentation for future technicians and updates asset management databases.

Key Concept

CompTIA 6-Step Troubleshooting Methodology applied to Laser Printer Hardware Maintenance
Question 77Question →

A IT technician needs to identify and close a frozen background application process that is consuming excessive system memory on a Windows workstation using command-line utilities. In which logical sequence should the technician execute the following steps to identify and terminate the process?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins by opening an elevated Command Prompt, running tasklist to locate the Process ID (PID), attempting a standard termination with taskkill /PID, and finally using taskkill /F /PID to force termination if the process remains unresponsive.
The correct troubleshooting procedure starts by launching an elevated Command Prompt to ensure sufficient administrative permissions. Next, tasklist must be run to retrieve the specific Process ID (PID) of the hung application. Following identification, a standard taskkill /PID command should be issued to gracefully end the process. If the application remains stuck and ignores the initial request, taskkill /F /PID is used to forcefully terminate the process.

Step-by-Step Solution

1
Open Command Prompt as Administrator.
Elevated CLI environment is accessible.
Process query and termination commands require elevated administrative rights.
2
Run tasklist to query running processes.
Obtain the precise PID associated with the hung application.
You must obtain the unique identifier (PID) or image name to target the correct executable.
3
Run taskkill /PID <PID_number>.
Sends a graceful close request to the target PID.
Standard troubleshooting best practice dictates trying a soft termination before forcing closure.
4
Run taskkill /F /PID <PID_number>.
Forcefully halts the unresponsive process.
The /F switch is necessary to forcefully terminate frozen processes that ignore standard shutdown signals.

Key Concept

Windows Command-Line Process Troubleshooting
Question 78Question →

A desktop support technician is troubleshooting a Windows 11 workstation experiencing persistent network stack corruption and invalid socket bindings that prevent all web traffic. Standard GUI troubleshooter fixes have failed. The technician opens an administrative Command Prompt to perform a complete CLI-based network stack reset and system reboot. Place the command execution steps in the correct operational sequence to resolve the issue.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence begins with flushing the DNS resolver cache (ipconfig /flushdns), followed by resetting the Winsock API catalog (netsh winsock reset), then resetting the TCP/IP protocol stack registry state (netsh int ip reset), and finally performing an immediate system restart (shutdown /r /t 0).
Resolving severe CLI network transport failures requires systematically clearing stored DNS records, resetting corrupt socket API layers via netsh winsock reset, restoring TCP/IP protocol registry keys via netsh int ip reset, and finally executing shutdown /r /t 0 to reload system kernel drivers.

Step-by-Step Solution

1
Execute ipconfig /flushdns in elevated Command Prompt.
Purges all local DNS cache entries from memory.
Clears invalid address resolutions before altering underlying protocol layers.
2
Execute netsh winsock reset.
Restores the Windows Sockets catalog to default operational state.
Fixes socket binding errors and removes corrupted network interface hooks.
3
Execute netsh int ip reset.
Overwrites IPv4 and IPv6 registry parameters with default values.
Ensures core TCP/IP stack configuration parameters are completely restored.
4
Execute shutdown /r /t 0.
Reboots the operating system immediately without delay.
Commits Winsock and TCP/IP kernel driver modifications upon system initialization.

Key Concept

Windows Network Stack Remediation CLI Workflow
Question 79Question →

A technician needs to manually assign a static IPv4 address and DNS server on a Windows client workstation using the legacy Network Connections applet. In what sequence should the technician perform the following steps from start to finish?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts by opening Network Connections using ncpa.cpl, opening the Ethernet adapter properties, selecting TCP/IPv4 properties, specifying the static IP address details, and finally entering the DNS server address before saving.
Configuring a static IPv4 address on Windows using ncpa.cpl requires a logical progression: first open Network Connections using the run command ncpa.cpl, open the network adapter properties menu, select Internet Protocol Version 4 (TCP/IPv4) properties, change the selection to manually enter the IP address parameters (IP, Subnet Mask, Default Gateway), and finally set the DNS server address and save the settings.

Step-by-Step Solution

1
Launch the Network Connections control panel applet
Network adapters installed on the Windows system are displayed
Opening ncpa.cpl quickly navigates directly to network interfaces without navigating through Windows Settings.
2
Open adapter properties
The network interface properties dialog opens showing configured network components
Component properties must be accessed to modify specific network protocol bindings.
3
Open IPv4 properties
The IPv4 address configuration window opens
TCP/IPv4 controls the IP addressing schema utilized for local and remote network communication.
4
Configure static IP parameters
Manual fields for IP Address, Subnet Mask, and Default Gateway are populated
Switching from 'Obtain an IP address automatically' enables static field entry.
5
Configure DNS settings and apply changes
Static IP settings and name resolution servers are saved to the interface
Domain name resolution relies on configured DNS server addresses to translate hostnames to IP addresses.

Key Concept

Windows TCP/IPv4 Manual Client Configuration via Network Connections Applet
Question 80Question →

A systems administrator needs to create an automated alert in Windows 11 Pro that monitors system CPU utilization and automatically executes a maintenance script whenever CPU usage exceeds 90%90\%. Place the administrative configuration steps in Performance Monitor (`perfmon.msc`) into the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts by opening Performance Monitor and creating a manual User Defined Data Collector Set, selecting Performance Counter Alert to configure the % Processor Time counter and 90% threshold, configuring the Alert Action properties to trigger the maintenance task, and finally starting the Data Collector Set.
To build an automated alert-driven workflow in Windows Performance Monitor, an administrator must first create a User Defined Data Collector Set manually (`perfmon.msc`). Next, the collector type must be set to 'Performance Counter Alert' with the specific counter (`% Processor Time`) and threshold (`90%`). After creation, opening the alert properties allows configuring the 'Alert Action' to launch a pre-created task from Task Scheduler. Finally, the Data Collector Set must be started so Windows active monitoring begins.

Step-by-Step Solution

1
Launch Performance Monitor (`perfmon.msc`) and create a manual User Defined Data Collector Set.
Establishes a custom container for performance tracking rules.
Custom alerts cannot be added directly to default system templates without creating a User Defined set first.
2
Configure the collector type as a Performance Counter Alert with the % Processor Time counter set to exceed 90%.
Defines the specific metric and quantitative threshold that constitutes an alert condition.
Performance Monitor requires an Alert-type collector rather than a Data Log collector when monitoring for threshold breaches.
3
Configure the Alert Action properties of the created alert collector to run a defined Task Scheduler task.
Associates the threshold breach event with an automated action (the maintenance script).
The Alert Action tab within the collector properties is where Windows binds event triggers to automated Task Scheduler actions.
4
Start the User Defined Data Collector Set.
Activates background monitoring.
Newly created Data Collector Sets remain in a stopped state until explicitly started.

Key Concept

Performance Monitor Data Collector Sets and Alert Actions
Estimated Time:2m 0s
PreviousPage 4 / 22Next
All practice questions — CompTIA A+ (Core 1 & Core 2) | Examkin