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.
300 results across 1 active filter
Page 10 of 13
Separates mandatory persistence-context identity from optional shared entity caching and its consistency tradeoffs.
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.
Distinguishes fewer network round trips from atomic execution and chooses the smallest correct Redis primitive.
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.
Connects stable hashing and equality to dictionary and set correctness, including custom types and mutable-key failures.
Defines omission, nullability, field ownership, invariants, concurrency, and effects for DRF partial updates.
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.
Chooses streams or loops by transformation shape, control flow, side effects, debuggability, and measured performance.
Explains lazy query construction, evaluation triggers, result caching, and repeated-query surprises.
Explains default rollback behavior, checked exceptions, rollback rules, swallowed failures, and commit-time exceptions.
Uses generics to preserve relationships among types and introduces bounds, constraints, and variance only where they clarify a real API.
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.