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 feature allows you to require manual approval before a deployment proceeds to a production environment?
Answer: Pre-deployment approvals
Pre-deployment approvals in Azure Pipelines require designated approvers to manually authorize a deployment before it proceeds to the target stage.
A team wants to automatically roll back a release if Application Insights detects error rates above 5% after deployment. Which release pipeline feature should they configure?
Answer: Post-deployment gates
Post-deployment gates evaluate conditions after deployment (such as Application Insights metrics) and can trigger automatic rollback if thresholds are breached.
What is the purpose of a deployment group in Azure Pipelines?
Answer: A logical set of target machines for deployment jobs
A deployment group is a logical set of physical or virtual target machines, each with an installed agent, used to run deployment jobs across multiple servers.
Which deployment strategy deploys a new version to a small subset of servers first, monitors results, then gradually rolls out to all servers?
Answer: Rolling deployment
Rolling deployment incrementally updates servers in batches, reducing risk by monitoring each batch before proceeding to the next.
In Azure Pipelines, what does a release trigger set to 'Continuous deployment' do?
Answer: Creates a new release automatically whenever the linked artifact is updated
A continuous deployment trigger automatically creates and starts a new release pipeline run whenever a new build artifact is published.
A company needs to ensure their Azure release pipeline only deploys during business hours on weekdays. Which feature should they use?
Answer: Deployment conditions with time-based gates
Deployment conditions allow you to specify time-based restrictions (schedifying allowed deployment windows) to prevent releases outside approved hours.
What is the key benefit of using release variables scoped to a specific stage in Azure Pipelines?
Answer: They allow stage-specific values like environment URLs without duplicating pipelines
Stage-scoped variables let you define environment-specific values (e.g., connection strings, URLs) that override pipeline-level variables only within that stage.