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.
171 results across 1 active filter
Page 7 of 8
Chooses between synchronous and asynchronous FastAPI handlers based on the libraries and work they execute.
Uses fixture factories and test-data builders to keep setup flexible, readable, and owned by each test.
Aligns selected database data with an API read model and avoids unnecessary ORM state.
Uses task-aware context for tracing while keeping business inputs explicit and correctly reset.
Uses cryptographically secure token generation and timing-resistant comparison at credential boundaries.
Uses Django signals selectively and makes transaction timing and side effects explicit.
Distinguishes object identity from value equality and prevents fragile code based on interning or implementation accidents.
Distinguishes unavailable conditions, known defects, and unstable tests while keeping lost coverage visible.
Compares eager collections with lazy one-pass generation through memory, timing, reuse, readability, and resource ownership.
Chooses Django view style by clarity, reuse, and lifecycle needs rather than hierarchy preference.
Chooses structural or nominal contracts based on ownership, runtime identity, shared behavior, and third-party integration.
Chooses task synchronization by protected state, notification predicates, and limited capacity.
Compares structured task ownership with ordered result aggregation and different failure behavior.
Compares convenient context-propagating thread offload with explicit executor selection and ownership.
Chooses Django relationship loading from relationship shape, result cardinality, and measured query behavior.
Chooses synchronous or asynchronous FastAPI test clients from the boundary exercised and resources involved.
Chooses a SQLAlchemy abstraction from the work's shape instead of performance slogans.
Aligns SQLAlchemy transactions with business operations and uses savepoints without inventing independent commits.
Balances model methods, QuerySets, managers, and application services by the responsibility they own.
Places exception handling at meaningful boundaries and preserves causes, tracebacks, client contracts, and retry safety.
Diagnoses shared mutable function defaults and explains safe initialization without turning the behavior into a superstition.
Explains Python name binding and patches the reference actually used by the system under test.
Explains Django's nested middleware stack, short-circuiting, exceptions, and response unwinding.
Explains nested ASGI middleware ordering, reverse response flow, exception boundaries, CORS, and streaming-safe design.