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.
132 results across 1 active filter
Page 2 of 6
Explains one observation lifecycle feeding metrics, tracing, and context through registered handlers.
Explains first-match chain selection, rule matching inside a chain, ordering, fallback coverage, and accidental unprotected paths.
Compares joining an existing transaction, suspending it for an independent transaction, and using a savepoint-backed nested scope.
Treats GrantedAuthority as the common representation while explaining role prefixes, scope mapping, and domain permission design.
Explains proxy interception, target delegation, JDK versus class proxies, method limits, and the self-invocation boundary.
Explains cache interception, keys, conditions, eviction, proxy self-invocation, and the provider boundary.
Maps each part of the HTTP request to explicit controller arguments and distinguishes conversion, model binding, and body conversion.
Selects the smallest Spring test scope that can prove the risky boundary without mocking away framework or infrastructure behavior.
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.
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.
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.
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.