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 7 of 9
Separates an unmodifiable API surface from a stable snapshot and from deep immutability of contained objects.
Separates propagation of entity operations from deletion of dependent children removed from an owning relationship.
Separates the persistence specification, its ORM implementation, and Spring's repository abstraction while keeping generated SQL visible.
Distinguishes one-to-one transformation from transformation plus flattening for nested collections, streams, and optionals.
Separates full Spring MVC dispatch over mock Servlet objects from tests that cross an actual network and container boundary.
Separates logging a user into an application, obtaining tokens for outbound calls, and validating access tokens on an API.
Separates Spring's application framework and container from Boot's opinionated startup, dependency, configuration, and operational conventions.
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.
Walks from instantiation and dependency injection through post-processing, initialization callbacks, use, and supported destruction behavior.
Explains how Java compiles generic code and connects erasure to runtime checks, reflection limits, overloads, arrays, and bridge methods.
Explains heap, per-thread stacks, Metaspace, code cache, and native memory through the failures and evidence they produce.
Combines Spring Boot signals into an operator-focused baseline for service health, dependencies, capacity, releases, and actionable alerts.
Treats @Async as an in-process executor boundary with proxy, failure, context, capacity, and durability consequences.
Chooses streams or loops by transformation shape, control flow, side effects, debuggability, and measured performance.
Explains default rollback behavior, checked exceptions, rollback rules, swallowed failures, and commit-time exceptions.
Uses sealed types for deliberately closed variants and connects them to exhaustive reasoning, evolution, and open extension boundaries.
Chooses between blocking Servlet execution and end-to-end non-blocking reactive execution based on dependencies, concurrency, and team cost.
Uses direct bodies for fixed successful contracts and ResponseEntity when status or headers vary by outcome.
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.
Uses bounds to express capabilities required by generic code and distinguishes them from wildcard flexibility at call sites.
Chooses stereotype scanning for owned application components and explicit factory methods for third-party types, construction policy, and visible composition.
Uses typed grouped binding and validation for application configuration while reserving @Value for small isolated expressions.