Technical interview questions and drills

24 results across 1 active filter

Page 1 of 1

Showing the Azure .NET Production Hosting curriculum. Technology tags describe each drill's actual implementation context; shared drills can belong to more than one track.

Architecture scenarioMedium~10 min

Design a reversible Azure App Service release

Designs App Service slot releases so rollback, roll-forward, and targeted disablement remain evidence-based options.

In Azure .NET Production HostingShared across 2 tracks

Application InsightsAzureAzure App Service

Drills

Design a reversible Azure App Service release

How do Azure App Service deployment slots make .NET releases safer?

How does an App Service plan affect scaling for a .NET API?

How do feature flags change Azure App Service deployment strategy?

How do Key Vault references and managed identity work in App Service?

How should a .NET API handle Azure SQL transient faults?

How should configuration work for a .NET API in Azure App Service?

How would a .NET API connect to Azure SQL without a password?

How would you design health checks for an App Service-hosted .NET API?

How would you design queue-based background processing in Azure?

How would you diagnose a failed Azure App Service deployment?

How would you handle database migrations during an Azure App Service deployment?

How would you promote a .NET App Service release through dev, staging, and production?

How would you trace a request across Azure-hosted services?

OpenTelemetry vs classic Application Insights SDK in a .NET API

WebJobs vs Azure Functions for background work in a .NET system

What Application Insights baseline would you add to a .NET API?

What are slot settings and why do they matter during an App Service swap?

What Azure Monitor alerts would you create for a production .NET API?

What breaks when an App Service API scales out with in-memory state?

What production boundary checks matter for an App Service web API?

What should a CI/CD pipeline do when deploying a .NET API to App Service?

When would you host a .NET API on App Service, AKS, or Azure Functions?

Why should an App Service-hosted API be stateless across instances?