Exam AZ-400 topic 7 question 26 discussion

Should be: A build policy A status policy https://azuredevopslabs.com/labs/vstsextend/sonarcloud/ https://docs.microsoft.com/en-us/azure/devops/repos/git/branch-policies?view=azure-devops#build-validation

Got this in the AZ-400 exam (June 2021).

build validation and status policy

To ensure that your pull requests meet the specified criteria in Azure Repos, you should configure the following policy types: For the requirement that committed code must compile successfully, you should configure a build policy. This policy will enforce that all code submitted in pull requests is built and passes all the configured tests before it can be merged. For the requirement that pull requests must have a Quality Gate status of Passed in SonarCloud, you should configure a status policy. This policy will check the integration with SonarCloud to ensure that the code quality meets the defined standards before allowing the merge.

build policy status policy check policy are available only for TFVersion control https://learn.microsoft.com/en-us/azure/devops/repos/tfvc/add-check-policies?view=azure-devops

A build policy A status policy

build policy status policy

Build Policy Status Policy

Final answer after reading all the commnts 1. build policy 2. status policy

Action 1: Committed code must compile successfully Policy: Build policy A build policy is used to ensure that any changes made to the code can be successfully built. This means that before changes can be merged, the code must compile successfully, which is the requirement you're trying to enforce. By using a build policy, you can ensure that every pull request builds successfully before it's merged into the main branch. Action 2: Pull requests must have a Quality Gate status of Passed in SonarCloud Policy: Status policy A status policy requires that an external service posts a status to the pull request. In this case, the external service would be SonarCloud. SonarCloud can analyze the code and check whether it meets the defined quality standards (Quality Gates). If it does, SonarCloud can then post a Passed status to the pull request. The status policy will then check this status before allowing the pull request to be merged. Check-in policy is a term associated with TFVC (Team Foundation Version Control), not Git, hence it is not applicable here.

Status policy for SonarCloud => https://community.sonarsource.com/t/azure-devops-pull-request-quality-gate-status-check/33957/2

[X] Check-in policy is made for TFVC https://learn.microsoft.com/en-us/azure/devops/repos/tfvc/add-check-policies?view=azure-devops

build, status Successful last build, code analysis and work item association can be verified before every code commit in check-in policy. But this question is about PR request and not individual check-ins.

https://azuredevopslabs.com/labs/vstsextend/sonarcloud/ Committed code must compile successfully ---> Build policy Pull requests must pass ---> Status Policy

On exam 20220727. Answer is: Build policy Status policy

As per "Administrators of Team Foundation version control can add check-in policy.." So Microsoft docs clearly mentions Check-in policy is for TFVC not Git, for git it is build policy. answer is build and status policy as

this came in today exam Az-400 (Dec 2021)