Release Management Flashcards
7 cards from real AZ-400 practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Release Management flashcards as text
A company uses Azure Key Vault to store secrets. How should a release pipeline securely access these secrets without hardcoding them?
Answer: Link the Key Vault as a variable group and reference variables in the pipeline
Linking an Azure Key Vault to a variable group in Azure DevOps dynamically fetches secrets at runtime and exposes them as masked pipeline variables.
What is the difference between a 'Runbook' gate and an 'Invoke Azure Function' gate in Azure Pipelines release pipeline?
Answer: Runbook gates execute Azure Automation runbooks; Azure Function gates invoke serverless HTTP-triggered functions
The Runbook gate integrates with Azure Automation to run existing runbooks, while the Azure Function gate invokes an HTTP-triggered Azure Function for custom logic.
In Azure DevOps, what is a 'release definition' (classic) equivalent to in YAML pipelines?
Answer: A YAML pipeline file with stages defined under the 'stages' key
In YAML pipelines, the stages section with deployment jobs and environments replicates the functionality of a classic release definition with its environments and stages.
Which deployment strategy in Azure Pipelines YAML should be used to deploy to a percentage of targets first, verify health, then roll out to the rest?
Answer: canary
The 'canary' deployment strategy in YAML pipelines deploys to a defined percentage of targets first, allows health checks, then proceeds to the remaining targets.
A DevOps engineer needs to ensure that a failed deployment to production automatically triggers a rollback to the previous release. Which Azure Pipelines feature enables this?
Answer: Automatic redeploy on failure in stage options
The 'Auto-redeploy trigger' option in a stage's deployment conditions can be configured to redeploy the last successful release when the current deployment fails.
When using environments in Azure Pipelines YAML, what is the benefit of recording deployment history per environment?
Answer: It provides audit trails showing which commit and pipeline run deployed to each environment
Environment deployment history tracks which pipeline runs deployed to an environment, what commit was deployed, and who triggered it, providing full deployment audit capability.
A team wants to prevent multiple pipelines from deploying to the production environment simultaneously. Which Azure Pipelines environments feature handles this?
Answer: Exclusive lock on the environment
Setting an exclusive lock on a YAML pipeline environment ensures only one deployment job runs against that environment at a time, queuing others.