N10-009 Question 298
Single answerDocument findings, actions, outcomes, and lessons learned throughout the processA network administrator resolves an intermittent VoIP quality issue affecting one branch office by identifying a duplex mismatch on an access switch port connected to the branch router. After correcting the port settings, the administrator verifies that packet loss and jitter return to normal levels. The issue was caused by a previous emergency replacement that was never fully documented. Which action should the administrator take NEXT to best support future troubleshooting and continual improvement?
- A
Update the incident record with the root cause, changes made, validation results, and a brief lessons-learned summary
- B
Close the ticket immediately because service has been restored and the technical issue is resolved
- C
Reboot the router during the next maintenance window to confirm the duplex mismatch does not return
- D
Email the help desk that the problem is fixed and let them document any details they think are relevant
Show answer and explanation
Correct answer: A
Explanation
This question tests the final phase of structured troubleshooting: documenting findings, actions, outcomes, and lessons learned after confirming the fix. In real environments, good documentation should capture the symptoms reported, the root cause identified, the exact remediation steps taken, and the validation evidence showing service was restored. It should also note process improvements, such as the need to document emergency replacements more thoroughly. This aligns with common IT operational best practices for incident management, change tracking, and knowledge-base maintenance. Proper documentation improves auditability, speeds future diagnosis, reduces repeat incidents, and supports continuous improvement.
- A. Correct.
Correct. After resolving and validating the issue, the best next step is to document the findings, actions taken, outcomes, and lessons learned in the incident or change record. This creates an accurate history for future troubleshooting, supports knowledge transfer, and helps prevent recurrence. Including the root cause, exact configuration changes, and post-change verification results reflects standard operational best practices.
- B. Incorrect.
Incorrect. Restoring service is important, but closing the ticket without documenting the cause and resolution leaves the organization vulnerable to repeated outages and slower future troubleshooting. This option reflects a common mistake: treating restoration as the final step instead of completing the full troubleshooting lifecycle.
- C. Incorrect.
Incorrect. A reboot is not the most appropriate next step because the root cause has already been identified and corrected, and the fix has been validated through normal performance metrics. Rebooting introduces unnecessary risk and does not address the documentation gap that contributed to the problem in the first place.
- D. Incorrect.
Incorrect. Informal communication to the help desk is not a substitute for updating the official incident or change documentation. While notifying stakeholders may be useful, relying on someone else to record technical details can result in incomplete or inaccurate records. The technician who performed the troubleshooting should document the evidence, actions, and outcomes directly.