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.
391 results across 1 active filter
Page 14 of 17
Distinguishes fewer network round trips from atomic execution and chooses the smallest correct Redis primitive.
Separates Jakarta cascaded validation, Spring validation groups, and modern MVC method validation without relying on outdated controller advice.
Distinguishes the synchronous WSGI request contract from ASGI's asynchronous, multi-event application contract.
Walks from instantiation and dependency injection through post-processing, initialization callbacks, use, and supported destruction behavior.
Explains heap, per-thread stacks, Metaspace, code cache, and native memory through the failures and evidence they produce.
Focuses unit tests on stable behavior, meaningful boundaries, deterministic outcomes, and useful failure messages.
Explains Aspire as a code-first application model and developer experience without confusing it with a production runtime or architecture style.
Combines Spring Boot signals into an operator-focused baseline for service health, dependencies, capacity, releases, and actionable alerts.
Defines omission, nullability, field ownership, invariants, concurrency, and effects for DRF partial updates.
Turns Django's production settings, server, storage, security, and operational dependencies into a repeatable release check.
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 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.
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.