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.
878 drills fit a 10-minute session. Closest fits first.
Page 10 of 37
Explains scale-out bugs from in-memory sessions, local caches, background queues, uploaded files, and per-instance behavior.
Defines the serializable prop boundary, component composition pattern, and protections against leaking server-only data.
Handles eager subscription, initial values, injection context, errors, cleanup, and repeated conversions.
Fixes lazy access outside the persistence context with explicit fetch and DTO mapping while explaining the tradeoff of Open Session in View.
Explains the operating, security, governance, and integration capabilities that surround managed model inference without treating a platform as the application.
Uses the JPA slice for mappings and repositories while recognizing embedded-database substitutions and transaction-owned blind spots.
Separates bearer-token extraction and OpenAPI description from token validation, user lookup, and authorization.
Explains visibility and ordering through synchronization actions instead of misleading main-memory and thread-cache folklore.
Treats isolation as concurrency behavior and read-only and timeout as resource hints whose enforcement depends on the transaction stack.
Designs scheduled work for overlap, multiple replicas, restart, failure, and durable ownership instead of assuming one execution.
Explains making a fully constructed object visible through valid happens-before edges and final-field semantics.
Explains awaitable work, scheduled ownership, and eventual-result integration in asyncio.
Compares explicit DRF serializers with model-derived serializer convenience and coupling.
Separates what a model can perform from whether the complete AI feature behaves dependably under real inputs, failures, and constraints.
Separates logging a user into an application, obtaining tokens for outbound calls, and validating access tokens on an API.
Separates transaction-phase callbacks inside one process from durable database-backed publication across process failure.
Separates Jakarta cascaded validation, Spring validation groups, and modern MVC method validation without relying on outdated controller advice.
Distinguishes the synchronous WSGI request contract from ASGI's asynchronous, multi-event application contract.
Distinguishes model-directed execution from explicit application control and explains when each is appropriate.
Designs index records that support filtering, authorization, freshness, citations, diagnosis, and safe reprocessing.
Combines Spring Boot signals into an operator-focused baseline for service health, dependencies, capacity, releases, and actionable alerts.
Defines MCP as a client-host-server protocol for discovering and using tools, resources, and prompts without confusing interoperability with safety.
Places provider guardrails as one configurable defense while preserving application authorization, validation, testing, and incident evidence.
Treats model, prompt, schema, tools, routing, retrieval, policy, and evaluators as one observable behavior release.