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.
1345 results
Page 22 of 57
Chooses a Java collection by the behavior the code needs: ordering, duplicates, membership, lookup keys, and iteration.
Chooses runtime from dependency, data locality, feature, latency, and deployment constraints instead of fashion.
Selects the smallest Spring test scope that can prove the risky boundary without mocking away framework or infrastructure behavior.
Builds stable Micrometer dimensions that answer operational questions without unbounded time series and cost.
Uses input availability, rendering completion, cleanup, and SSR safety to choose lifecycle work deliberately.
Draws a short atomic database boundary around one invariant while moving network side effects into explicit, recoverable workflow states.
Configures finite origins, methods, headers, credentials, and preflight behavior while separating browser enforcement from authorization.
Uses generated repository behavior for simple cases and explicit query or implementation boundaries when the use case becomes complex.
Uses ownership, inputs, outputs, rendering responsibility, and dependency scope to define maintainable standalone components.
Designs executor ownership, pool size, queue capacity, rejection, shutdown, task context, and observability around workload behavior.
Traces the injection point, candidate type, registration path, conditions, profiles, generics, qualifiers, and package boundaries.
Finds repeated association queries with SQL evidence and chooses a bounded fetch or projection without creating a cartesian result.
Finds synchronous I/O or CPU work that prevents the event loop from scheduling other tasks.
Classifies mapping, conversion, binding, validation, multipart, CORS, filter, and negotiation failures before changing controller code.
Locates pre-handler failures across proxies, routing, parsing, validation, dependencies, and middleware using structured evidence.
Explains EF Core query performance diagnostics with practical .NET data-access examples and production trade-offs.
Combines asyncio debug evidence, task inspection, warnings, profiling, and capacity signals.
Distinguishes missing-class and incompatible-class failures, then traces them to the actual packaged runtime dependency graph.
Profiles real interactions to separate excessive change detection, expensive component work, layout cost, and network delay before optimizing.
Models partial updates without confusing omitted fields, explicit nulls, defaults, or unauthorized changes.
Prefers compatible evolution, uses Spring version resolution when a breaking contract requires it, and operates deprecation deliberately.
Maps a bounded public list contract to Spring arguments without exposing persistence property names or unstable ordering.
Separates authentication challenge from denied authorization and traces the selected entry point, denied handler, and matched rule.
Uses version-ready notifications, user-safe reloads, cache policy, and deployment compatibility instead of activating mixed versions in place.