AZ-400 Continuous Delivery 2 — Questions and Answers
Question 1: Which Azure DevOps feature allows you to require a manual approval before a deployment proceeds to a production stage?
- Branch policy
- Pre-deployment approval gate (Correct answer)
- Service connection
- Artifact filter
Correct answer: Pre-deployment approval gate
Pre-deployment approvals in Azure Pipelines let you designate approvers who must sign off before a stage begins.
Question 2: A team wants to deploy to Azure App Service only when code coverage stays above 80%. Which mechanism enforces this in a release pipeline?
- Artifact trigger
- Quality gate (Correct answer)
- Deployment slot
- Build retention policy
Correct answer: Quality gate
Quality gates query external services (like SonarCloud) and block or allow deployment based on metric thresholds.
Question 3: What is the purpose of a deployment slot in Azure App Service during a continuous delivery process?
- It stores deployment logs for auditing
- It allows zero-downtime deployments via slot swap (Correct answer)
- It restricts deployments to business hours
- It enforces multi-region failover
Correct answer: It allows zero-downtime deployments via slot swap
Deployment slots let you deploy to a staging slot and then swap it with production, achieving near-zero downtime.
Question 4: Which artifact source type in Azure Pipelines supports triggering a release pipeline when a new Docker image is pushed?
- GitHub
- Azure Container Registry (Correct answer)
- Azure Repos Git
- NuGet feed
Correct answer: Azure Container Registry
Azure Container Registry can be configured as an artifact source, triggering releases when a new image tag is pushed.
Question 5: A YAML pipeline uses the 'environment' keyword targeting a Kubernetes namespace. What additional capability does this unlock?
- Automatic horizontal pod autoscaling
- Deployment history tracking and approvals at the environment level (Correct answer)
- Built-in canary traffic splitting
- Automatic rollback on pod crash
Correct answer: Deployment history tracking and approvals at the environment level
Using environments in YAML pipelines enables deployment history, traceability, and approval/check policies at the environment scope.
Question 6: When configuring a multi-stage YAML pipeline, which keyword controls the condition under which a stage runs?
- dependsOn
- condition (Correct answer)
- trigger
- strategy
Correct answer: condition
The 'condition' keyword evaluates an expression at runtime to decide whether a stage or job should execute.
Question 7: Your team wants every production deployment to be traceable to a specific work item. Which Azure DevOps feature supports this requirement?
- Artifact retention
- Release gates
- Deployment history linked to commits and work items (Correct answer)
- Service hooks
Correct answer: Deployment history linked to commits and work items
Azure Pipelines automatically associates commits and linked work items to each deployment recorded in the release history.
AZ-400 Continuous Delivery 2
Which Azure DevOps feature allows you to require a manual approval before a deployment proceeds to a production stage?