Loading
Pick a focused question that fits your time, stack, and interview goal.
18 results across 1 active filter
Page 1 of 1
Diagnose a .NET API that fails to start on Azure App Service after a deployment.
Diagnose App Service app settings that reference Key Vault secrets but fail at runtime.
Identify a failed App Service deployment caused by a mismatched .NET runtime or publish target.
Investigate production failures caused by custom domain, DNS, TLS certificate, or HTTPS binding problems.
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.
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.
Covers App Service app settings, environment-specific configuration, restarts, slot settings, and avoiding hard-coded production values.
Explains health endpoints, readiness versus liveness, warm-up, dependency checks, and safe App Service health behavior.
Covers deployment logs, startup failures, runtime stack, app settings, missing files, Key Vault references, and post-deployment diagnosis.
Explains same-artifact promotion, environment-specific configuration, approvals, smoke testing, drift detection, and production traceability.
Compares App Service WebJobs and Azure Functions for queue processing, scheduled tasks, scaling, deployment ownership, and operational isolation.
Explains scale-out bugs from in-memory sessions, local caches, background queues, uploaded files, and per-instance behavior.
Covers custom domains, TLS, HTTPS, allowed hosts, CORS boundaries, and production-facing endpoint hygiene for App Service APIs.
Covers build-once deployment, tests, artifact traceability, slot deployment, smoke checks, approvals, and post-release monitoring.
Compares Azure hosting choices for a .NET API using operational complexity, scaling model, deployment ownership, and workload shape.
Explains local filesystem limits, multiple instances, in-memory state, distributed cache, durable storage, and scale-out-safe API design.