Configure processes and communications →mediumMultiple ChoiceObjective-mapped

AZ-400 Configure processes and communications Practice Question

Exhibit

{
  "branchPolicies": [
    {
      "scope": [
        {"repositoryName": "MyRepo", "branchName": "main"}
      ],
      "isEnabled": true,
      "settings": {
        "statusChecks": [
          {"context": "continuous-integration/azure-devops", "required": true},
          {"context": "security-scanner", "required": false}
        ],
        "minimumApproverCount": 0,
        "allowDirectPush": false
      }
    }
  ]
}

Refer to the exhibit. You are reviewing the branch policy configuration for the main branch in Azure DevOps. The policy requires a successful status check for 'continuous-integration/azure-devops' but not for 'security-scanner'. The minimum approver count is 0 and direct push is disallowed. What is the effect of this policy?

⚠ Common exam trap

Many candidates assume 'minimum approver count = 0' means direct push is allowed, or that all listed status checks are required, when in fact only explicitly selected checks are mandatory.

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

✓

Pull requests must pass the 'continuous-integration/azure-devops' check, but no reviewer approval is needed.

The policy requires a successful status check for 'continuous-integration/azure-devops' but not for 'security-scanner'. With a minimum approver count of 0 and direct push disallowed, pull requests must pass the required CI check, but no reviewer approval is needed. This means the PR can be completed automatically once the CI check passes, without any human reviewer.

Answer analysis

Option-by-option breakdown

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

✗
Developers can push directly to main without a pull request.
Why it's wrong here
The branch policy has allowDirectPush set to false, meaning direct pushes to main are blocked by the policy. Developers must create and successfully complete a pull request to merge changes into main, so this statement is incorrect.
✗
Pull requests require at least two reviewers.
Why it's wrong here
In the exhibit, the branch policy's Minimum approver count is set to 0, meaning Azure DevOps does not require even one reviewer approval, let alone two. No mandatory reviewer group is configured either, so there is no policy object that would enforce a two-reviewer rule. This option misreads the effective approval gate, which is zero required approvals.
✗
Both status checks are required to pass.
Why it's wrong here
Only the 'continuous-integration/azure-devops' status check is marked as required in the branch policy. The 'security-scanner' check is optional and not included in the required status checks, so the statement that both are required is incorrect.
✓
Pull requests must pass the 'continuous-integration/azure-devops' check, but no reviewer approval is needed.
Why this is correct
The branch policy lists 'continuous-integration/azure-devops' under required status checks, so a pull request cannot be merged until that CI check succeeds. However, the Minimum approver count is explicitly configured to 0, meaning no reviewer approval is part of the merge gate. Thus, the pull request is blocked only by the CI pipeline result, not by human code review.

Go deeper

AZ-400 Configure processes and communications Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question