During a scheduled maintenance window, you are troubleshooting a production Linux file server that sporadically loses connectivity to its iSCSI storage array. Your investigation has narrowed the probable causes to either an outdated NIC driver on the server or an MTU mismatch on the upstream switch port. Backups are verified and affected users have already been notified. According to CompTIA's recommended troubleshooting methodology when implementing a solution, what is the most appropriate next step?
Change the switch MTU and update the NIC driver during the same outage to shorten downtime.
Restore the server from the most recent full backup image to eliminate both potential causes at once.
Update the NIC driver, test storage connectivity, and only attempt another fix if the problem remains.
Escalate the incident to the storage vendor immediately since the issue spans the network fabric.
CompTIA's troubleshooting process stresses making one change at a time and immediately testing to see whether that single modification resolves the problem. Doing so lets you confirm the root cause, prevents needless downtime, and simplifies rollback if the fix fails. Updating the NIC driver first and then verifying storage connectivity follows that best practice. Applying multiple fixes at once, re-imaging the server, or escalating before attempting any carefully planned change all skip this critical "one change, then test" discipline and therefore do not align with 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 an iSCSI storage array?
Open an interactive chat with Bash
What is MTU and why does a mismatch cause issues?
Open an interactive chat with Bash
Why is updating the NIC driver important in troubleshooting?