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 8 of 57
Explain why awaiting while holding synchronization resources can create deadlocks, contention, or stalled workflows.
Uses deadlock evidence to correct EF Core transaction scope, query plans, and resource order, with bounded retries only for repeat-safe victims.
Combines debounce cleanup, AbortController, and request identity to prevent stale search results.
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.
Improve diagnosis when App Service log stream does not show enough information during an incident.
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.
Uses Query Store and deployment evidence to diagnose and safely mitigate a concrete Azure SQL plan regression.
Identify a failed App Service deployment caused by a mismatched .NET runtime or publish target.
Builds a story about collaborating during an incident without chaos or duplicated work.
Diagnose and recover from a production failure caused by rotated secrets or stale secret references.
Investigate production failures caused by custom domain, DNS, TLS certificate, or HTTPS binding problems.
Explains a practical debugging path across browser, Next.js layer, API, logs, database, and deployment changes.
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.
Explains database connection pool exhaustion with practical .NET data-access examples and production trade-offs.
Diagnose browser CORS errors after moving an Azure-hosted API or frontend to a new custom domain.
Investigate resource spikes on App Service after a new .NET API release.
Diagnoses duplicate processing from Azure Service Bus lock loss or Storage Queue visibility behavior without repeating generic idempotency theory.