AZ-400 ยท Deployment strategies
Ordering dependent deployments and hotfix paths
Ordering dependent deployments across stages and pipelines, pipeline resources and triggers, hotfix branches and expedited paths that still pass gates, backporting fixes.
Key points
- Stages run in order; dependsOn builds the graph (fan-out, fan-in).
- By default a stage runs only if everything it depends on succeeded.
- Across pipelines: pipeline resources with triggers start the downstream pipeline after the upstream one completes.
- Hotfix: branches from what is in production and goes through an accelerated version of the same stages and gates.
- Then backport it to the main line so the fix is not lost.
Source: https://learn.microsoft.com/en-us/azure/devops/pipelines/process/stages?view=azure-devops
Practice questions
Which YAML keyword makes a stage wait for another stage?
- waitFor
- after
- requires
- dependsOn
Show answer
Answer: D. dependsOn
dependsOn declares the dependency graph between stages. condition only refines when a stage runs, and trigger: manual just requires a manual start.
Which practices fit a well-designed hotfix path?
- Branch from the commit or tag currently in production
- Copy the binaries to production by hand to save time
- Run the fix through the same stages with accelerated approvals and tests
- Merge or cherry-pick the fix back to the main branch afterwards
- Disable all environment checks for the whole organization during incidents
Show answer
Answer: A. Branch from the commit or tag currently in production, C. Run the fix through the same stages with accelerated approvals and tests, D. Merge or cherry-pick the fix back to the main branch afterwards
A hotfix starts from the code in production, still passes the pipeline (possibly accelerated), and is backported so the next release keeps the fix. Skipping the pipeline or the backport creates regressions.
True or false: in a multi-stage YAML pipeline, stages run in parallel by default unless you add dependsOn.
Show answer
Answer: False
False. Stages run one after another in the order they are defined; you use dependsOn (for example dependsOn: []) to change that.
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.
