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 38 of 52
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.
Uses explicit status and field semantics so absence, null, not-applicable, and insufficient evidence are not conflated.
Explains decimal construction, scale, equality, rounding, and why BigDecimal needs a money contract around it.
Explain how Task.WhenAll behaves when one or more tasks fail and how to inspect failures safely.
Covers using managed identity and Microsoft Entra authentication for Azure SQL access from a .NET API.
Builds an immutable Java type through valid construction, final state, defensive copying, controlled exposure, and safe sharing.
Explains health endpoints, readiness versus liveness, warm-up, dependency checks, and safe App Service health behavior.
Creates queryable structured events with trace correlation, stable fields, useful context, and deliberate redaction.
Repairs unstable Hook order caused by branches, early returns, callbacks, loops, or exception paths.
Keeps credentials in trusted executors and replaces broad reusable secrets with scoped references and short-lived authority.
Binds typed configuration, understands property precedence, validates startup invariants, and keeps secrets outside source control.
Uses routers as feature-oriented HTTP modules while keeping application logic, composition, and contract ownership clear.
Explains same-artifact promotion, environment-specific configuration, approvals, smoke testing, drift detection, and production traceability.
Explains correlation IDs, distributed tracing, dependency telemetry, message boundaries, and logs across App Service, queues, and downstream APIs.