Hardware and Network Troubleshooting practice questions

The file server is powered off.

Why wrong: If the file server were powered off, no device on the network would be able to access its shares. The problem states that other devices *can* access the shares, which directly contradicts the idea of the server being offline. Furthermore, the laptop's ability to access the internet indicates that its basic network connectivity is functional, pointing away from a server-side issue affecting only one client.

The Wi-Fi router is overloaded.

Why wrong: An overloaded Wi-Fi router would typically manifest as widespread network performance issues, affecting *all* connected devices, not just a single laptop. Since other devices are working fine and the laptop itself can access the internet, the router is clearly capable of handling traffic and performing its routing functions. This scenario points to a client-specific configuration problem rather than a general network infrastructure bottleneck.

The laptop's firewall is blocking all traffic.

Why wrong: If the laptop's firewall were blocking all traffic, it would be unable to connect to *any* network resources, including the internet. The fact that the laptop can successfully access the internet directly contradicts the statement that its firewall is blocking all traffic. While a firewall *could* be configured to selectively block local network access while allowing internet access, the option specifically states "all traffic," making it incorrect.

Verify the printer's DNS settings

Why wrong: Verifying the printer's DNS settings would be crucial if the SMTP server address was provided as a hostname and the printer was unable to resolve it to an IP address. However, if the problem statement implies the "server address is correct," it suggests either an IP address is configured directly, or the hostname resolution has already succeeded. Therefore, DNS is unlikely the root cause of an email delivery failure if the server address itself is deemed correct and reachable.

Replace the printer's toner cartridge

Why wrong: Replacing the printer's toner cartridge is entirely unrelated to the functionality of scanning documents and sending them via email. Toner is a consumable material specifically required for the printing process, where it is fused onto paper to create physical output. The 'scan to email' function is a digital process that does not involve printing, rendering toner levels irrelevant to its operation.

Reboot the network switch

Why wrong: Rebooting the network switch is a broad troubleshooting step that would disrupt network connectivity for all connected devices and is generally reserved for widespread network issues. Since the printer has a valid IP address, it indicates that basic network layer connectivity is established, and the printer can communicate on the local network. Therefore, a switch reboot is an unnecessary and potentially disruptive action that would not address a specific email authentication problem.

Enable Secure Boot

Why wrong: Secure Boot is a UEFI firmware feature designed to enhance system security by preventing the loading of unauthorized operating system bootloaders and drivers during startup. It verifies the digital signatures of boot components against a database of trusted certificates to ensure system integrity. While crucial for protecting against rootkits and malware, Secure Boot does not directly enable or facilitate hardware-level virtualization, which relies on specific CPU extensions for efficient hypervisor operation.

Enable Execute Disable Bit (XD/NX)

Why wrong: Execute Disable Bit (Intel XD) or No-Execute bit (AMD NX) is a CPU security feature that marks certain memory regions as non-executable. This hardware-enforced protection helps prevent specific types of malicious code, such as buffer overflow attacks, from running in data-only memory areas, thereby enhancing system security. Although a vital security measure, XD/NX is unrelated to the CPU's ability to support or accelerate virtualization technologies, which require dedicated instruction sets for direct hardware access.

Set SATA mode to AHCI

Why wrong: Advanced Host Controller Interface (AHCI) is a technical standard that defines an operation mode for SATA controllers, enabling advanced features like Native Command Queuing (NCQ) and hot-swapping. Its primary purpose is to improve the performance and functionality of SATA hard drives and solid-state drives by optimizing data transfer and command processing. AHCI is a storage interface standard and has no direct bearing on the CPU's ability to perform hardware-level virtualization; it only affects how storage devices communicate with the system.

The 5 GHz SSID is hidden and requires manual entry.

Why wrong: While a hidden SSID could prevent automatic connection, the tablets would still see the network if they support 5 GHz. The symptom is that they cannot connect at all, not that they can't find it.

The corporate 5 GHz network requires 802.1X authentication that is not configured on the tablets.

Why wrong: While 802.1X authentication is common in corporate environments, it is a security protocol that comes into play *after* a device has successfully detected and attempted to associate with the wireless network. If the tablets were capable of seeing the 5 GHz network, they would typically display the SSID and then prompt the user for the required authentication credentials or certificate. The core problem described is the inability to connect *at all*, implying they cannot even detect the network, making authentication a secondary, non-root cause.

