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.
65 results across 1 active filter
Page 2 of 3
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.
Turns business recovery targets into right-sized backup, restore, standby, failover, validation, ownership, and rehearsal plans.
Explains alert design based on user-impact symptoms, SLOs, burn rate, thresholds, and avoiding noisy cause-only alerts.
Designs a file workflow with metadata, durable storage, validation, access control, scanning, and safe downloads.
Explains health checks that prove an API can serve traffic without becoming fragile dependency probes.
Decide whether Azure SQL errors are transient platform faults or a real application/query regression.
Makes EF Core transient retries safe across transactions, uncertain commits, generated keys, and external side effects.
Explains how an API behaves when Redis is unavailable and which cache usages can safely fall back.
Explains initial incident triage: confirm impact, mitigate, assign roles, preserve evidence, and communicate.
Explains staging slots, validation before swap, warm-up, traffic continuity, and safer production releases for App Service APIs.
Explains how App Service plans provide compute capacity, how scale-out affects app instances, and why APIs need stateless design.
Explains deployment versus release, staged enablement, kill switches, cleanup, and App Service slot interaction.
Explains how App Service can resolve Key Vault references through managed identity and what to watch during rotation and environment setup.
Explains transient database errors, retry strategy, EF Core execution strategy, idempotency, timeouts, and avoiding retry storms.
Covers App Service app settings, environment-specific configuration, restarts, slot settings, and avoiding hard-coded production values.
Covers using managed identity and Microsoft Entra authentication for Azure SQL access from a .NET API.
Explains health endpoints, readiness versus liveness, warm-up, dependency checks, and safe App Service health behavior.
Covers queue-backed work, idempotency, retries, visibility timeout, poison messages, progress tracking, and choosing Storage Queues or Service Bus.
Covers deployment logs, startup failures, runtime stack, app settings, missing files, Key Vault references, and post-deployment diagnosis.
Explains safe migration strategy for Azure-hosted .NET APIs, including expand-contract changes, locking risk, rollback, and deployment order.
Explains same-artifact promotion, environment-specific configuration, approvals, smoke testing, drift detection, and production traceability.
Explains correlation IDs, distributed tracing, dependency telemetry, message boundaries, and logs across App Service, queues, and downstream APIs.