Question
Which practice avoids a common mistake with Logging?
- Ignore the Logging issue and rely on team discipline instead of clearer APIs or invariants.
- Do not log sensitive values or flood the output with noise that hides the one field or state transition you actually need.
- Silence the Logging problem by using broad catches, hidden globals, or extra shared mutable state.
- Prefer the version of Logging that makes behavior less predictable as long as the code still runs.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: B. Do not log sensitive values or flood the output with noise that hides the one field or state transition you actually need.
Do not log sensitive values or flood the output with noise that hides the one field or state transition you actually need. This is a common failure mode in real Python code and a frequent interview follow-up.
Track: Python