Bitzu

100-150 CCST ยท Troubleshooting and device commands

Troubleshooting methodology

Structured steps from identifying the problem and gathering information to testing a theory, fixing, verifying and documenting, and top-down, bottom-up and divide-and-conquer approaches.

Key points

  • Work in a structured order: identify the problem (gather information, question the user), establish a theory of probable cause, test the theory, plan and implement a fix, verify full functionality, then document.
  • Approaches: top-down (application layer first), bottom-up (physical layer first), divide-and-conquer (start in the middle layer and move up or down).

Practice questions

Single choice

Which step normally comes first in a structured troubleshooting process?

  1. Replace the suspected faulty hardware
  2. Identify the problem and gather information
  3. Document the final solution
  4. Verify full system functionality
Show answer

Answer: B. Identify the problem and gather information

You must understand and identify the problem before you can form a theory. Replacing hardware or documenting come later.

Select all that apply

Which are recognised troubleshooting approaches?

  1. Top-down
  2. Reboot every device first
  3. Bottom-up
  4. Divide-and-conquer
  5. Swap parts at random
Show answer

Answer: A. Top-down, C. Bottom-up, D. Divide-and-conquer

Top-down, bottom-up and divide-and-conquer are layer-based strategies. Rebooting everything or swapping parts at random is guessing, not a method.

True or false

Once a fix is applied, the problem can be considered solved without further checks.

Show answer

Answer: False

False. You must verify full functionality (ideally with the user) and then document the solution; a fix can solve one symptom and break something else.

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.

Download on the App StoreGet it on Google Play

More 100-150 CCST topics in this module