The tablets have a defective Wi-Fi antenna.

Why wrong: A defective Wi-Fi antenna would typically impair the tablet's ability to connect to *any* wireless network, regardless of the frequency band. Since the tablets are able to connect successfully to 2.4 GHz networks, this indicates that their Wi-Fi antennas are functional and capable of receiving and transmitting signals. A problem specifically with 5 GHz connectivity, while 2.4 GHz works, points away from a general antenna defect and towards a band-specific hardware or configuration issue.

The switch is a hub, not a switch.

Why wrong: A hub operates at Layer 1 of the OSI model, simply repeating all incoming electrical signals to every other port. While this creates a single collision domain and significantly reduces network performance due to frequent collisions, all devices connected to a hub remain within the same broadcast domain. Consequently, devices would still be able to send and receive broadcast frames, such as ARP requests, allowing them to discover and communicate with each other at Layer 2, even if internet access is slow.

The router is blocking multicast traffic.

Why wrong: Routers primarily operate at Layer 3 and are designed to segment networks, preventing broadcast and multicast traffic from traversing between different subnets by default. However, local network discovery protocols, like ARP or NetBIOS over TCP/IP, rely on broadcasts or link-local multicasts that occur *within* the same Layer 2 segment (e.g., a single switch or VLAN). Therefore, if the desktop computer and other local devices are on the same subnet and switch, the router's multicast blocking configuration would not impact their ability to discover each other locally.

The Ethernet cable is a crossover cable.

Why wrong: Historically, a crossover Ethernet cable was required to connect two similar devices directly (e.g., PC to PC, switch to switch) by swapping the transmit and receive wire pairs. However, virtually all modern network interface cards (NICs) and network switches are equipped with Auto-MDIX (Automatic Medium-Dependent Interface Crossover) technology. This feature automatically detects the cable type and adjusts the port's wiring configuration as needed, rendering crossover cables largely obsolete. If Auto-MDIX were not present or failed, a crossover cable would typically result in a complete link failure, preventing any network communication whatsoever, rather than just a loss of local visibility.

Replace the HDMI cable.

Why wrong: Replacing the HDMI cable is not the initial troubleshooting step because the external monitor has already been confirmed to function correctly with another device, indicating the monitor's input port and the cable itself are likely operational. While a cable could still be intermittently faulty or damaged in a way specific to this laptop's output, it is more efficient to first verify the laptop's display output settings and activation, which are common causes of a 'No Signal' message.

Update the graphics driver.

Why wrong: Updating the graphics driver is generally not the immediate solution for a complete 'No Signal' message, as driver issues typically manifest after a display signal is established, causing artifacts, incorrect resolutions, or system instability. A lack of any signal at all usually points to a fundamental output setting or hardware activation problem, rather than a software rendering or compatibility fault. This step should be considered only after basic display output activation has been confirmed.

Check the monitor's power cable.

Why wrong: Checking the monitor's power cable is an unnecessary troubleshooting step in this scenario because the customer explicitly stated the external monitor works correctly when connected to another device. This confirms that the monitor itself is receiving power, is functional, and its internal components are operational. The problem is therefore isolated to the laptop's ability to output a signal, not the monitor's power supply or general functionality.

The BIOS settings for primary display adapter

Why wrong: While BIOS/UEFI settings can designate a primary display adapter, most modern motherboards are configured to automatically prioritize a dedicated PCIe graphics card when one is detected. It is less common for a default BIOS setting to prevent display output from a newly installed, functional discrete GPU, especially if the card is otherwise receiving power and its fans are spinning. Manual intervention in BIOS is usually only needed for specific multi-GPU setups or troubleshooting.

The graphics card power connectors are properly attached

Why wrong: Although the graphics card's fans are spinning, indicating it receives some power from the PCIe slot, high-performance dedicated GPUs require additional direct power from the power supply via 6-pin or 8-pin PCIe power connectors. However, a complete lack of these supplemental power connections would typically prevent the card from fully initializing or even spinning its fans, often triggering diagnostic LEDs or POST errors. Since the fans are spinning, the card is likely receiving enough power to initiate, making missing power connectors less probable as the sole cause of 'no display' compared to other issues.

