Free AZ-400 Exam Braindumps
Designing and Implementing Microsoft DevOps Solutions Questions 20–24 (page: 41)

Updated On: 16-Nov-2026

SIMULATION
In Project-12345678, you need to ensure that you can add the following iterations to items added to Azure Boards:
-Sprint 1
-Sprint 2
-Sprint 3
Sprint 3 must have as start date of January 1 of next year and an end date of January 31 of next year.

  1. See Explanation section for answer.

Answer(s): A

Explanation:

See explanation below.


To add Sprint 1, 2, and 3, and specifically configure Sprint 3 with dates of January 31 to January 31 of next year, follow these steps in Azure DevOps:
Action 1. Define Project-Level Iterations (Sprints)
Step 1: Navigate to your project in Azure DevOps [Select Project-12345678].
Step 2: Click Project settings (bottom left corner).
Step 3: Under the Boards section, select Project configuration.
Step 4: Select the Iterations tab.
Step 5: Click + New child to add sprints.
Step 6: Name them "Sprint 1", "Sprint 2", and "Sprint 3".
Action 2. Configure Sprint 3 Dates
Step 7: In the same Iterations tab, hover over Sprint 3 and click the three dots (...) to select Edit.
Step 8: In the dialog box, select the Start Date as January 1 of next year (\(01/01/2027\)).
Step 9: Set the End Date as January 31 of next year (\(1/31/2027\)).
Step 10: Click Save and close.
Action 3. Assign Sprints to Your Team [Skip this step. Not required]
Step 11: Go back to Project settings > Boards > Team configuration.
Step 12: Select the Iterations tab for your team.
Step 13: Click + Select Iteration(s) to add "Sprint 1", "Sprint 2", and "Sprint 3" to your team's active iterations.


Reference:

https://learn.microsoft.com/en-us/azure/devops/organizations/settings/set-iteration-paths-sprints



DRAG DROP (Drag and Drop is not supported)
You are using Agile process methodologies and Azure Boards in Azure DevOps.
You import the work items shown in the following table.

You need to categorize the items.
Which state should you assign to each item? To answer, drag the appropriate states to the correct items. Each state may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
Note: Each correct selection is worth one point.
Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: In Progress
Category states
Category states determine how Agile planning tools and select dashboard widgets treat each workflow state. The state categories used by the backlogs, boards and widgets are Proposed, In Progress, Resolved, and Complete.
In Progress: Assigned to states that represent active work. Work items assigned to states mapped to this category appear in the backlog (unless you choose to hide them) and make up the middle columns on Kanban boards.
Box 2: Proposed
Proposed: Assigned to states associated with newly added work items so that they appear on the backlog. The first column on the Kanban boards and Taskboards map to a Proposed state category.
Box 3: Completed
Completed: Assigned to states that represent work that has finished. Work items whose state is in this category don't appear on the backlog and do appear in the last column of the Kanban board. You can't modify states in this category nor can you add states to this category.


Reference:

https://learn.microsoft.com/en-us/azure/devops/boards/work-items/workflow-and-state-categories



HOTSPOT (Drag and Drop is not supported)
You have an Azure subscription that contains an Azure load testing instance named Test1 and an Azure App Service web app named App1.
You implement a CI/CD pipeline named Pipeline1 that uses Test1. Pipeline1 uses the following alt-config-pipeline1.yaml file.

For each of the following statements, select Yes if the statement is true, otherwise select No.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: No
No - Test1 will terminate after 180 seconds.
No, the test will not necessarily terminate after exactly 180 seconds.
While the durationInSeconds is set to 180, the total execution time will likely be longer due to test initialization and the configuration of your criteria.
Why It Takes Longer than 180 Seconds
Engine Startup Time: Azure Load Testing takes a few minutes to provision, configure, and boot up the 2 test engine instances before the test actually begins.
Ramp-up Time: Your 60-second ramp-up time is typically included within the total duration, but engine spin-down and data aggregation add time at the end.
Why It Might Terminate Early
The configuration includes a specific setting that can kill the test before it reaches the 180-second mark: Auto-Stop Function: The autoStop enabled. If the error rate hits 90% (errorPercentage: 90) within any 60-second window (timeWindow: 60), Azure will automatically abort the test immediately to save costs and protect your App Service.
Box 2: Yes
Yes - Test1 will fail if a request exceeds 250 ms.
Yes, Test1 will fail if any single request named "MyRequest" exceeds 250 ms.
Criteria definition: The pipeline configuration file (alt-config-pipeline1.yaml) contains the rule - MyRequest: max(response_time_ms) >250.
Metric function: The max function evaluates the absolute highest response time recorded during the test run.Failure trigger: If even one request takes 251 ms or longer, this specific threshold condition becomes true, which instructs Azure Load Testing to mark the overall pipeline test run as a failure.
Box 3: No
No - Test1 will run at peak load for 60 seconds.
No, the test will run at peak load for 120 seconds (2 minutes), not 60 seconds.
The configuration file defines a total duration and a ramp-up period:
Total Duration (durationInSeconds): 180 seconds
Ramp-Up Time (rampupTimeInSeconds): 60 seconds
How Peak Load Time is Calculated
Azure Load Testing calculates the time spent at peak load by subtracting the ramp-up time from the total duration: Peak Load Time=Total Duration-Ramp-Up Time
Peak Load Time= 180 s - 60 s = 120 s
During the first 60 seconds, the system linearly increases the load until it reaches 20 total virtual users (10 users per engine x 2 engines). It then sustains this maximum peak load for the remaining 120 seconds of the test.


