AZ-400 Configure processes and communications Practice Question
Which TWO Azure DevOps features can be used to implement change management processes?
⚠ Common exam trap
Test-takers frequently confuse features for documentation or testing (Test plans, Wiki) with those that enforce process controls, overlooking that change management requires approval workflows and audit trails, not just recording or searching content.
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
✓
Release approval gates.
Release approval gates (Option B) in Azure Pipelines allow you to enforce manual or automated checks before a release proceeds to a stage, implementing change management by requiring sign-offs or validation against external systems. Audit logging (Option C) captures a chronological record of changes to Azure DevOps resources, providing an immutable trail for compliance and change review processes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Test plans.
Why it's wrong here
Test plans are used for defining and running quality assurance tests, such as manual and automated test cases, to validate that a change behaves as expected. They do not provide change management controls, approvals, or auditability over the release process itself, so they are insufficient for implementing change management.
- ✓
Release approval gates.
Why this is correct
Release approval gates are a change management control that require designated reviewers to explicitly approve a release before it proceeds to an environment, and can also enforce automated checks. By gating the promotion of builds across stages, they ensure only authorized changes are deployed.
- ✓
Audit logging.
Why this is correct
Audit logging captures a tamper-evident record of user actions and changes across the Azure DevOps organization, including who changed what and when. This provides the traceability and change history needed to demonstrate compliance and control over modifications.
- ✗
Project wiki.
Why it's wrong here
Project wiki is a built-in knowledge base for creating and sharing documentation within a project, such as onboarding guides or architecture notes. It does not enforce approvals, track changes to code or releases, or provide any governance over what is deployed.
- ✗
Code search.
Why it's wrong here
Code search is a feature that lets users quickly locate code across repositories by keywords and filters, improving developer efficiency. It is purely a discovery tool and does not manage, approve, or record changes, so it cannot implement change management.
Visual reference
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Stage
A stage is a discrete phase in a software development or deployment pipeline where code is built, tested, integrated, or released in a controlled environment.
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.