FastAPI · interview question
A bug appears around validation. What is the strongest first debugging move?
Multiple choiceMediumchapter-13-curatedpremiumfastapivalidation
class CreateOrderRequest(BaseModel):
sku: str
quantity: int
@field_validator("quantity")
@classmethod
def quantity_must_be_positive(cls, value: int) -> int:
if value <= 0:
raise ValueError("quantity must be positive")
return valueAnswer and explanation
Correct answer
D. 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. Allowing invalid data deeper into the service layer makes later failures harder to interpret.
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?