Exam AZ-400 topic 5 question 7 discussion

The right set of steps in the build pipeline is 1. Prepare Analysis Configuration – First you prepare the analysis configuration for SonarCloud 2. Visual Studio Build – Next you need to build your .Net project 3. Visual Studio Test – Next run the unit tests 4. Run Code Analysis – Then you run the code analysis using the SonarCloud tools

The answer is correct: Reorder the tasks to respect the following order: 1.Prepare Analysis Configuration task before any MSBuild or Visual Studio Build tasks. 2.Run Code Analysis task after the Visual Studio Test task. 3.Publish Quality Gate Result task after the Run Code Analysis task https://docs.sonarqube.org/latest/analysis/scan/sonarscanner-for-azure-devops/

correct ansewer according with the microsoft learning path https://microsoftlearning.github.io/AZ400-DesigningandImplementingMicrosoftDevOpsSolutions/Instructions/Labs/AZ400_M07_L14_Managing_technical_debt_with_SonarQube_and_Azure_DevOps.html

Agree with answer

1. Prepare Analysis Configuration 2. VS Build 3. VS Test 4. Run Code Analysis https://docs.sonarqube.org/latest/devops-platform-integration/azure-devops-integration/ - In Azure DevOps, create or edit a Build Pipeline, and add a new Prepare Analysis Configuration task before your build task - Add a new Run Code Analysis task after your build task

Order of answer is logically correct so I would go with it

Prepare analysis configuration Visual Studio Build Visual Studio Test Run code Analysis

Prepare -> Build -> Test -> Analysis

Config --> build --> test --> analysis

Given answer is correct, I have done the same configuration in my project

In that doc: 6. Click the Visual Studio Test task and check the Code Coverage Enabled checkbox to process the code coverage and have it imported into SonarQube. (Optional but recommended) Once all this is done, you can trigger a build

I agree with the examtopics. 1. prepare 2. build 3. Test 4. Run code Section "Analyzing a .NET solution" from: https://docs.sonarqube.org/latest/analysis/scan/sonarscanner-for-azure-devops/ Publish build artifacts doesn't necessary because the goal is to TEST app instead of deploy app

1. Analysis 2. Build 3.Test 4.Run 5. Publish

Analyzing a .NET solution In your build definition, add: At least Prepare Analysis Configuration task and Run Code Analysis task Optionally Publish Quality Gate Result task Reorder the tasks to respect the following order: Prepare Analysis Configuration task before any MSBuild or Visual Studio Build tasks. Run Code Analysis task after the Visual Studio Test task. Publish Quality Gate Result task after the Run Code Analysis task Click on the Prepare Analysis Configuration build step to configure it: You must specify the service connection (i.e. SonarQube) to use. You can: select an existing endpoint from the drop down list add a new endpoint manage existing endpoints Keep Integrate with MSBuild checked and specify at least the project key Project Key - the unique project key in SonarQube Project Name - the name of the project in SonarQube Project Version - the version of the project in SonarQube Click the Visual Studio Test task and check the Code Coverage Enabled checkbox to process the code coverage and have it imported into SonarQube. (Optional but recommended) Once all this is done, you can trigger a build

Answer is correct, follow the link provided on the answer section, make sure you check .net section

prepare run code analysis publish quality gate build

From that link Tos0, under "Analyzing a .NET solution" (assuming that the VSbuild task comes in at B after "Prepare": Reorder the tasks to respect the following order: Prepare Analysis Configuration task before any MSBuild or Visual Studio Build tasks. Run Code Analysis task after the Visual Studio Test task. Publish Quality Gate Result task after the Run Code Analysis task