Debugging · interview question
Which option describes the most likely pitfall around tracebacks and root cause?
Multiple choiceMediumchapter-5-curatedpremiumdebuggingtracebacks-and-root-cause
Answer and explanation
Correct answer
C. Replacing every exception with a vague generic message erases the clue that would have shortened the investigation.
Why
Replacing every exception with a vague generic message erases the clue that would have shortened the investigation. Calling out that risk matters because good debuggers preserve evidence instead of rewriting history.
Test yourself on Debugging
A free test with instant, explained results. No account needed.
More Debugging questions
- When is logging being used in the wrong way?
- Which move is the best default when logging becomes part of this workflow?
- Which explanation would sound strongest in an interview when discussing logging?
- What assumption should be made explicit when working with logging?
- Which move is the best default when tracebacks and root cause becomes part of this workflow?
- A bug appears around tracebacks and root cause. What is the strongest first debugging move?