Debugging · interview question
Which option describes the most likely pitfall around logging?
Multiple choiceMediumchapter-5-curatedpremiumdebugginglogging
Answer and explanation
Correct answer
B. Too little logging hides the story, but noisy logs bury the one field or event you actually need.
Why
Too little logging hides the story, but noisy logs bury the one field or event you actually need. Calling out that risk matters because interviewers often ask how you would debug production without a debugger attached, and logs are the first answer.
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?