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 3 of 6
Tests serialization, headers, status mapping, timeouts, and retries against a controllable HTTP boundary instead of mocking fluent internals.
Tests anonymous, authenticated, forbidden, CSRF, JWT, method, ownership, and full credential flows without confusing mocked identity with authentication.
Constructs a service directly with explicit collaborators and verifies behavior without Spring startup or framework-owned concerns.
Explains why ordinary injection resolves once and chooses providers, factories, scoped proxies, or explicit parameters for shorter-lived dependencies.
Runs stable shared production-like dependencies with Spring service connections, real migrations, deterministic data, and bounded startup cost.
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.
Binds related values to typed configuration properties, applies validation constraints, and fails with actionable non-secret diagnostics.
Uses versioned migrations and staged compatibility instead of letting Hibernate mutate a production schema automatically.
Uses Resource Server and JwtDecoder to validate signature, issuer, audience, time, algorithms, key rotation, and authority mapping.
Chooses stable entity equality across transient, managed, detached, and proxied instances without breaking hash collections.
Separates restart-worthy process failure from traffic readiness and composes Spring Boot health groups around those meanings.
Places the application class above owned components, uses capability-oriented packages, and keeps scanning and imports deliberate.
Stores salted adaptive password hashes, supports algorithm migration, and separates password verification from encryption.
Builds outbound resilience from deadlines and operation safety, then adds bounded retry, circuit, and concurrency controls with telemetry.
Creates queryable structured events with trace correlation, stable fields, useful context, and deliberate redaction.
Moves from user-visible latency to route, dependency, database, executor, JVM, and change evidence before selecting a fix.
Preserves the root cause, separates binding, bean, port, classpath, migration, and external failures, and uses Boot's diagnostic reports.
Uses Hikari metrics, thread evidence, database activity, transaction scope, and query behavior to separate leaks from slow or excessive work.
Separates server request capacity from application executor capacity and finds blocking, queueing, rejection, or downstream causes.
Keeps cached reads acceptably fresh and prevents hot-key reloads from overwhelming the database across application instances.
Places an idempotency key at the Spring boundary while persisting request identity and terminal outcome atomically with business work.
Coordinates startup work, readiness, schema compatibility, warmup, and mixed-version traffic during a rolling release.
Binds typed configuration, understands property precedence, validates startup invariants, and keeps secrets outside source control.