N10-009 Question 293
Single answerImplement the solution or escalate as necessaryA network technician is troubleshooting intermittent connectivity for users in a small branch office. After identifying that a recently installed access switch has multiple ports negotiating to half-duplex because of a bad configuration template, the technician updates the affected switch ports to auto-negotiate correctly. Users report that performance immediately returns to normal. According to best practice, what should the technician do NEXT?
- A
Implement the fix on the remaining affected ports, validate that connectivity is stable, and document the change
- B
Reboot all routers at the branch to ensure the new duplex settings propagate through the network
- C
Replace all patch cables connected to the switch because duplex mismatches usually indicate cabling faults
- D
Escalate the issue to the ISP because end-user connectivity was impacted
Show answer and explanation
Correct answer: A
Explanation
This question tests the Network+ troubleshooting step focused on implementing the solution or escalating as necessary. In CompTIA's troubleshooting methodology, after identifying the problem, establishing a theory, testing the theory, and creating a plan of action, the technician should implement the fix, verify full system functionality, and document the entire process. In this scenario, the technician has already confirmed the root cause and proven that the fix works on affected switch ports. The proper next action is to apply the fix where needed, confirm stable network performance, and document the remediation. This approach follows common enterprise change and incident management best practices and avoids unnecessary escalation or unrelated remediation steps.
- A. Correct.
Correct. Once the root cause has been identified and a successful fix has been tested, the next step is to implement the solution across the remaining affected systems, verify normal operation, and document what was changed. This aligns with standard troubleshooting methodology used in Network+, where after establishing a plan and implementing a solution, the technician verifies full system functionality and documents findings, actions, and outcomes.
- B. Incorrect.
Incorrect. Router reboots are unnecessary for a switch-port duplex mismatch and could create additional downtime. Duplex settings are negotiated at the interface level between the switch port and the connected device; they do not need to 'propagate' through routers.
- C. Incorrect.
Incorrect. While bad cabling can cause physical-layer errors, duplex mismatches are typically caused by interface configuration inconsistencies, such as one side forced and the other side set to auto. Replacing all patch cables would not address the confirmed root cause and would waste time.
- D. Incorrect.
Incorrect. Escalation to the ISP is not appropriate because the technician has already identified an internal LAN configuration problem and verified that correcting the switch settings resolves the issue. Escalation should occur only when the issue is outside the technician's scope or authority, or when the root cause lies with an external provider.