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 20 of 52
Controls operation identities, request and response schemas, error documentation, and compatibility checks without hand-maintaining a second contract.
Combines JDBC batching, compatible identifiers, periodic flush and clear, bounded transactions, and explicit bulk-operation semantics.
Keeps domain outcomes transport-neutral and maps not-found, conflict, invalid transition, and dependency failure at the web boundary.
Propagates trace and observation context through supported clients and executor boundaries without passing framework state manually.
Uses latest-request semantics, cancellation, identity checks, and explicit state transitions for changing inputs.
Frames collector and heap decisions around service goals, workload evidence, pause distributions, live set, and deployment limits.
Uses supported properties, replacement beans, and narrow exclusions in that order, with condition-report and upgrade verification.
Chooses Resource, StreamingResponseBody, emitters, or SSE while controlling memory, timeout, disconnect, headers, and late failure.
Streams bounded chunks with explicit resource lifetime, cancellation, late-failure, and proxy behavior.
Uses HttpTestingController to verify request semantics and return controlled responses without calling a real server.
Uses a real route configuration and RouterTestingHarness to verify URLs, rendered components, redirects, guards, and failures.
Tests serialization, headers, status mapping, timeouts, and retries against a controllable HTTP boundary instead of mocking fluent internals.
Exercises signal-based component contracts through Angular bindings and waits for scheduled rendering before asserting.
Tests anonymous, authenticated, forbidden, CSRF, JWT, method, ownership, and full credential flows without confusing mocked identity with authentication.
Explains why ordinary injection resolves once and chooses providers, factories, scoped proxies, or explicit parameters for shorter-lived dependencies.
Uses multiple thread dumps, CPU correlation, lock ownership, executor context, and request evidence to distinguish deadlock, contention, blocking, and hot loops.
Uses parametrization for one behavior across meaningful cases while keeping failures and intent easy to read.
Runs stable shared production-like dependencies with Spring service connections, real migrations, deterministic data, and bounded startup cost.
Handles multipart uploads with bounded size, untrusted metadata, content inspection, controlled storage, scanning, and cleanup.
Combines multipart limits, metadata validation, content inspection, safe storage, and asynchronous malware processing.
Uses cascaded validation for nested DTOs, class-level constraints for local invariants, and domain services for state-dependent rules.
Keeps FastAPI dependency resolution at transport and composition boundaries while application services use explicit dependencies.
Separates interruptible background rendering from time-based event or request suppression.
Uses versioned migrations and staged compatibility instead of letting Hibernate mutate a production schema automatically.