AZ-400 Continuous Delivery & Release Management 5

Question 1

A pipeline must deploy to three regions sequentially, failing fast if any region fails. Which YAML configuration achieves this?

Accepted Answer

Three stages each with dependsOn pointing to the previous stage and condition: succeeded()

Answer

Chaining stages with dependsOn and condition: succeeded() ensures each region deploys only after the previous succeeds, providing sequential fail-fast behavior.

Question 2

What is the purpose of the 'Initialize Job' step that automatically appears at the start of every Azure Pipelines job?

Accepted Answer

It sets up the agent environment, downloads tools, and prepares the workspace

Answer

The Initialize Job step prepares the hosted or self-hosted agent by setting environment variables, configuring the workspace, and downloading required agent capabilities.

Question 3

Which Azure Pipelines feature enables releasing the same build artifact to multiple environments in parallel rather than sequentially?

Accepted Answer

Setting dependsOn to an empty array [] on multiple stages

Answer

Setting dependsOn: [] on multiple stages removes their dependency on each other, allowing them to execute in parallel after their common predecessor completes.

Question 4

In Azure DevOps, what does 'continuous delivery' differ from 'continuous deployment'?

Accepted Answer

Continuous delivery ensures every build is release-ready but may require manual approval to deploy; continuous deployment automatically deploys every successful build

Answer

Continuous delivery automates the release process up to a production-ready state but may include a manual approval gate, while continuous deployment fully automates production releases without human intervention.

Question 5

A release fails in the 'Deploy to Staging' stage. Which built-in Azure release pipeline option can automatically retry the failed stage with the same artifact?

Accepted Answer

Re-deploy option on the failed stage from the release summary

Answer

The 'Redeploy' option on a failed stage in the Azure release pipeline summary allows re-executing that stage without creating a new release.

AZ-400 Practice Test

AZ-400 Practice Test

AZ-400 Continuous Delivery & Release Management 5