Exceptions · interview question
A bug appears around raising exceptions. What is the strongest first debugging move?
Multiple choiceEasychapter-5-curatedpremiumexceptionsraising-exceptions
def ensure_positive(quantity: int) -> None:
if quantity <= 0:
raise ValueError("quantity must be positive")Answer and explanation
Correct answer
C. Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.
Why
That approach is reliable because it creates evidence. Delaying a broken invariant usually spreads bad data and hides the original mistake.
Test yourself on Exceptions
A free test with instant, explained results. No account needed.
More Exceptions questions
- A teammate submits shaky custom exceptions code. Which review comment is the strongest?
- Which explanation would sound strongest in an interview when discussing raising exceptions?
- You cannot rewrite everything today. What is the best incremental improvement around custom exceptions?
- Which judgment is strongest when choosing a data shape for custom exceptions?
- Which option treats error translation as an engineering policy decision instead of a syntax trick?
- What does a strong engineer do when reasoning through custom exceptions code?