AZ-400 ยท Deployment strategies
Minimizing downtime with slots and rolling
Load balancing and health probes, rolling deployments, App Service deployment slots with swap and warm-up, slot-specific settings, traffic routing percentage.
Key points
- App Service deployment slots (Standard tier and above): live apps with their own host names.
- Deploy to staging; target slot settings apply, every instance warms up, then routing rules switch, so no requests drop.
- Swapping the same slots again rolls back.
- VMs: rolling strategy with maxParallel keeps some machines serving.
- Load balancer health probes keep unhealthy instances out of rotation.
Source: https://learn.microsoft.com/en-us/azure/app-service/deploy-staging-slots
Practice questions
What is the lowest App Service plan tier that supports deployment slots?
- Free
- Basic
- Standard
- Premium only
Show answer
Answer: C. Standard
Slots start at Standard (Standard, Premium, Isolated). Free and Basic tiers do not support them.
Which items stay with their slot and are NOT swapped?
- Custom domain names
- Language framework version (for example .NET version)
- Scale settings
- WebJobs content
- App settings marked as deployment slot settings
Show answer
Answer: A. Custom domain names, C. Scale settings, E. App settings marked as deployment slot settings
Custom domain names, scale settings and app settings marked as deployment slot settings stay put. Runtime/framework versions and WebJobs content travel with the app.
True or false: after a slot swap, the previous production version is lost and cannot be restored quickly.
Show answer
Answer: False
False. After a swap the old production app sits in the source slot, so swapping the same two slots again restores the last known good site.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
