AZ-400 Continuous Delivery & Release Management 4 — Questions and Answers
Question 1: A release pipeline must wait for an external system to signal readiness before proceeding. Which gate mechanism is most appropriate?
- Query Work Items gate
- Invoke REST API gate (Correct answer)
- Query Azure Monitor Alerts gate
- Manual intervention task
Correct 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.
Question 2: In YAML pipelines, what is the correct way to reference a secret variable stored in Azure Key Vault within a pipeline step?
- Directly reference $(secretName) after linking the Key Vault variable group (Correct answer)
- Use the az keyvault secret show command inline
- Hardcode the secret value in the YAML file
- Access secrets only via environment-level approvals
Correct 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.
Question 3: Which deployment pattern involves running two identical production environments, switching traffic between them for each release?
- Canary deployment
- Rolling deployment
- Blue-green deployment (Correct answer)
- Shadow deployment
Correct 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.
Question 4: What is the effect of setting 'trigger: none' at the top of an Azure Pipelines YAML file?
- The pipeline runs on every branch push
- The pipeline is disabled entirely and cannot be queued
- CI triggers are disabled; the pipeline runs only when manually triggered or via API (Correct answer)
- The pipeline only triggers on pull requests
Correct 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.
Question 5: 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?
- In the pipeline YAML under the approvals section
- As a required reviewer policy on the main branch
- In the Environments settings with an approval and check requiring two reviewers (Correct answer)
- In the service connection security settings
Correct 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.
Question 6: Which Azure Pipelines concept allows you to define reusable deployment logic that can be called from multiple pipeline files?
- Task groups (classic) or templates (YAML) (Correct answer)
- Deployment groups
- Variable groups
- Pipeline artifacts
Correct 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.
Question 7: When using Azure release pipelines, what is the function of 'pre-deployment conditions' compared to 'post-deployment conditions'?
- Pre-deployment conditions validate the artifact before the build; post-deployment validate after the build
- Pre-deployment conditions (approvals/gates) must pass before the stage starts; post-deployment conditions run after the stage completes (Correct answer)
- Pre-deployment conditions set variables; post-deployment conditions clean up resources
- They are identical in function but applied at different pipeline scopes
Correct 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.
AZ-400 Continuous Delivery & Release Management 4
A release pipeline must wait for an external system to signal readiness before proceeding.
Which gate mechanism is most appropriate?