Exceptions · interview question

What is the healthiest performance judgment around raising exceptions?

Multiple choiceMediumchapter-5-curatedpremiumexceptionsraising-exceptions

python

def ensure_positive(quantity: int) -> None:
    if quantity <= 0:
        raise ValueError("quantity must be positive")

Keep raising exceptions implicit so the script stays short and hope the next engineer infers the rule.Delay clarity until production traffic reveals the edge case and then patch it under pressure.Measure before optimizing, then change the part that actually dominates cost instead of guessing from style alone.Solve the symptom with comments only and avoid changing the code shape around raising exceptions.

Answer and explanation

Correct answer

C. Measure before optimizing, then change the part that actually dominates cost instead of guessing from style alone.

Why

Premature optimization is usually weaker than targeted optimization backed by measurement.

Test yourself on Exceptions

A free test with instant, explained results. No account needed.

Start free test

All Exceptions questions →

What is the healthiest performance judgment around raising exceptions?

Correct answer

Why

More Exceptions questions