Loading
Pick a focused question that fits your time, stack, and interview goal.
13 results across 1 active filter
Page 1 of 1
Reason through mitigation choices during a live App Service production incident.
Diagnose a deployment slot swap that fails because the target app does not warm up successfully.
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.
Investigate production HTTP 500 errors that start immediately after a deployment slot swap.
Explains staging slots, validation before swap, warm-up, traffic continuity, and safer production releases for App Service APIs.
Explains deployment versus release, staged enablement, kill switches, cleanup, and App Service slot interaction.
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 how to choose rollback, swap-back, hotfix, or roll-forward after a failed Azure App Service deployment.
Covers configuration that must stay with a slot, such as connection strings, secrets, callback URLs, and staging-only settings.
Covers build-once deployment, tests, artifact traceability, slot deployment, smoke checks, approvals, and post-release monitoring.