AZ-400 Design and implement source control Practice Question
Exhibit
Azure DevOps Git repository configuration: Branch policies: - Branch: main Required reviewers: 2 Minimum number of reviewers: 1 Reset code reviewer votes when new changes are pushed: true Automatically include code reviewers: ["user1@contoso.com", "user2@contoso.com"]
Refer to the exhibit. A developer pushes a new commit to an existing pull request targeting the main branch. What is the effect on the pull request?
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
✓
All existing approvals are revoked, and the pull request must be re-approved.
The policy 'Reset code reviewer votes when new changes are pushed' is set to true. Therefore, when a new commit is pushed, all previous reviewer votes are reset. The required number of reviewers is 2, but minimum is 1, so at least one reviewer must approve again.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The pull request is automatically merged.
Why it's wrong here
No automatic merge policy is configured for this pull request, so pushing a new commit merely updates the source branch and triggers a fresh policy evaluation; the PR remains open and requires manual completion or a merge action.
- ✗
The existing approvals remain valid, and no re-review is needed.
Why it's wrong here
Because the branch policy is set to reset approvals on new changes, any existing approvals are invalidated the moment the commit is pushed; the pull request must go through a new approval cycle before it can be completed.
- ✓
All existing approvals are revoked, and the pull request must be re-approved.
Why this is correct
With the reset-approvals policy enabled, all previously granted approvals are revoked as soon as a new commit is pushed to the source branch, requiring reviewers to re-approve the latest changes before the pull request can be merged.
- ✗
The new commit is rejected because it was pushed without a code review.
Why it's wrong here
Pushing a commit to an existing PR does not trigger a rejection for lack of review; the commit is accepted and the branch is updated. The reset policy only clears the approval status, which forces a new review but does not block or reject the commit itself.
Go deeper
Related to this question
Learn chapter
Managing Infrastructure as Code Using Azure
Key term
Pull request
A pull request is a way for a developer to propose changes to a codebase and ask other team members to review and merge them into the main project.
Key term
Branch
A branch is a pointer to a specific commit in a version control system that allows you to work on features or fixes in isolation from the main codebase.
About these practice questions
This AZ-400 question is part of Courseiva's 696-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.