The PCIe slot is damaged

Why wrong: A damaged or faulty PCIe slot would most likely prevent the system from detecting the graphics card entirely, leading to a complete lack of functionality. In such a scenario, the card would not receive power through the slot, meaning its fans would not spin, and the system would likely fail to POST or display specific error codes. The fact that the graphics card's fans are spinning indicates that the PCIe slot is at least providing basic power and allowing initial communication with the card.

Port 22 and 23

Why wrong: Port 22 is exclusively reserved for Secure Shell (SSH), which provides a secure, encrypted channel for remote command-line access, file transfers, and tunneling services. Conversely, Port 23 is used by Telnet, an older, unencrypted protocol for remote terminal access. Neither of these protocols is designed for the collection of network device statistics or sending alerts, which are the primary functions of network monitoring tools utilizing SNMP.

Port 80 and 443

Why wrong: Port 80 is the standard port for Hypertext Transfer Protocol (HTTP), facilitating unencrypted communication for web browsing and accessing web-based services. Port 443 is used by HTTPS (HTTP Secure), which encrypts HTTP traffic using SSL/TLS for secure web communication. While network monitoring tools might have web interfaces accessible via these ports, HTTP/HTTPS are not the underlying protocols for gathering device metrics or receiving traps from network devices via SNMP.

Port 67 and 68

Why wrong: Port 67 is designated for the Dynamic Host Configuration Protocol (DHCP) server, which listens for incoming requests from clients seeking IP addresses and other network configuration parameters. Port 68 is used by DHCP clients to send their initial requests to the server and receive configuration offers. These ports are fundamental for IP address management within a network and have no functional role in the process of network monitoring or the operation of SNMP.

The router's firewall is blocking traffic between VLANs.

Why wrong: If the router's firewall were blocking inter-VLAN traffic, it would typically be a deliberate security policy rather than an accidental misconfiguration preventing basic communication. Since users can ping their own default gateway, the router is reachable, suggesting the issue isn't a complete block of all router-bound traffic. A firewall would specifically deny forwarding packets between different subnets/VLANs, but the core problem here seems to be the router not receiving traffic from all VLANs to begin with for routing.

The default gateway for VLAN 20 is misconfigured.

Why wrong: The problem statement indicates that users in VLAN 20 can ping their default gateway. This directly refutes a misconfigured default gateway, as they would be unable to reach it if the IP address or subnet mask was incorrect. A misconfigured gateway would prevent any outbound communication from VLAN 20 to any other network, including other VLANs or the internet, because packets wouldn't know where to go to leave their local subnet.

The switch has Spanning Tree Protocol enabled, blocking the link.

Why wrong: Spanning Tree Protocol (STP) is designed to prevent network loops by blocking redundant paths between switches. In a typical inter-VLAN routing setup, there is usually only a single physical link connecting the switch to the router. STP would not block this essential, non-redundant link, as doing so would isolate the entire network segment from the router and other VLANs. If STP were blocking this link, users in all VLANs would be unable to reach their default gateways.

255.255.240.0

Why wrong: This subnet mask corresponds to a /20 CIDR prefix. If applied to a Class B network (e.g., /16), it borrows 4 bits for subnetting, resulting in 2^4 = 16 available subnets. While this provides more than the required 8 subnets, it leaves only 12 host bits, allowing for 2^12 - 2 = 4094 usable hosts per subnet. This is less efficient and provides fewer hosts than the optimal solution, which typically aims for the minimum number of subnets to meet the requirement while maximizing host capacity.

255.255.248.0

Why wrong: This subnet mask translates to a /21 CIDR prefix. Utilizing 5 bits for subnetting (e.g., from a /16 network) would create 2^5 = 32 subnets, which is significantly more than the 8 subnets required. Furthermore, with only 11 host bits remaining, each subnet would support 2^11 - 2 = 2046 usable hosts. This provides an excessive number of subnets and a considerably lower host count per subnet compared to the optimal solution.

255.255.192.0

