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.
579 results across 1 active filter
Page 6 of 25
Identify a failed App Service deployment caused by a mismatched .NET runtime or publish target.
Diagnose and recover from a production failure caused by rotated secrets or stale secret references.
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.
Explains high database CPU after an API change with practical .NET data-access examples and production trade-offs.
Diagnose a post-swap HTTP 500 from supplied database-migration evidence and choose a safe mitigation.
Explains why server HTML and client render can disagree, how to debug it, and how to avoid mismatch-prone code.
Diagnose a .NET API that cannot connect to Azure SQL using managed identity.
Investigate a .NET API that appears to run but sends little or no telemetry to Application Insights.
Explains how to troubleshoot absent logs or telemetry by checking configuration, sampling, sinks, levels, deployment, and correlation.
Explains a constraint-first approach to responsive layout, intrinsic sizing, overflow, and content resilience.
Implements duplicate suppression while preserving the first event for each idempotency key.
Turns business recovery targets into right-sized backup, restore, standby, failover, validation, ownership, and rehearsal plans.
Define logs, metrics, traces, alerts, and dashboards needed to operate an ASP.NET Core API in production.
Explains how to design DTOs, response shapes, UI needs, API compatibility, and frontend/backend ownership for a feature.
Distinguishes callable delegate values from publisher-controlled events and makes subscription lifetime explicit.
Distinguishes explicit dependency injection from runtime service lookup and identifies the narrow framework boundaries where scoped resolution is legitimate.
Keeps business policy independent from infrastructure while centralizing concrete dependency assembly at the application edge.