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 Pipelines artifact type allows a release pipeline to consume packages published to Azure Artifacts feeds?
Answer: Azure Artifacts artifact
The Azure Artifacts artifact source type links a release pipeline to a specific feed and package, enabling versioned package consumption in deployments.
A DevOps engineer wants to deploy an application to Azure App Service slots and then swap slots with zero downtime. Which task in Azure Pipelines performs the slot swap?
Answer: Azure App Service Manage
The 'Azure App Service Manage' task includes a slot swap action that swaps staging and production slots with near-zero downtime.
What is the primary purpose of using infrastructure as code (IaC) tools like ARM templates or Bicep within a release pipeline?
Answer: To provision and configure Azure resources consistently as part of the deployment
IaC tools embedded in release pipelines ensure target infrastructure is provisioned or updated to a desired state before or during application deployment.
In a release pipeline, which option ensures that only a specific build branch (e.g., 'main') triggers a continuous deployment?
Answer: Artifact filters / Branch filters
Artifact filters (also called branch filters) in the continuous deployment trigger restrict automatic releases to artifacts built from specified branches.
Which Azure service should a DevOps engineer integrate with a release pipeline gate to query the health of an external REST API before allowing deployment to proceed?
Answer: Invoke REST API gate
The 'Invoke REST API' gate calls an external HTTP endpoint and evaluates the response, allowing or blocking the release based on the result.
A release pipeline needs to deploy a containerized application to Azure Kubernetes Service (AKS). Which deployment strategy in AKS ensures that new pods replace old ones gradually while maintaining availability?
Answer: Rolling update strategy
Kubernetes rolling update strategy incrementally replaces old pods with new ones, maintaining a configurable minimum number of available pods throughout the update.
When configuring a multi-stage Azure release pipeline, which setting controls whether a stage automatically deploys when the previous stage succeeds?
Answer: Pre-deployment condition set to 'After stage'
Setting the pre-deployment condition to 'After stage' on a downstream stage causes it to automatically trigger when the specified upstream stage completes successfully.