Why wrong: This subnet mask corresponds to a /18 CIDR prefix. When applied to a Class B network (e.g., /16), it borrows only 2 bits for subnetting. This configuration would result in 2^2 = 4 available subnets, which is insufficient to meet the requirement of creating 8 separate subnets. Although it would provide a large number of hosts (2^14 - 2 = 16382) per subnet, the primary condition of having enough subnets is not satisfied.

Use a crossover cable to connect the router directly to the WAP.

Why wrong: Using a crossover cable for a direct router-to-WAP connection would consume the router's single LAN port, leaving no direct connection point for the rest of the office network, which requires a switch. While modern devices often support auto-MDI/MDIX, eliminating the specific need for a crossover cable, the fundamental problem remains the router's limited port capacity. This setup fails to provide connectivity for additional devices beyond the WAP, making it an impractical solution for a small office network needing multiple connections.

Use a hub between the router and the switch.

Why wrong: Using a hub would create a single collision domain and half-duplex connections, failing the requirement to connect both the switch and WAP to the router’s single LAN port without an uplink port, as a hub cannot isolate traffic between devices. It is tempting because a hub provides additional ports to physically connect multiple devices, and it would be the correct choice in a scenario where all connected devices must share the same broadcast and collision domain, such as for legacy network traffic monitoring.

Configure the switch as a router to connect to the WAP.

Why wrong: A typical unmanaged network switch operates at Layer 2 of the OSI model, forwarding data frames based on MAC addresses, and lacks the necessary Layer 3 routing capabilities. Configuring such a switch to function as a router, which handles IP address-based packet forwarding and network address translation (NAT), is not possible. Even managed switches with some Layer 3 features are primarily designed for switching and would not typically replace a dedicated router for internet gateway functions in this context.

The PC's network cable is faulty.

Why wrong: If the PC's network cable, or the segment connecting the phone to the PC, were faulty, the PC would experience a complete loss of connectivity. However, the VoIP phone itself is reported as working, which indicates the primary network connection to the wall jack and the phone's internal networking components are functional. While a specific cable segment *to the PC* could be bad, the phone's operational status points away from a general cable fault as the primary cause for the PC's lack of connectivity.

The VoIP phone's passthrough port is disabled.

Why wrong: Many enterprise VoIP phones include an integrated switch, providing a passthrough port (often labeled PC) to connect a computer using a single wall jack. While disabling this port would prevent the PC from obtaining network access, most phones have this feature enabled by default for convenience. It would require a deliberate administrative action, either locally on the phone or via a centralized management system, to disable the passthrough functionality, making it an uncommon default issue.

The PC's network adapter is set to a static IP address that conflicts with the phone.

Why wrong: An IP address conflict occurs when two or more devices on the same network segment are assigned identical IP addresses. If the PC's network adapter had a static IP address that conflicted with the VoIP phone, both devices would experience intermittent or complete network connectivity issues, not just the PC. Since the VoIP phone is reported as working correctly, an IP address conflict between the PC and the phone is highly improbable.

Multimeter

Why wrong: While a multimeter can technically measure voltage, it is not the appropriate tool for quickly and safely detecting Power over Ethernet (PoE) on an RJ-45 jack. It would require precise knowledge of the specific PoE standard's pin assignments (e.g., Mode A or Mode B) and careful, manual probing of individual pins, which is impractical and carries a risk of shorting circuits or damaging equipment. This method is far less efficient and reliable than using a dedicated PoE tester.

Cable tester

Why wrong: A standard cable tester's primary function is to verify the physical integrity and correct wiring of an Ethernet cable. It checks for continuity, open circuits, short circuits, and proper pinout (e.g., T568A or T568B), ensuring data can transmit reliably. However, it lacks the internal circuitry and sensors required to detect or measure the presence of electrical power, such as Power over Ethernet, on the data lines.

Loopback plug

Why wrong: A loopback plug is a diagnostic tool used to test the functionality of a network interface card (NIC) or a network port by sending data out and immediately receiving it back on the same interface. It verifies the transmit and receive capabilities of the hardware itself, confirming that the port is operational for data communication. This tool provides no information regarding the presence or absence of Power over Ethernet on the connected cable or port.

Increase the transmit power of the access point.

Why wrong: Increasing the transmit power of an access point amplifies its signal, potentially extending its range. However, this action does not address channel congestion; instead, it can exacerbate the problem by increasing the noise floor for neighboring networks and causing more co-channel or adjacent-channel interference. Stronger signals from a congested source will only make it harder for other devices and networks to communicate effectively, leading to worse performance.

