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

Three parallel jobs with no dependsOn

Answer

One job with three deployment tasks and maxParallel: 1

Answer

Three environments with a single approval gate

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

It installs required pipeline extensions

Answer

It pulls the latest source code from the repository

Answer

It authenticates the service connection for the job

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

Using deployment groups with parallel execution

Answer

Configuring multiple CD triggers on the artifact

Answer

Creating separate release pipelines for each environment

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 deploys every commit automatically; continuous deployment requires manual approval

Answer

Continuous delivery applies only to infrastructure; continuous deployment applies to application code

Answer

There is no difference; the terms are interchangeable in Azure DevOps

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

Auto-redeploy trigger with rollback condition

Answer

Restart pipeline from the failed job using the YAML resume feature

Answer

Re-queue the CI build and trigger a new release

Question 6

Which service connection type should be configured when an Azure Pipelines release needs to deploy resources to an AWS environment?

Accepted Answer

AWS service connection via the AWS Toolkit for Azure DevOps extension

Answer

Azure Resource Manager service connection

Answer

Generic service connection with AWS endpoint

Answer

SSH service connection to an EC2 instance

Question 7

What is the 'release retention policy' in Azure DevOps release pipelines used for?

Accepted Answer

Controlling how long release records and associated artifacts are kept before automatic deletion

Answer

Limiting the number of concurrent release deployments

Answer

Setting the maximum duration a deployment stage can run

Answer

Defining which branches are eligible to trigger a release