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.
208 results across 1 active filter
Page 3 of 9
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.
Uses generated repository behavior for simple cases and explicit query or implementation boundaries when the use case becomes complex.
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.
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.
Separates authentication challenge from denied authorization and traces the selected entry point, denied handler, and matched rule.
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.
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.
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.
Tests serialization, headers, status mapping, timeouts, and retries against a controllable HTTP boundary instead of mocking fluent internals.
Tests anonymous, authenticated, forbidden, CSRF, JWT, method, ownership, and full credential flows without confusing mocked identity with authentication.
Constructs a service directly with explicit collaborators and verifies behavior without Spring startup or framework-owned concerns.
Explains why ordinary injection resolves once and chooses providers, factories, scoped proxies, or explicit parameters for shorter-lived dependencies.
Uses multiple thread dumps, CPU correlation, lock ownership, executor context, and request evidence to distinguish deadlock, contention, blocking, and hot loops.