Question 491 of 913
Design and implement build and release pipelineshardMultiple ChoiceObjective-mapped

AZ-400 Practice Question: Design and implement build and release pipelines

This AZ-400 practice question tests your understanding of design and implement build and release pipelines. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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
{
  "policies": [
    {
      "policy": {
        "name": "Require Pull Request Review",
        "isEnabled": true,
        "blocking": true,
        "settings": {
          "minimumApproverCount": 2,
          "creatorVoteCounts": false,
          "allowDownvotes": true,
          "resetOnPush": false
        }
      }
    }
  ]
}
```

You are configuring a branch policy for the main branch using the Azure DevOps REST API. The JSON above is the policy configuration. A developer pushes a new commit to an existing pull request. What happens to the existing approvals?

Question 1hardmultiple choice
Full question →

Exhibit

Refer to the exhibit.
```json
{
  "policies": [
    {
      "policy": {
        "name": "Require Pull Request Review",
        "isEnabled": true,
        "blocking": true,
        "settings": {
          "minimumApproverCount": 2,
          "creatorVoteCounts": false,
          "allowDownvotes": true,
          "resetOnPush": false
        }
      }
    }
  ]
}
```

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 existing approvals remain valid.

Option A is correct because, by default, Azure DevOps branch policies do not automatically reset approvals when a new commit is pushed to a pull request. The policy configuration shown does not include the 'resetOnPush' property (or its equivalent in the REST API), which is required to invalidate existing approvals. Without that setting, approvals remain valid even after new commits are pushed.

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.

  • The existing approvals remain valid.

    Why this is correct

    Correct: resetOnPush: false means approvals are not reset.

    Related concept

    Read the scenario before looking for a memorised answer.

  • The policy blocks the push until re-reviewed.

    Why it's wrong here

    The policy is blocking but this does not affect approval reset.

  • The pull request is automatically rejected.

    Why it's wrong here

    No automatic rejection based on policy.

  • All existing approvals are reset.

    Why it's wrong here

    resetOnPush is false, so approvals are not reset.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often assume any new commit to a pull request automatically resets approvals, but Azure DevOps requires explicit configuration (the 'resetOnPush' property) to enable that behavior.

Detailed technical explanation

How to think about this question

Under the hood, the Azure DevOps REST API for branch policies uses the 'settings' object to define policy behavior. The 'resetOnPush' property, when set to true, triggers a reset of all approvals on the pull request whenever a new commit is pushed. In this scenario, the absence of that property means the policy defaults to 'false', preserving existing approvals. This is a common configuration for teams that want to allow minor fixes without requiring re-approval, but it can be risky if strict review is needed for every change.

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 build and release pipelines — This question tests Design and implement build and release pipelines — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The existing approvals remain valid. — Option A is correct because, by default, Azure DevOps branch policies do not automatically reset approvals when a new commit is pushed to a pull request. The policy configuration shown does not include the 'resetOnPush' property (or its equivalent in the REST API), which is required to invalidate existing approvals. Without that setting, approvals remain valid even after new commits are pushed.

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.