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.
690 results
Page 7 of 29
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.
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.
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.
Traces duplicate side effects across message delivery, lock ownership, settlement, durable job state, and external idempotency, then repairs affected users safely.
Explains high database CPU after an API change with practical .NET data-access examples and production trade-offs.
Investigate production HTTP 500 errors that start immediately after a deployment slot swap.
Explains why server HTML and client render can disagree, how to debug it, and how to avoid mismatch-prone code.
Diagnose missing trace continuity when an API enqueues work processed by an Azure worker.
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.
Investigate messages that repeatedly fail and move to a poison queue or dead-letter queue.
Explains a constraint-first approach to responsive layout, intrinsic sizing, overflow, and content resilience.
Explains how to decide if caching is the right fix for a slow API endpoint instead of query tuning or contract changes.
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.