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.
878 drills fit a 10-minute session. Closest fits first.
Page 30 of 37
Distinguishes sources that can produce iteration from stateful one-pass iterators and explains exhaustion and repeatability.
Contrasts opting out of static checking with safely accepting an unknown value that must be narrowed before use.
Compares copying strategies through nested state, ownership, performance, and domain identity rather than presenting deep copy as universally safer.
Contrasts blocking result retrieval with composable completion stages, explicit executors, failure handling, and limited cancellation guarantees.
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.
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.
Walks from instantiation and dependency injection through post-processing, initialization callbacks, use, and supported destruction behavior.
Explains N+1 queries in EF Core with practical .NET data-access examples and production trade-offs.
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.
Explains how GC roots retain reachable object graphs and turns heap evidence into a concrete ownership fix for static state, events, closures, queues, and caches.
Connects stable hashing and equality to dictionary and set correctness, including custom types and mutable-key failures.
Explains why memory diagnostics need access control, retention limits, and careful handling of secrets and user data.
Covers build-once deployment, tests, artifact traceability, slot deployment, smoke checks, approvals, and post-release monitoring.
Tests rendered behavior, user interaction, outputs, and visible failure states without coupling to private implementation details.
Uses harnesses for reusable or complex widgets where a stable user-oriented test API is more valuable than direct DOM coupling.
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.
Uses runtime tokens for configuration and abstractions while distinguishing provider recipes and instance identity.
Uses direct bodies for fixed successful contracts and ResponseEntity when status or headers vary by outcome.