Microsoft Microsoft Certifications AZ-400 Questions & Answers

• Question 211:

  You manage a project by using Azure Boards. You manage the project code by using GitHub.

  You have three work items that have IDs of 456, 457, and 458.

  You need to create a pull request that will be linked to all the work items. The solution must set the state of work item 456 to done.

  What should you add to the commit message?

  A. Done #456, #457, #458

  B. #AB456, #AB457, #AB458

  C. #456, #457, #458 Completed #456

  D. #AB456, #AB457, #AB458 Completed #AB456

  Correct Answer: D

  Use the #AB{id} syntax for the work items.

  Use Completed #AB456 to set the state of work item 456 to done.

  Note: 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.

  You can also enter a commit or pull request message to transition the work item. The system will recognize fix, fixes, fixed and apply it to the #-mention item that follows.

  Example:

  Fixes AB#123, AB#124, and AB#126

  Links to Azure Boards work items 123, 124, and 126. Transitions only the first item, 123 to the Resolved workflow state category or, if none is defined, then the Completed workflow state category.

  Incorrect:

  Not A: Must use the AB#{ID} format to link to work items. #456 links to an issue. Done keyword not recognized.

  Not B: Use Completed #AB456 to set the state of work item 456 to done.

  Not C: Must use the AB#{ID} format to link to work items.

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

• Question 212:

  You are creating a dashboard in Azure Boards.

  You need to visualize the time from when work starts on a work item until the work item is closed.

  Which type of widget should you use?

  A. cycle time

  B. velocity

  C. cumulative flow

  D. lead time

  Correct Answer: A

  Both lead time and cycle time widgets are useful to teams. They both indicate how long it takes for work to flow through their development pipeline. Lead time measures the total time elapsed from the creation of work items to their completion. Cycle time measures the time it takes for your team to complete work items once they begin actively working on them.

  The following diagram illustrates how lead time differs from cycle time. Lead time is calculated from work item creation to entering a completed state. Cycle time is calculated from first entering an In Progress or Resolved state category to entering a Completed state category.

  Reference: https://learn.microsoft.com/en-us/azure/devops/report/dashboards/cycle-time-and-lead-time

• Question 213:

  You manage a project by using Azure Boards. You manage the project code by using GitHub.

  You have three work items that have IDs of 456, 457, and 458.

  You need to create a pull request that will be linked to all the work items. The solution must set the state of work item 456 to done.

  What should you add to the commit message?

  A. Fixes #456, #457, #458

  B. Fixes #AB456, #AB457, #AB458

  C. #456, #457, #458Completed #456

  D. #AB456, #AB457, #AB458

  Correct Answer: B

  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.

  You can also enter a commit or pull request message to transition the work item. The system will recognize fix, fixes, fixed and apply it to the #-mention item that follows.

  Example:

  Fixes AB#123, AB#124, and AB#126 Links to Azure Boards work items 123, 124, and 126. Transitions only the first item, 123 to the Resolved workflow state category or, if none is defined, then the Completed workflow state category.

  Reference:

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

• Question 214:

  You use Git for source control.

  You need to commit a 3-GB ZIP file that contains virtual machines used for testing. The solution must meet the following requirements:

  1.

  The file must be versioned.

  2.

  The file must be associated with the corresponding code commits.

  Which two actions should you include in the solution? Each correct answer presents part of the solution.

  NOTE: Each correct selection is worth one point.

  A. Install the git-fat extension and associate the extension to ZIP files.

  B. Install the Git LFS extension and associate the extension to ZIP files.

  C. Install the git-stash extension and associate the extension to ZIP files.

  D. Use GZip to compress the file before committing the file.

  E. Store files in Azure Storage and enable blob versions.

  Correct Answer: BE

  Reference: https://github.com/jedbrown/git-fat https://git-lfs.com/

  https://learn.microsoft.com/en-us/azure/storage/blobs/versioning-overview https://www.learnthecontent.com/exam/azure/az-400-designing-and-implementing-microsoft-devops-solutions-2/s/Design-a-strategy-for-managing-large-files-including-Git-LFS-and-git-fat

