Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
24 results across 1 active filter
Page 1 of 1
Builds a FastAPI POST boundary with separate input/output models, forbidden extra fields, domain mapping, and a 201 response.
Explains acquisition and cleanup around `yield`, including request and function scopes, streaming, and exception-safe ownership.
Traces a request from the ASGI server through middleware, routing, dependencies, validation, handler execution, and response completion.
Explains FastAPI parameter-source inference and when explicit markers make an HTTP contract clearer.
Explains dependency graphs, sub-dependencies, request-local caching, failures, and deliberate cache bypass.
Explains how input conversion, strict validation, and extra-field policies change what an API accepts and preserves.
Locates pre-handler failures across proxies, routing, parsing, validation, dependencies, and middleware using structured evidence.
Models partial updates without confusing omitted fields, explicit nulls, defaults, or unauthorized changes.
Controls operation identities, request and response schemas, error documentation, and compatibility checks without hand-maintaining a second contract.
Streams bounded chunks with explicit resource lifetime, cancellation, late-failure, and proxy behavior.
Handles multipart uploads with bounded size, untrusted metadata, content inspection, controlled storage, scanning, and cleanup.
Keeps FastAPI dependency resolution at transport and composition boundaries while application services use explicit dependencies.
Uses Pydantic models as explicit transport contracts without making them persistence or domain models automatically.
Maps validation, HTTP, domain, and unexpected failures into a stable client contract while preserving diagnostics.
Uses routers as feature-oriented HTTP modules while keeping application logic, composition, and contract ownership clear.
Uses lifespan to acquire and release process-level resources while making readiness, workers, failures, and tests explicit.
Separates deterministic request-shape validation from authorization, I/O, workflows, and durable business invariants.
Explains runtime output validation, filtering, serialization, and the security value of an explicit response contract.
Defines FastAPI as an ASGI web framework and explains how types drive validation, dependency resolution, responses, and OpenAPI.
Uses an explicit discriminator to model genuine request variants with predictable validation and OpenAPI output.
Distinguishes small in-process post-response work from durable, retryable, independently operated jobs.
Chooses between FastAPI-managed response processing and direct control over the HTTP response.
Chooses between synchronous and asynchronous FastAPI handlers based on the libraries and work they execute.
Explains nested ASGI middleware ordering, reverse response flow, exception boundaries, CORS, and streaming-safe design.