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 11 of 52
Handles SIGTERM, traffic draining, cancellation, background work, and termination deadlines without losing accepted work or hanging rollout.
Investigate and mitigate API failures caused by a slow or failing downstream dependency.
Explains optimistic concurrency with EF Core rowversion tokens, API conflict responses, and safe retry boundaries.
Defines what happens when several operations fail, cancellation arrives, or only part of a parallel batch completes, without orphaning work or hiding errors.
Separates process start from readiness, coordinates hosted-service startup, and drains work within a bounded shutdown window.
Handles an urgent production fix from verified impact and deployed provenance through minimal code, focused validation, controlled rollout, rollback readiness, and merge-forward.
Explains context propagation, value identity, provider scope, domain separation, and measured optimization.
Explains when to capture dumps, what to compare, and how to use roots without turning dumps into guesswork.
Separates development and held-out cases, controls access, detects duplication, and validates improvements on fresh traffic.
Balances AI quality, tail latency, and cost through explicit product thresholds, model choice, context control, caching, routing, and measurement.
Draws a short atomic database boundary around one invariant while moving network side effects into explicit, recoverable workflow states.
Explains EF Core query performance diagnostics with practical .NET data-access examples and production trade-offs.
Profiles real interactions to separate excessive change detection, expensive component work, layout cost, and network delay before optimizing.
Uses version-ready notifications, user-safe reloads, cache policy, and deployment compatibility instead of activating mixed versions in place.
Explains a structured response to a failed production deployment in a .NET application.
Uses production build output, explicit budgets, dependency analysis, and meaningful lazy boundaries instead of arbitrary size cuts.
Keeps server and client output compatible while isolating browser APIs, user state, and post-render integration.
Explains safe EF Core migrations with practical .NET data-access examples and production trade-offs.
Controls virtual time and completion order to prove debounce, switching, retries, and teardown without sleeping in tests.
Separates model and provider outcomes, applies bounded recovery, validates outputs, and exposes useful status and telemetry.
Returns correlated, minimal, typed, and safely bounded tool results without confusing them with trusted instructions.
Defines success, failure, step, time, token, cost, retry, and repetition limits with useful escalation behavior.
Combines production-shaped, expert-authored, edge, and adversarial cases with versioned labels and privacy controls.
Combines a canonical detail page with an intercepted modal, Parallel Route slot, browser history, and accessible dismissal.