AZ-400 Practice Question: Design and implement build and release pipelines
Your organization uses Azure DevOps. You have a classic release pipeline that deploys to multiple stages: Dev, QA, and Prod. Each stage has a pre-deployment approval gate. Recently, the QA team complained that they are not receiving approval notifications. You have verified that the approval configuration is correct and the approvers are members of the 'QA Approvers' group. The release pipeline is set to send email notifications to the approvers. However, the QA approvers report they do not receive any emails when a release is pending their approval. What should you check first?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Verify that the organization-level notification settings allow email notifications for approvals.
The correct first step. Even if the pipeline's approval configuration is correct and the approvers are in the correct group, the organization-level notification settings in Azure DevOps can override individual pipeline settings. If email notifications for approvals are disabled at the organization level, no emails will be sent regardless of the pipeline configuration. Therefore, checking the organization-level notification settings should be the first troubleshooting step. Option A is not the first step because while spam filters could cause missed emails, the issue is more likely a system-level configuration problem. Option C is incorrect because Azure DevOps automatically sends approval notifications; adding a manual 'Send email' task is unnecessary and not a standard fix. Option D is incorrect because checking release pipeline logs might reveal delivery failures, but the most efficient first step is to verify the notification settings at the organization level.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Ask the QA team to check their spam folder.
Why it's wrong here
Approval notification emails are system-generated by Azure DevOps and are rarely misclassified as spam if the SMTP/notification configuration is correct. Checking spam folders is a secondary step; the first step should be to verify that email notifications are enabled in the organization-level settings, as disabled subscriptions or incorrect filters are the more likely cause.
- ✓
Verify that the organization-level notification settings allow email notifications for approvals.
Why this is correct
Verify that the organization-level notification settings allow email notifications for approvals, specifically the 'Release approval pending' subscription. In Azure DevOps, this subscription is a default system subscription that may be disabled or scoped to specific roles, and if it is turned off, approvers will not receive any approval notification emails regardless of personal notification preferences.
- ✗
Add a 'Send email' task in the pipeline before the approval gate.
Why it's wrong here
Adding a 'Send email' utility task before the approval gate is unnecessary because approval notifications are generated by Azure DevOps's built-in notification engine, not by pipeline tasks. This approach can duplicate notifications or create emails that are inconsistent with the actual approval state, and it does not fix any underlying notification configuration issue.
- ✗
Check the 'Release Pipeline' logs for a warning about email delivery failure.
Why it's wrong here
Release Pipeline logs record deployment activities and task execution, but they do not log email delivery failures for the notification system. Notification delivery is handled by the Azure DevOps platform itself, so the absence of a warning in the logs does not confirm that approval emails were sent successfully; configuration issues at the organization level are the typical root cause.
Visual reference
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Task
A Task in Azure DevOps is a predefined, reusable step that performs a specific action during a build or release pipeline, like compiling code or running tests.
Key term
Azure DevOps
Azure DevOps is a Microsoft service that provides development tools for planning, building, testing, and deploying software applications using automated pipelines and collaboration features.
About these practice questions
One of 823 original AZ-400 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.