Disable SSID broadcast to hide the network.

Why wrong: Disabling SSID broadcast is a security measure intended to make a network less visible to casual users, not a method to reduce channel congestion. While it hides the network's name from standard client scans, the wireless signal continues to be transmitted on the same frequency channel, occupying the same airwaves. Therefore, it has no impact on mitigating interference from other networks or alleviating the amount of traffic already present on that specific channel.

Replace the access point with a higher-gain antenna model.

Why wrong: Replacing an access point with a higher-gain antenna model primarily serves to extend the physical range and directivity of the wireless signal. While this might improve signal strength for clients at a greater distance, it does not alter the operating channel or reduce the amount of data traffic on that channel. In fact, by projecting a stronger signal further, a higher-gain antenna could potentially increase interference with more distant networks, thereby worsening overall channel congestion rather than resolving it.

The DNS server is unreachable

Why wrong: An unreachable DNS server would prevent name resolution, meaning the laptop could not translate domain names to IP addresses for web browsing or accessing network resources by name. However, the device would still successfully obtain an IP address from a functioning DHCP server. The presence of a 169.254.x.x APIPA address indicates a failure in the fundamental IP address acquisition process itself, which occurs before any DNS resolution attempts.

The default gateway is misconfigured

Why wrong: A misconfigured default gateway would impact a device's ability to communicate with hosts outside its local subnet, preventing access to the internet or other networks. However, it would not prevent the device from obtaining a valid IP address, subnet mask, and DNS server information from a DHCP server. The client would still receive a proper IP, only failing when attempting to route traffic beyond its immediate network segment.

The network cable is faulty

Why wrong: While a faulty network cable can certainly prevent network connectivity, the assignment of an APIPA address implies that a physical link has been established and the network adapter is active. If the cable were completely faulty, disconnected, or the network interface card (NIC) was disabled, the operating system would typically report no link status, and the device would not even attempt DHCP or subsequently assign an APIPA address.

Install Windows 7 in a dual-boot configuration

Why wrong: Dual-booting involves installing two separate operating systems on different partitions of the same physical hard drive. While this allows the legacy application to run natively in Windows 7, it necessitates a full system reboot to switch between operating systems. This method prevents simultaneous use of the legacy application alongside modern applications on the primary OS, introducing significant downtime and workflow disruption for a business environment.

Deploy Windows 11 and use Windows 7 compatibility mode

Why wrong: Windows compatibility mode attempts to mimic specific environmental settings of older operating systems for a particular application. However, it primarily adjusts minor API calls and system behaviors, not fundamental architectural differences or deep-seated dependencies that a true legacy application might have. This method is often insufficient for complex or highly integrated legacy software, which frequently fails to run correctly or at all, even with these settings applied.

Replace the legacy application with a cloud-based alternative

Why wrong: Replacing a legacy application with a cloud-based alternative represents a significant business transformation rather than a technical solution for running the existing software. This option involves substantial costs for migration, potential data conversion, retraining staff, and ongoing subscription fees, which might not be feasible or desirable for a small business. Furthermore, it does not address the immediate technical challenge of maintaining the current legacy application's functionality.

Infrastructure mode WLAN; configure a laptop as a software access point.

Why wrong: Infrastructure mode WLAN inherently relies on a central access point (AP) to manage connections and forward data between devices. While configuring a laptop as a software access point can create this central point, it still functions as an intermediary, routing all traffic. This contradicts scenarios where direct, peer-to-peer communication without any central device, even a temporary software one, is desired for simplicity or lack of dedicated hardware.

PAN network using Bluetooth; all laptops pair via Bluetooth.

Why wrong: A Personal Area Network (PAN) using Bluetooth is designed for connecting a small number of personal devices over very short distances, typically less than 10 meters. While it can facilitate file transfers, its limited throughput (speed) and restricted number of simultaneous connections (often 7 active devices in a piconet) make it impractical for efficiently sharing files among multiple laptops. Wi-Fi-based solutions offer significantly greater range, speed, and scalability for such a task.

Mesh network; each laptop acts as a node forwarding traffic.

