During a remote-support session, you learn that a standalone Linux web server stopped responding to HTTP and SSH just after 03:00. Other servers on the same subnet are reachable, and the data-center switch shows the server's access port in an up state. You have already reviewed syslog, found no kernel panics, and confirmed that no patches were applied overnight. According to the CompTIA troubleshooting methodology, which action best illustrates questioning the obvious while you establish a theory of probable cause?
Open an urgent case with the OS vendor to request a driver hotfix.
Inspect the server's NIC link light and reseat the network cable or transceiver to confirm a solid physical connection.
Schedule downtime to replace the server's backplane and retest connectivity.
Capture a full memory dump to look for kernel deadlocks affecting the TCP stack.
When establishing a theory of probable cause, technicians should first eliminate simple, obvious issues before moving to complex or invasive tests. Verifying that the server's NIC really has link (for example, checking the link light and reseating the cable or SFP) is a classic "question the obvious" task because loose or unseated connections are common, easy-to-overlook causes of network outages. The other actions either assume a complex root cause (memory analysis), require service disruption (backplane swap), or immediately escalate outside the organization, none of which aligns with the "start simple, work toward the complex" guidance in the methodology.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a NIC and why is it important in a server?
Open an interactive chat with Bash
What does 'link light' indicate on a NIC, and why is it important?
Open an interactive chat with Bash
What is the CompTIA troubleshooting methodology and its key steps?