Question 272 of 913
Design and implement a source control strategymediumMultiple ChoiceObjective-mapped

AZ-400 Practice Question: Design and implement a source control strategy

This AZ-400 practice question tests your understanding of design and implement a source control strategy. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Exhibit

Refer to the exhibit.
```json
{
  "branchProtectionRules": [
    {
      "branch": "main",
      "requiredStatusChecks": ["build", "test"],
      "enforceAdmins": true,
      "requiredPullRequestReviews": {
        "requiredApprovingReviewCount": 2,
        "dismissStaleReviews": true
      }
    }
  ]
}
```

You are reviewing the branch protection policy for the main branch in an Azure DevOps repository. Based on the exhibit, what happens when a stale review exists on a pull request after new changes are pushed?

Question 1mediummultiple choice
Full question →

Exhibit

Refer to the exhibit.
```json
{
  "branchProtectionRules": [
    {
      "branch": "main",
      "requiredStatusChecks": ["build", "test"],
      "enforceAdmins": true,
      "requiredPullRequestReviews": {
        "requiredApprovingReviewCount": 2,
        "dismissStaleReviews": true
      }
    }
  ]
}
```

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

The stale review is automatically dismissed, and the PR requires new approvals

The branch protection policy for the main branch has 'Reset code reviewer votes when there are new changes' enabled. When a stale review exists after new changes are pushed, Azure DevOps automatically dismisses the previous approval(s) and requires new approvals to meet the minimum number of reviewers (2). This ensures that reviewers re-evaluate the latest code changes before the pull request can be merged.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Admins are exempt from the review requirement

    Why it's wrong here

    enforceAdmins is true.

  • The stale review is automatically dismissed, and the PR requires new approvals

    Why this is correct

    dismissStaleReviews: true.

    Related concept

    Read the scenario before looking for a memorised answer.

  • The PR still requires only 2 approvals, but stale reviews are not dismissed

    Why it's wrong here

    dismissStaleReviews is true.

  • The PR can be merged even without the required reviews

    Why it's wrong here

    Required reviews are enforced.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may confuse 'stale reviews are not dismissed' with the default behavior of Azure DevOps, but the exhibit explicitly shows the 'Reset code reviewer votes when there are new changes' checkbox is enabled, which forces dismissal.

Detailed technical explanation

How to think about this question

Under the hood, Azure DevOps tracks each review vote as a stateful artifact tied to a specific commit ID. When new changes are pushed, the system compares the commit ID and automatically invalidates any votes associated with the previous commit, triggering a re-approval workflow. This behavior is controlled by the 'Reset code reviewer votes' setting in the branch policy, which is distinct from the 'Allow completion even if there are rejected votes' setting. In real-world scenarios, this prevents stale approvals from bypassing code review for incremental changes, ensuring that each iteration of the code is independently reviewed.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related AZ-400 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free AZ-400 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this AZ-400 question test?

Design and implement a source control strategy — This question tests Design and implement a source control strategy — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The stale review is automatically dismissed, and the PR requires new approvals — The branch protection policy for the main branch has 'Reset code reviewer votes when there are new changes' enabled. When a stale review exists after new changes are pushed, Azure DevOps automatically dismisses the previous approval(s) and requires new approvals to meet the minimum number of reviewers (2). This ensures that reviewers re-evaluate the latest code changes before the pull request can be merged.

What should I do if I get this AZ-400 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 25, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

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.