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.
1225 drills fit a 20-minute session. Closest fits first.
Page 45 of 52
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.
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.
Prefers constructor injection for required dependencies while explaining the limited roles and costs of setter and field injection.
Distinguishes deterministic cleanup from finalization and explains resource ownership in normal application code.
Uses profiles for named environment or deployment groups and focused conditions for feature or capability selection.
Chooses a focused MVC slice or full application context based on whether the risk is the web contract or complete wiring.
Chooses dataclasses for transparent data-oriented types while preserving invariants, safe defaults, and honest immutability claims.
Positions records as transparent, shallowly immutable data carriers with generated value-oriented members and clear modeling limits.
Explains asynchronous cleanup for resources whose shutdown path needs async work, such as flushing or closing remote connections.
Frames inheritance as a behavioral is-a relationship whose subtypes must remain valid substitutes, not merely a code-reuse shortcut.
Chooses between FastAPI-managed response processing and direct control over the HTTP response.
Chooses between synchronous and asynchronous FastAPI handlers based on the libraries and work they execute.