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 5 of 6
Explains the persistence context as an identity map and unit of work that tracks managed entities through EntityManager.
Separates proving an identity from deciding whether that identity may perform a specific action on a resource.
Separates view-oriented controller return handling from class-level response-body semantics without implying different request mapping.
Separates mandatory persistence-context identity from optional shared entity caching and its consistency tradeoffs.
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.
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.
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.
Explains default rollback behavior, checked exceptions, rollback rules, swallowed failures, and commit-time exceptions.
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.
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.
Prefers constructor injection for required dependencies while explaining the limited roles and costs of setter and field injection.
Chooses a query representation from static versus dynamic shape, portability, database features, readability, and performance evidence.
Chooses version-based conflict detection or database locks from contention, transaction duration, and invariant needs.