Why wrong: A mesh network requires each laptop to forward traffic for others, but the scenario demands direct file sharing without any central access point or router. This fails because mesh nodes still rely on routing protocols and multi-hop forwarding, which introduces complexity and dependency on intermediary devices. It is tempting because mesh networks are designed for decentralised, ad-hoc connectivity in environments lacking infrastructure, such as disaster recovery sites, where they would be the correct choice for resilient, self-healing communication.

The iPhone's DNS settings are misconfigured.

Why wrong: If the iPhone's DNS settings were misconfigured, the device would likely connect to the Wi-Fi network but fail to resolve domain names for *any* internet resource, not just after connecting to a public hotspot. While the captive portal page itself might load via IP redirection, subsequent attempts to browse the web would result in "server not found" errors. This issue typically affects all internet access uniformly, rather than being specific to the initial public Wi-Fi authentication phase.

The iPhone's Wi-Fi antenna is faulty.

Why wrong: A faulty Wi-Fi antenna on the iPhone would primarily manifest as an inability to detect available networks, extremely weak signal strength even when in close proximity to an access point, or persistent connection drops. Since the iPhone successfully connects to the public Wi-Fi hotspot, it indicates that the device's antenna and radio components are functioning adequately to establish a physical and data link layer connection. Therefore, a faulty antenna is inconsistent with the described scenario.

The public Wi-Fi network is using an incompatible security protocol.

Why wrong: If the public Wi-Fi network were employing a security protocol incompatible with the iPhone's capabilities, the device would be unable to establish a connection to the access point at all. The iPhone would either fail to authenticate, display an error message during the connection attempt, or simply be unable to join the network. The fact that the iPhone *connects* to the hotspot rules out an incompatible security protocol as the root cause of the lack of internet access.

Replace the CPU with a known good one

Why wrong: Replacing the CPU is a drastic and expensive troubleshooting step that should only be considered after ruling out more common and easily diagnosable issues. Random lockups are frequently caused by faulty RAM, overheating, or power supply problems, which are simpler to test. Swapping a CPU requires careful handling, thermal paste application, and often disassembling the cooling system, making it an inefficient initial diagnostic.

Update the motherboard BIOS to the latest version

Why wrong: Updating the motherboard BIOS is primarily intended to resolve compatibility issues with new hardware, improve system stability, or fix specific firmware bugs. While it can sometimes address obscure system behaviors, it is an unlikely solution for random lockups, which often point to a hardware fault like failing RAM or an unstable power supply. Furthermore, a failed BIOS update can render the motherboard inoperable, making it a risky step without strong evidence it's the cause.

Check the CPU voltage in BIOS and increase it slightly

Why wrong: Adjusting CPU voltage in the BIOS is an advanced technique primarily used for overclocking or stabilizing an under-volted CPU, not a standard diagnostic procedure for random lockups. Increasing voltage unnecessarily can lead to excessive heat generation, reduced component lifespan, and further system instability or damage. Unless there's specific evidence of insufficient voltage, such as under-clocking or a known power delivery issue, this action introduces more variables and risks rather than diagnosing the root cause.

The DHCP server is out of IP addresses.

Why wrong: If the DHCP server were truly exhausted, the laptop would fail to obtain an IP address for any interface configured for DHCP, including the wired Ethernet connection. Since the user can connect via Ethernet, the DHCP server is demonstrably functioning and assigning IP addresses. This indicates the issue is specific to the wireless connection's ability to request or receive an IP, not the server's overall capacity.

The wireless adapter driver is corrupted.

Why wrong: A corrupted or faulty wireless adapter driver typically manifests as the adapter not being recognized by the operating system, failing to initialize, or being unable to detect any wireless networks whatsoever. The fact that the user can see available networks indicates the driver is at least functional enough to scan for and identify SSIDs, making a fundamental driver corruption unlikely to be the root cause of connection failure.

The router’s SSID is hidden.

Why wrong: If a router's Service Set Identifier (SSID) is configured to be hidden (broadcast disabled), the network name will not appear in the list of available wireless networks that the laptop's adapter detects. To connect to a hidden network, the user must manually enter the SSID and security information. Since the user *sees* available networks, including presumably the target network, the SSID cannot be hidden.