Reference:

https://learn.microsoft.com/en-us/azure/app-testing/load-testing/quickstart-create-and-run-load-test



You are developing a multi-tier application. The application will use Azure App Service web apps as the front end and an Azure SQL database as the back end. The application will use Azure functions to write some data to Azure Storage.
You need to send the Azure DevOps team an email message when the front end fails to return a status code of 200.
Which feature should you use?

  1. Service Map in Azure Log Analytics
  2. availability tests in Azure Application Insights
  3. Profiler in Azure Application Insights
  4. Application Map in Azure Application Insights

Answer(s): B



You manage a project by using Azure Boards, and you manage the project code by using GitHub repositories.
You have a work item that has an ID of 123.
You need to link a commit message in GitHub to work item 123 on the board.
What are two ways to achieve the goal? Each correct answer presents a complete solution.
Note: Each correct selection is worth one point.

  1. From the Development settings of work item 123, select Add link, and then enter the URL of the commit.
  2. Add AB#123 to the text of the commit message.
  3. Add GH-123 to the text of the commit message.
  4. From the Links settings of work item 123, select Add link, select Existing item, and then enter the URL of the commit.
  5. To work item 123, add a comment that includes the URL of the commit.

Answer(s): A,B

Explanation:

Correct:
* Add AB#123 to the text of the commit message.
* To the description of the pull request, add #AB123.
or
* In the Development section for work item 123, select Add link, and then enter the URL of the pull request. * From the Development settings of work item 123, select Add link, and then enter the URL of the commit.
Incorrect:
* Add GH-123 to the text of the commit message.
* From the Links settings of work item 123, select Add link, select Existing item, and then enter the URL of the commit.
* From work item 123, open the Links tab, select Add link, select Existing item, and then enter the URL of the commit.
* To work item 123, add a comment that includes the URL of the commit.
* To work item 123 add a comment that includes the URL of the pull request.
Note:
Link GitHub commits, pull requests, and issues to work items in Azure Boards
Once you connect your Azure Boards project with a GitHub repository, you can link work items to your GitHub commits and pull requests. You can add links using the #mention syntax familiar to GitHub users or you can add a GitHub commit or GitHub pull request link type from the Azure Boards work item.
* Add AB#123 to the text of the commit message.
* To the description of the pull request, add #AB123.
Method 1: Use AB# to link from GitHub to Azure Boards work items
From a GitHub commit, pull request or issue, use the following syntax to create a link to your Azure Boards work item. Enter the AB#ID within the text of a commit message. Or, for a pull request or issue, enter the AB#ID within the title or description (not a comment).
AB#{ID}
For example, AB#125 links to work item ID 125.
* In the Development section for work item 123, select Add link, and then enter the URL of the pull request. * From the Development settings of work item 123, select Add link, and then enter the URL of the commit.
Method 2: Add link from a work item to a GitHub commit, pull request, or issue
Add link from a work item to a GitHub commit, pull request, or issue
1. To link to a commit or pull request, open the work item and choose Add link under the Development section.

To link to an issue, choose the Links tab, and then choose Add Link>Existing item.

2. From the Add link dialog, select one of the GitHub link types, enter the URL to the commit, pull request, or issue and then choose OK.
Here, we add a link to a GitHub pull request.

* From work item 123, open the Links tab, select Add link, select Existing item, and then enter the URL of the commit.


Reference:

https://learn.microsoft.com/en-us/azure/devops/boards/github/link-to-from-github



Viewing page 41 of 81
Viewing questions 201 - 205 out of 398 questions


Post your Comments and Discuss Microsoft AZ-400 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!