Exceptions · interview question
Which move is the best default when error translation becomes part of this workflow?
Multiple choiceHardchapter-5-curatedpremiumexceptionserror-translation
Answer and explanation
Correct answer
B. Convert low-level failures into boundary-appropriate messages where callers genuinely need a different contract.
Why
Convert low-level failures into boundary-appropriate messages where callers genuinely need a different contract. That is the stronger engineering move because interviewers like hearing where the translation boundary belongs and why. Translating too early disconnects the caller from the technical clue, while translating too late leaks infrastructure details upward.
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?