AZ-400 ยท Deployment strategies
Choosing a deployment strategy
Blue-green, canary, ring-based and progressive exposure, A/B testing, runOnce/rolling/canary strategies in deployment jobs, traffic shifting, choosing a strategy for a risk or rollback requirement.
Key points
- Blue-green runs two full environments and switches traffic, so rollback is just switching back.
- Canary and ring-based rollouts expose the new version to a small group first and widen step by step (progressive exposure).
- A/B testing compares two variants on a business metric.
- In Azure Pipelines deployment jobs, the built-in strategies are runOnce, rolling (VMs only) and canary (with increments such as [10, 20]).
Source: https://learn.microsoft.com/en-us/azure/well-architected/operational-excellence/safe-deployments
Practice questions
Which strategy keeps two identical production-capable environments and switches user traffic from the old one to the new one?
- Canary deployment
- A/B testing
- Blue-green deployment
- Recreate deployment
Show answer
Answer: C. Blue-green deployment
That is blue-green. Canary shifts a growing fraction of traffic to a new version and A/B testing compares variants; neither is defined by two full parallel environments.
Which are built-in strategies of an Azure Pipelines YAML deployment job?
- runOnce
- blueGreen
- rolling
- ring
- canary
Show answer
Answer: A. runOnce, C. rolling, E. canary
runOnce, rolling and canary are the supported keywords. blueGreen and ring are patterns you build with environments, slots or stages, not strategy keywords.
True or false: the rolling strategy in an Azure Pipelines deployment job can target Kubernetes resources as well as virtual machines.
Show answer
Answer: False
False. The rolling strategy is currently supported only for virtual machine resources; use canary for Kubernetes.
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.
