FastAPI · interview question
Which move is the best default when api errors becomes part of this workflow?
Multiple choiceHardchapter-13-curatedpremiumfastapiapi-errors
Answer and explanation
Correct answer
D. Return status codes and messages that are truthful for the caller while preserving deeper detail in logs.
Why
Return status codes and messages that are truthful for the caller while preserving deeper detail in logs. That is the stronger engineering move because good interview answers distinguish caller-facing errors from operator-facing diagnostics. Dumping raw exceptions at the client boundary makes the API feel accidental and insecure.
Test yourself on FastAPI
A free test with instant, explained results. No account needed.
More FastAPI questions
- A teammate submits shaky pydantic models code. Which review comment is the strongest?
- What do interviewers usually hear as a strong signal when you discuss api errors well?
- Which boundary choice best fits api errors in a maintainable Python system?
- What do interviewers usually hear as a strong signal when you discuss pydantic models well?
- Which option treats route handlers as an engineering policy decision instead of a syntax trick?
- What assumption should be made explicit when working with route handlers?