Design and implement build and release pipelines2 / 5
A team wants to roll out a new microservice version to an Azure Kubernetes Service cluster gradually: first to 10% of pods, then 20%, monitoring health after each traffic shift, and finally promoting to 100% only if health checks pass. Which deployment strategy in an Azure Pipelines deployment job should they use?
CorrectIncorrect
Alex
Azure Pipelines deployment jobs support three strategies: runOnce, rolling, and canary. runOnce executes each lifecycle hook (preDeploy, deploy, routeTraffic, postRouteTraffic) exactly once. rolling replaces application instances on a fixed set of VMs in batches controlled by maxParallel and is currently supported only for VM resources. canary is the advanced strategy for incremental exposure: it runs preDeploy once, then iterates deploy, routeTraffic, and postRouteTraffic for each increment (for example 10%, then 20%), monitoring health in postRouteTraffic before promoting to 100%. The strategy.increment variable is available during those iterating hooks. Note blueGreen is not a built-in deployment-job strategy keyword. Exam tip: phased percentage rollout with health checks between increments equals canary; VM batch replacement equals rolling; single execution equals runOnce.
Sourcelearn.microsoft.com
Follow-up answers are available in the app. Create a free account — no credit card required.
Question 2 of 5
Create a free account