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.
460 drills fit a 10-minute session. Closest fits first.
Page 1 of 20
Explains audit fields and data change tracking with practical .NET data-access examples and production trade-offs.
Maps creation, updates, asynchronous work, validation, authorization, conflicts, and failures to useful HTTP outcomes.
Places state according to who owns it, how long it must live, and whether the URL or server is the source of truth.
Builds a proportionate test plan from blast radius, failure probability, detectability, and reversibility.
Chooses between sequence, counted, indexed, set, and dictionary contracts based on required operations and complexity.
Explains what a lambda captures, how captured state is shared, and why a long-lived callback can retain more memory than expected.
Review async .NET code that does not accept or propagate CancellationToken and explain the practical production risk.
Designs controlled diagnostic access, collection triggers, container permissions, artifact egress, privacy, retention, and post-capture verification.
Explains how environment configuration drift causes deployment bugs and how to reduce it.
Explains how later configuration providers override earlier values and keeps secrets, environment overrides, and diagnostics within explicit boundaries.
Debugs ASP.NET Core authentication challenges and authorization forbids across schemes, token validation, policies, claims, tenants, and resource checks.
Uses resource state, structured logs, traces, metrics, health, and configuration evidence to isolate a cross-service failure.
Handle a production support case where logs exist but related request events cannot be connected.
Diagnose a .NET API that fails to start on Azure App Service after a deployment.
Diagnose App Service app settings that reference Key Vault secrets but fail at runtime.
Diagnose a deployment slot swap that fails because the target app does not warm up successfully.
Diagnose a growing queue backlog in an Azure-based background processing system.
Builds a story about collaborating during an incident without chaos or duplicated work.
Investigate production failures caused by custom domain, DNS, TLS certificate, or HTTPS binding problems.
Investigate SQL timeouts that appear after a new .NET API release.
Diagnose authentication redirect or callback failures after a slot swap or domain change.
Investigate an endpoint accepting invalid data or returning inconsistent validation errors.
Investigate a production issue caused by staging and production slot configuration drifting apart.
Investigate resource spikes on App Service after a new .NET API release.