N10-009 ยท Troubleshooting methodology, cabling and interfaces
The seven-step troubleshooting process
The seven-step process, probable cause approaches (top-to-bottom, bottom-to-top, divide and conquer), documentation.
Key points
- 1) Identify the problem.
- 2) Establish a theory of probable cause (top-to-bottom, bottom-to-top or divide and conquer).
- 3) Test the theory.
- 4) Establish a plan of action and note its side effects.
- 5) Implement the solution or escalate.
- 6) Verify full system functionality and apply preventive measures.
- 7) Document findings, actions and outcomes.
Practice questions
In the troubleshooting process, what comes immediately after you establish a theory of probable cause?
- Document the findings
- Establish a plan of action
- Test the theory to confirm the cause
- Implement the solution
Show answer
Answer: C. Test the theory to confirm the cause
You must confirm the theory before planning a fix. Planning first risks fixing the wrong thing.
Which actions belong to the work after the fix is in place?
- Verify that the full system works
- Reboot every device to be safe
- Put preventive measures in place where possible
- Document findings, actions and outcomes
- Skip documentation if the fix was quick
Show answer
Answer: A. Verify that the full system works, C. Put preventive measures in place where possible, D. Document findings, actions and outcomes
After implementing, you verify full functionality, add preventive measures and document. Rebooting everything is not verification, and skipping documentation for quick fixes loses knowledge.
If testing shows your theory of probable cause was wrong, you should go ahead and implement the plan of action anyway.
Show answer
Answer: False
A refuted theory means you establish a new theory or escalate. Implementing a plan built on a wrong cause wastes time and may add new faults.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
