Validation error responses in FastAPI - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the default HTTP status code for validation errors in FastAPI?

When FastAPI detects a validation error in the request data, what HTTP status code does it return by default?

A 422 Unprocessable Entity

B 200 OK

C 400 Bad Request

D 500 Internal Server Error

💡 Hint

Think about the status code that means the server understands the request but the data is invalid.

FastAPI uses status code 422 Unprocessable Entity by default for validation errors. This means the server understood the request but the data did not pass validation.

📝 Syntax

intermediate

Which code snippet correctly customizes the validation error response in FastAPI?

You want to customize the response when validation fails in FastAPI. Which code snippet correctly overrides the default validation error handler?

FastAPI

from fastapi import FastAPI, Request
from fastapi.responses import JSONResponse
from fastapi.exceptions import RequestValidationError

app = FastAPI()

@app.exception_handler(RequestValidationError)
async def validation_exception_handler(request: Request, exc: RequestValidationError):
    return JSONResponse(
        status_code=400,
        content={"detail": exc.errors(), "body": exc.body},
    )

A Override FastAPI's default exception handler by subclassing FastAPI and redefining validation_error method

B Use @app.middleware('http') to catch validation errors and return JSONResponse

C Use @app.get('/error') endpoint to manually check validation and return custom response

D Use @app.exception_handler(RequestValidationError) with async function returning JSONResponse with status_code 400

💡 Hint

Look for the decorator that handles exceptions of type RequestValidationError.

FastAPI allows customizing validation error responses by defining an exception handler for RequestValidationError using @app.exception_handler.

🔧 Debug

advanced

Why does this FastAPI validation error handler not work as expected?

Consider this code snippet that tries to customize validation error responses. Why does it fail to catch validation errors?

FastAPI

from fastapi import FastAPI
from fastapi.exceptions import RequestValidationError
from fastapi.responses import JSONResponse

app = FastAPI()

@app.exception_handler(Exception)
async def generic_exception_handler(request, exc):
    if isinstance(exc, RequestValidationError):
        return JSONResponse(status_code=400, content={"error": "Validation failed"})
    return JSONResponse(status_code=500, content={"error": "Server error"})

A Because @app.exception_handler(Exception) does not catch RequestValidationError exceptions

B Because FastAPI processes RequestValidationError before generic Exception handlers, so this handler is never called for validation errors

C Because the handler function is missing the Request type annotation for the request parameter

D Because JSONResponse cannot be returned from exception handlers

💡 Hint

Think about the order FastAPI uses to handle exceptions and specific vs generic handlers.

FastAPI uses the most specific exception handler first. Since there is no handler for RequestValidationError, it uses the default one before the generic Exception handler. So this generic handler never catches validation errors.

❓ state_output

advanced

What is the content of the validation error response body?

When a validation error occurs in FastAPI, what keys are included in the JSON response body by default?

A {"message": "Invalid input", "status": 400}

B {"error": "Validation failed", "code": 422}

C {"detail": [{"loc": [...], "msg": "...", "type": "..."}]}

D {"errors": ["field required", "value is not valid"]}

💡 Hint

Look for the key that contains a list of error details with location and message.

The default validation error response includes a key "detail" which is a list of error objects. Each error object has keys like "loc" (location), "msg" (message), and "type" (error type).

🧠 Conceptual

expert

How can you globally change the validation error status code in FastAPI without overriding the handler?

You want all validation errors in your FastAPI app to return status code 400 instead of the default 422, but you do not want to write a custom exception handler. Which approach achieves this?

A Use a middleware to intercept responses and change status code 422 to 400

B Use the openapi_schema parameter to modify the validation error status code globally

C Override the default RequestValidationError handler by subclassing FastAPI and setting a custom validation error status code property

D Set the status_code attribute on the Pydantic model to 400

💡 Hint

Think about intercepting responses after they are generated without changing exception handlers.

FastAPI does not provide a built-in way to change the validation error status code globally without a custom handler. Using middleware to catch responses with status 422 and change them to 400 is a practical approach without overriding handlers.