Free AZ-400 Exam Braindumps
Designing and Implementing Microsoft DevOps Solutions Questions 1–4 (page: 37)

Updated On: 16-Nov-2026
View Related Case Study

You need to the merge the POC branch into the main branch. The solution must meet the technical requirements.
Which command should you run?

  1. git rebase
  2. git merge --squash
  3. git push
  4. git merge --allow-unrelated-histories

Answer(s): B

Explanation:

The commit history of the POC branch must replace the history of the default branch.
Squash merging is a merge option that allows you to condense the Git history of topic branches when you complete a pull request. Instead of each commit on the topic branch being added to the history of the default branch, a squash merge adds all the file changes to a single new commit on the default branch.
Incorrect:
* Rebasing is the process of moving or combining a sequence of commits to a new base commit. Rebasing is most useful and easily visualized in the context of a feature branching workflow. The general process can be visualized as the following:

From a content perspective, rebasing is changing the base of your branch from one commit to another making it appear as if you'd created your branch from a different commit. Internally, Git accomplishes this by creating new commits and applying them to the specified base. It's very important to understand that even though the branch looks the same, it's composed of entirely new commits.
* To combine two separate Git repositories into one, add the repository to merge in as a remote to the repository to merge into. Then, combine their histories by merging while using the --allow-unrelated-histories command line option.


Reference:

https://learn.microsoft.com/en-us/azure/devops/repos/git/merging-with-squash https://jeffkreeftmeijer.com/git-combine/



You are integrating an Azure Boards project and a GitHub repository.
You need to authenticate Azure Boards to GitHub.
Which two authentication methods can you use? Each correct answer presents a complete solution.
Note: Each correct selection is worth one point.

  1. a publisher certificate
  2. a trusted root certificate
  3. Microsoft Entra ID
  4. GitHub user credentials
  5. a personal access token (PAT)

Answer(s): D,E

Explanation:

Connect Azure Boards to GitHub (Cloud), Authentication options
The following authentication options are supported based on the GitHub platform you want to connect to.
* GitHub.com
GitHub.com user account (Recommended)
Personal access token (PAT)
OAuth (preferred, registration required)
* GitHub Enterprise Server
PAT
Username plus password


Reference:

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



SIMULATION
You need to ensure that the maximum file size for all the Azure DevOps repositories of Project-12345678 is 2 MB.

  1. See Explanation section for answer.

Answer(s): A

Explanation:

See explanation below.


To set a maximum file size limit for all repositories within an Azure DevOps project, you use the Project Settings portal to configure a project-level repository policy.
Steps to Set Project-Wide File Size Limits
Step 1: Navigate to your project in the Azure DevOps portal.
1. Open Project Settings
Step 2: Click on Project settings (the gear icon) in the bottom-left corner of the sidebar. [Select Project-12345678]
Step 3: Under the Repos section on the left menu, select Repositories.
2. Access Repository Policies
Step 4: Ensure you have the All Repositories node selected at the top of the middle pane (do not select a specific individual repository yet if you want this to apply to all).
Step 5: Click on the Policies tab in the main window
3. Enable Maximum File Size Policy
Step 6: Scroll down to the Repository Policies section.
Step 7: Find the Maximum file size policy.
Step 8: Toggle the switch to On
Step 9: Enter the desired maximum size in MB. [Here 2 MB]
4. Set the Specific Limit
Common allowed values are typically 1, 2, 5, 10, 50, 100, or 200 MB.
Once enabled, Azure DevOps will block any git push containing a new or updated file that exceeds this limit


Reference:

https://learn.microsoft.com/en-us/azure/devops/repos/git/repository-settings



You have a GitHub repository that is integrated with Azure Boards. Azure Boards has a work item that has the number 715.
You need to ensure that when you commit source code in GitHub, the work item is updated automatically.
What should you include in the commit comments?

  1. the URL of the work item
  2. AB#715
  3. @715
  4. #715

Answer(s): B

Explanation:

Link GitHub commits, pull requests, and issues to work items in Azure Boards
Use AB# mention 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 will link to work item ID 125.


Reference:

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



You have an Azure DevOps organization that contains a project named Project1.
You need to create a published wiki in Project1.
What should you do first?

  1. In Project1, create an Azure DevOps pipeline.
  2. Modify the Team configuration settings of Project1.
  3. Modify the Storage settings of Project1.
  4. In Project1, create an Azure DevOps repository

Answer(s): D

Explanation:

Azure DevOps, Create a wiki for your project
Create a wiki Git repository
Create a new Git repository that stores all your wiki pages and related artifacts. From the wiki landing page, select Create Project wiki. Even if you use TFVC for source control, you can create a wiki with a Git repository.


Reference:

https://learn.microsoft.com/en-us/azure/devops/project/wiki/wiki-create-repo



Viewing page 37 of 81
Viewing questions 181 - 185 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!