What standard and code elements power FastAPI's auto-generated API docs?

WHAT THIS TESTS: This question probes whether you understand the mechanics behind FastAPI's automatic documentation generation, specifically the relationship between the OpenAPI specification and the metadata FastAPI extracts from your source code. Senior candidates should distinguish between the specification standard, the generated schema file, and the interactive user interfaces that render it.

A GOOD ANSWER COVERS: First, state that the documentation is based on the OpenAPI standard. FastAPI generates an OpenAPI schema from your application, which is what powers both the interactive docs and alternative docs views. Second, explain that the primary source of schema data is Python type hints in your path operation function signatures. FastAPI reads parameter types to infer query params, path params, and request bodies, and it reads the return type annotation to build the response model. Third, mention Pydantic models. When you use Pydantic classes as type hints, FastAPI translates field names, types, defaults, and validation constraints directly into OpenAPI schema components. Fourth, note that path operation decorators like app.get or app.post supply the route paths, HTTP methods, and can override response status codes or tags. Fifth, include docstrings. FastAPI can use the path operation function's docstring as the description field for that endpoint in the generated docs.

COMMON WRONG ANSWERS: A major red flag is claiming you need to manually write or maintain a separate openapi.yaml or JSON schema file. FastAPI builds the schema dynamically from your code. Another weak answer omits Pydantic models as a distinct source of schema information, since they are the primary mechanism that defines reusable request and response schemas. Failing to name OpenAPI as the underlying specification and only referring to generic auto-docs shows shallow knowledge.

LIKELY FOLLOW-UPS: How would you customize the generated schema, such as adding examples or overriding a response model? How do you hide an endpoint from the docs? What is the difference between the interactive and alternative documentation UIs? How does FastAPI handle complex nested models in the OpenAPI output?

ONE CONCRETE EXAMPLE: If you define an endpoint with async def create_item(item: Item) -> Item where Item is a Pydantic model with name: str and price: float fields, FastAPI will generate an OpenAPI operation with a request body schema containing name and price, and a matching response schema, all without writing any YAML or JSON schema by hand.