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.
1345 results
Page 25 of 57
Uses versioned migrations and staged compatibility instead of letting Hibernate mutate a production schema automatically.
Uses plans as bounded, revisable execution aids while preserving evidence, policy, and application-owned state transitions.
Handles token-budget overflow and incomplete generation through explicit prioritization, rejection, retrieval, summarization, continuation, and validation.
Separates provider refusals, safety blocks, token truncation, transport failure, and valid domain abstention.
Separates model and provider outcomes, applies bounded recovery, validates outputs, and exposes useful status and telemetry.
Treats prompts as observable behavior, removes secrets and authorization policy from them, and limits the consequence of disclosure.
Returns correlated, minimal, typed, and safely bounded tool results without confusing them with trusted instructions.
Explains transient database errors, retry strategy, EF Core execution strategy, idempotency, timeouts, and avoiding retry storms.
Uses documented thread-safe scheduling APIs and keeps event-loop objects confined.
Uses a password-specific algorithm, measurable work settings, and gradual rehashing without blocking service capacity.
Reuses bounded redis-py pools for the application lifetime and closes async resources deliberately.
Coordinates readiness, signals, request drain, lifespan cleanup, and a bounded termination deadline.
Uses Resource Server and JwtDecoder to validate signature, issuer, audience, time, algorithms, key rotation, and authority mapping.
Separates stale checkout protection, connection aging, pool waits, statement timeouts, and uncertain transactions.
Treats cancellation as cooperative control flow with reliable resource cleanup and propagation.
Propagates request cancellation through async dependencies while keeping committed side effects and timeout policy explicit.
Makes duplicate-key behavior explicit through validation, merge policies, grouping, and deterministic map selection.
Covers App Service app settings, environment-specific configuration, restarts, slot settings, and avoiding hard-coded production values.
Explains DbContext lifetime and unit-of-work boundaries with practical .NET data-access examples and production trade-offs.
Chooses stable entity equality across transient, managed, detached, and proxied instances without breaking hash collections.
Uses FastAPI lifespan to create and close process-owned resources around request serving.
Treats interruption as a cooperative request, preserves interrupt status, defines cleanup, and separates cancellation signals from guaranteed task termination.
Separates restart-worthy process failure from traffic readiness and composes Spring Boot health groups around those meanings.
Uses Optional to model absence at return boundaries and avoids eager defaults, null Optionals, unsafe get calls, and awkward field or parameter usage.