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 5 of 37
Builds stable Micrometer dimensions that answer operational questions without unbounded time series and cost.
Configures finite origins, methods, headers, credentials, and preflight behavior while separating browser enforcement from authorization.
Designs executor ownership, pool size, queue capacity, rejection, shutdown, task context, and observability around workload behavior.
Traces the injection point, candidate type, registration path, conditions, profiles, generics, qualifiers, and package boundaries.
Finds repeated association queries with SQL evidence and chooses a bounded fetch or projection without creating a cartesian result.
Classifies mapping, conversion, binding, validation, multipart, CORS, filter, and negotiation failures before changing controller code.
Locates pre-handler failures across proxies, routing, parsing, validation, dependencies, and middleware using structured evidence.
Distinguishes missing-class and incompatible-class failures, then traces them to the actual packaged runtime dependency graph.
Prefers compatible evolution, uses Spring version resolution when a breaking contract requires it, and operates deprecation deliberately.
Maps a bounded public list contract to Spring arguments without exposing persistence property names or unstable ordering.
Treats a bean cycle as a design signal, explains constructor failure, and uses delayed resolution only for genuine lifecycle boundaries.
Maps known framework and application failures to RFC 9457 responses while preserving stable codes, safe detail, and correlation.
Explains a practical approach to diagnosing failed builds, tests, package restore, environment issues, or flaky checks.
Controls operation identities, request and response schemas, error documentation, and compatibility checks without hand-maintaining a second contract.
Combines JDBC batching, compatible identifiers, periodic flush and clear, bounded transactions, and explicit bulk-operation semantics.
Keeps domain outcomes transport-neutral and maps not-found, conflict, invalid transition, and dependency failure at the web boundary.
Propagates trace and observation context through supported clients and executor boundaries without passing framework state manually.
Uses latest-request semantics, cancellation, identity checks, and explicit state transitions for changing inputs.
Frames collector and heap decisions around service goals, workload evidence, pause distributions, live set, and deployment limits.
Uses supported properties, replacement beans, and narrow exclusions in that order, with condition-report and upgrade verification.
Chooses Resource, StreamingResponseBody, emitters, or SSE while controlling memory, timeout, disconnect, headers, and late failure.
Streams bounded chunks with explicit resource lifetime, cancellation, late-failure, and proxy behavior.
Uses HttpTestingController to verify request semantics and return controlled responses without calling a real server.
Uses a real route configuration and RouterTestingHarness to verify URLs, rendered components, redirects, guards, and failures.