Loading
Pick a focused question that fits your time, stack, and interview goal.
84 results across 1 active filter
Page 1 of 4
Explains dependency duration, error rate, timeout rate, query tagging, Redis latency, HTTP downstream calls, and endpoint correlation.
Reason through mitigation choices during a live App Service production incident.
Compares rollback, roll-forward, feature kill switches, scaling, and degraded mode as incident mitigations.
Chooses a deployment strategy from capacity, compatibility, risk, observability, and rollback needs, then defines progressive promotion and abort signals.
Compares vendor-neutral OpenTelemetry concepts with Application Insights usage for .NET production services.
Explains sampling, high-cardinality labels, retention, cost, and keeping enough signal for incident diagnosis.
Explains deployment markers, version telemetry, feature-flag state, commit traceability, and incident diagnosis after releases.
Explains what belongs in runbooks, how on-call handoff preserves context, and how operational docs stay useful.
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.
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.