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
Which Azure DevOps service connection type should be used to deploy resources to an Azure subscription using a service principal?
Answer: Azure Resource Manager service connection
The Azure Resource Manager service connection authenticates via a service principal (or managed identity) to authorize pipeline tasks to deploy Azure resources.
A pipeline deploys to 50 on-premises servers in a deployment group. The team wants only 10 servers updated at a time. Which deployment group job setting controls this?
Answer: Max parallel targets
The 'Maximum number of targets in parallel' setting on a deployment group job controls how many machines are updated simultaneously in each deployment batch.
In a release pipeline, what does setting the 'Deployment queue settings' to 'Deploy latest and cancel the others' accomplish?
Answer: Deploys only the most recent pending release and cancels any others waiting in queue
This setting ensures that when multiple releases are queued, only the latest version deploys while all other queued deployments are cancelled, reducing unnecessary deployments.
Which tool integrated into Azure Pipelines release gates uses work item queries to ensure all linked bugs are closed before a production deployment?
Answer: Query Azure DevOps Work Items gate
The 'Query Work Items' gate runs an Azure Boards query and fails the gate if the returned work item count doesn't meet the specified threshold (e.g., zero open critical bugs).
A DevOps engineer is using Helm charts to deploy to AKS from a release pipeline. Which task should they use to upgrade an existing Helm release?
Answer: Helm Deploy task with 'upgrade' command
The Helm Deploy task with the 'upgrade' command (helm upgrade) updates an existing Helm release in the AKS cluster using the specified chart and values.
What is the purpose of the 'protected' flag on an Azure Pipelines YAML environment?
Answer: It prevents the environment from being deleted by non-admins
Marking an environment as protected restricts deletion and modification to users with the Administrator role, preventing accidental removal of critical environments.
A team practicing trunk-based development wants every merge to 'main' to automatically deploy to staging but require approval before production. Which release pipeline configuration achieves this?
Answer: CD trigger on artifact filtered to 'main' branch, with auto-deploy to staging and pre-deployment approval on production stage
A continuous deployment trigger filtered to the 'main' branch auto-deploys to staging, while a pre-deployment approval gate on the production stage requires manual sign-off.