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.
1225 drills fit a 20-minute session. Closest fits first.
Page 25 of 52
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.
Treats @Async as an in-process executor boundary with proxy, failure, context, capacity, and durability consequences.
Uses an explicit discriminator to model genuine request variants with predictable validation and OpenAPI output.
Chooses between small in-process follow-up work and durable, independently operated background execution.
Explains lazy query construction, evaluation triggers, result caching, and repeated-query surprises.
Uses generics to preserve relationships among types and introduces bounds, constraints, and variance only where they clarify a real API.
Uses derived types for genuine relationships while preserving explicit boundaries for domain and transport models.
Chooses between blocking Servlet execution and end-to-end non-blocking reactive execution based on dependencies, concurrency, and team cost.
Chooses among explicit joins, reusable fetch graphs, and bounded secondary selects based on query shape and cardinality.
Places protocol-wide work in filters, handler-aware MVC work in interceptors, and controller exception or body concerns in advice.
Chooses a query representation from static versus dynamic shape, portability, database features, readability, and performance evidence.
Chooses version-based conflict detection or database locks from contention, transaction duration, and invariant needs.
Uses HTTP rules for route-level policy and method security for reusable service operations without creating contradictory enforcement.
Chooses synchronous, reactive, or declarative clients based on the application's execution model while keeping shared timeout and error policy explicit.