Continuous Delivery & 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 Continuous Delivery & Release Management flashcards as text
A release pipeline must wait for an external system to signal readiness before proceeding. Which gate mechanism is most appropriate?
Answer: Invoke REST API gate
The 'Invoke REST API' gate polls an external endpoint and proceeds only when the API returns a success response, enabling integration with any external system.
In YAML pipelines, what is the correct way to reference a secret variable stored in Azure Key Vault within a pipeline step?
Answer: Directly reference $(secretName) after linking the Key Vault variable group
By linking an Azure Key Vault to a variable group and referencing that variable group in the pipeline, secrets become available as $(secretName) at runtime.
Which deployment pattern involves running two identical production environments, switching traffic between them for each release?
Answer: Blue-green deployment
Blue-green deployments maintain two identical environments; the router switches all traffic to the new (green) environment after validation, enabling instant rollback by switching back.
What is the effect of setting 'trigger: none' at the top of an Azure Pipelines YAML file?
Answer: CI triggers are disabled; the pipeline runs only when manually triggered or via API
Setting 'trigger: none' disables automatic CI triggers so the pipeline only runs when manually queued, triggered by another pipeline, or via REST API.
A team needs to ensure every production deployment is approved by at least two people from the security team. Where should this be configured in YAML pipelines?
Answer: In the Environments settings with an approval and check requiring two reviewers
Environment-level approvals in Azure Pipelines allow configuring required reviewers with minimum approval counts before any deployment to that environment proceeds.
Which Azure Pipelines concept allows you to define reusable deployment logic that can be called from multiple pipeline files?
Answer: Task groups (classic) or templates (YAML)
Task groups in classic pipelines and YAML templates both enable packaging reusable steps or stages that can be referenced across multiple pipelines.
When using Azure release pipelines, what is the function of 'pre-deployment conditions' compared to 'post-deployment conditions'?
Answer: Pre-deployment conditions (approvals/gates) must pass before the stage starts; post-deployment conditions run after the stage completes
Pre-deployment conditions (approvals and gates) block a stage from starting until satisfied, while post-deployment conditions validate success after the stage finishes.