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.
298 results across 1 active filter
Page 3 of 13
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.
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.
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 a production issue caused by staging and production slot configuration drifting apart.
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.
Investigate production HTTP 500 errors that start immediately after a deployment slot swap.
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 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.
Designs an async export flow for large reports without blocking API requests or exhausting database and memory resources.
Designs dashboard APIs with precomputed metrics, freshness rules, query cost control, and drill-down support.