• Question 215:

  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.

  A. a publisher certificate

  B. a trusted root certificate

  C. Microsoft Azure Active Directory (Azure AD), part of Microsoft Entra

  D. GitHub user credentials

  E. a personal access token (PAT)

  Correct Answer: DE

  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

• Question 216:

  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?

  A. the URL of the work item

  B. AB#715

  C. @715

  D. #715

  Correct Answer: B

  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

• Question 217:

  You use GitHub for source control.

  You are evaluating whether to use proxying to add a private upstream MyGet package feed to your MyGet feed.

  What are two possible advantages of this approach? Each correct answer presents a complete solution.

  NOTE: Each correct selection is worth one point.

  A. minimizes the impact of upstream source availability issues

  B. minimizes latency when accessing the package

  C. provides automatic authentication

  D. minimizes the impact on your storage quota

  Correct Answer: AC

  Reference: https://github.com/maartenba/myget-documentation/blob/master/how-to/working-with-upstream-package-sources.md

• Question 218:

  You manage source code control and versioning by using GitHub.

  A large file is committed to a repository accidentally.

  You need to reduce the size of the repository. The solution must remove the file from the repository.

  What should you use?

  A. bfg

  B. lfs

  C. gvfs

  D. init

  Correct Answer: A

  If you commit sensitive data, such as a password or SSH key into a Git repository, you can remove it from the history. To entirely remove unwanted files from a repository's history you can use either the git filter-repo tool or the BFG Repo-Cleaner open source tool.

  The git filter-repo tool and the BFG Repo-Cleaner rewrite your repository's history, which changes the SHAs for existing commits that you alter and any dependent commits. Changed commit SHAs may affect open pull requests in your repository. We recommend merging or closing all open pull requests before removing files from your repository.

  Incorrect:

  * gvfs

  What is GVFS?

  GVFS stands for Git Virtual File System. GVFS virtualizes the file system beneath your git repo so that git and all tools see what appears to be a normal repo, but GVFS only downloads objects as they are needed. GVFS also manages git's

  sparse-checkout to ensure that git operations like status, checkout, etc., can be as quick as possible because they will only consider the files that the user has accessed, not all files in the repo.

  Reference:

  https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository

  https://github.com/SpiremtSCM/GVFS

• Question 219:

  You have a project in Azure DevOps.

  You need to implement a new branching solution. The solution must ensure that all pull requests meet the following requirements:

  1.

  Include linked work items.

  2.

  Pass build validation policies.

  3.

  Require at least three reviewers. What should you include in the solution?

  A. branch policies

  B. pull request templates

  C. branch security

  D. pull request permissions

  Correct Answer: A

  Branch policies help teams protect their important branches of development. Policies enforce your team's code quality and change management standards. Configure branch policies

  *

  Check for linked work items

  For work item management tracking, you can require associations between PRs and work items. Linking work items provides more context for changes, and ensures that updates go through your work item tracking process.

  *

  Build validation

  You can set a policy requiring PR changes to build successfully before the PR can complete. Build policies reduce breaks and keep your test results passing. Build policies help even if you're using continuous integration (CI) on your

  development branches to catch problems early.

  A build validation policy queues a new build when a new PR is created or changes are pushed to an existing PR that targets the branch. The build policy evaluates the build results to determine whether the PR can be completed.

  *

  Require a minimum number of reviewers

  Code reviews are important for software development projects. To ensure that teams review and approve PRs, you can require approval from a minimum number of reviewers. The basic policy requires that a specified number of reviewers

  approve the code, with no rejections.

  *

  Etc.

  Reference:

  https://learn.microsoft.com/en-us/azure/devops/repos/git/branch-policies

• Question 220:

  You have a GitHub repository.

  You need to ensure that all the code in the repository is scanned for vulnerabilities.

  What should you use?

  A. Dependabot alerts

  B. branch protection rules

  C. CodeQL actions

  D. GitHub Advisory Database databases

  Correct Answer: C

  Reference: https://github.blog/2022-04-22-5-simple-things-every-developer-can-do-to-ship-more-secure-code/#:~:text=Dependabot%20is%20complementary%20to%20CodeQL,for%20package%20registries%20and%20dependencies.