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 23 of 37
Explains cache interception, keys, conditions, eviction, proxy self-invocation, and the provider boundary.
Explains SQL joins for API response shapes with practical .NET data-access examples and production trade-offs.
Explains instruction authority while keeping provider-specific message roles separate from the application’s durable trust boundary.
Explains how decoding settings reshape token selection and why they must be tuned against task-specific evaluation rather than folklore.
Maps each part of the HTTP request to explicit controller arguments and distinguishes conversion, model binding, and body conversion.
Chooses interfaces or aliases based on object contracts, unions, composition, declaration merging, and team consistency.
Selects the smallest Spring test scope that can prove the risky boundary without mocking away framework or infrastructure behavior.
Uses input availability, rendering completion, cleanup, and SSR safety to choose lifecycle work deliberately.
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.
Models partial updates without confusing omitted fields, explicit nulls, defaults, or unauthorized changes.
Separates authentication challenge from denied authorization and traces the selected entry point, denied handler, and matched rule.
Connects virtual environments, pyproject metadata, version constraints, lock artifacts, Python versions, and CI verification.
Overrides dependencies at the provider boundary while preserving the same injection scope and contract used in production.
Binds related values to typed configuration properties, applies validation constraints, and fails with actionable non-secret diagnostics.
Contrasts abstraction's caller-facing contract with encapsulation's control of internal state and shows how one object can use both.
Treats prompts as observable behavior, removes secrets and authorization policy from them, and limits the consequence of disclosure.
Propagates request cancellation through async dependencies while keeping committed side effects and timeout policy explicit.
Makes duplicate-key behavior explicit through validation, merge policies, grouping, and deterministic map selection.
Separates restart-worthy process failure from traffic readiness and composes Spring Boot health groups around those meanings.
Uses Optional to model absence at return boundaries and avoids eager defaults, null Optionals, unsafe get calls, and awkward field or parameter usage.
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.
Uses Pydantic models as explicit transport contracts without making them persistence or domain models automatically.