Microsoft Microsoft Certifications AZ-400 Questions & Answers

• Question 421:

  You are developing an application. The application source has multiple branches.

  You make several changes to a branch used for experimentation.

  You need to update the main branch to capture the changes made to the experimentation branch and override the history of the Git repository.

  Which Git option should you use?

  A. Rebase

  B. Fetch

  C. Merge

  D. Push

  Correct Answer: C

  Create pull requests to review and merge code in a Git project. Pull requests let your team review code and give feedback on changes before merging it into the master branch. Incorrect Answers:

  A: Use rebase to address the problem of updating your branch with the latest changes from the main branch. Rebase takes the changes made in the commits in your current branch and replays them on the history of another branch. The commit history of your current branch will be rewritten so that it starts from the most recent commit in the target branch of the rebase. Rebasing your changes in your feature branch off the latest changes in the main branch lets you test your changes on the most recent version in the main branch while keeping a clean Git history.

  D: Share changes made in commits and branches using the push command. Push your branches to the remote repository. Git adds your commits to an existing branch on the remote or creates a new branch with the same commits as your local branch.

  Reference: https://docs.microsoft.com/en-us/azure/devops/repos/git/pull-requests

• Question 422:

  Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while

  others might not have a correct solution.

  After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

  Your company uses Azure DevOps to manage the build and release processes for applications.

  You use a Git repository for applications source control.

  You need to implement a pull request strategy that reduces the history volume in the master branch.

  Solution: You implement a pull request strategy that uses a three-way merge.

  Does this meet the goal?

  A. Yes

  B. No

  Correct Answer: B

  Instead use fast-forward merge.

  Note:

  No fast-forward merge - This option merges the commit history of the source branch when the pull request closes and creates a merge commit in the target branch.

  Reference:

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

• Question 423:

  Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while

  others might not have a correct solution.

  After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

  Your company uses Azure DevOps to manage the build and release processes for applications.

  You use a Git repository for applications source control.

  You need to implement a pull request strategy that reduces the history volume in the master branch.

  Solution: You implement a pull request strategy that uses squash merges.

  Does this meet the goal?

  A. Yes

  B. No

  Correct Answer: A

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

• Question 424:

  Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while

  others might not have a correct solution.

  After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

  Your company uses Azure DevOps to manage the build and release processes for applications.

  You use a Git repository for applications source control.

  You need to implement a pull request strategy that reduces the history volume in the master branch.

  Solution: You implement a pull request strategy that uses an explicit merge.

  Does this meet the goal?

  A. Yes

  B. No

  Correct Answer: B

  Instead use fast-forward merge.

  Note:

  No fast-forward merge - This option merges the commit history of the source branch when the pull request closes and creates a merge commit in the target branch.

  Reference:

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

• Question 425:

  Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while

  others might not have a correct solution.

  After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

  Your company uses Azure DevOps to manage the build and release processes for applications.

  You use a Git repository for applications source control.

  You need to implement a pull request strategy that reduces the history volume in the master branch.

  Solution: You implement a pull request strategy that uses fast-forward merges.

  Does this meet the goal?

  A. Yes

  B. No

  Correct Answer: B

  No fast-forward merge - This option merges the commit history of the source branch when the pull request closes and creates a merge commit in the target branch.

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

• Question 426:

  Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while

  others might not have a correct solution.

  After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

  You plan to update the Azure DevOps strategy of your company.

  You need to identify the following issues as they occur during the company's development process:

  1.

  Licensing violations

  2.

  Prohibited libraries

  Solution: You implement pre-deployment gates.

  Does this meet the goal?

  A. Yes

  B. No

  Correct Answer: B

  Instead use implement continuous integration.

  Note: WhiteSource is the leader in continuous open source software security and compliance management. WhiteSource integrates into your build process, irrespective of your programming languages, build tools, or development

  environments. It works automatically, continuously, and silently in the background, checking the security, licensing, and quality of your open source components against WhiteSource constantly-updated definitive database of open source

  repositories.

  Reference:

  https://azuredevopslabs.com/labs/vstsextend/whitesource/

• Question 427:

  Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while

  others might not have a correct solution.

  After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

  You plan to update the Azure DevOps strategy of your company.

  You need to identify the following issues as they occur during the company's development process:

  1.

  Licensing violations

  2.

  Prohibited libraries

  Solution: You implement continuous integration.

  Does this meet the goal?

  A. Yes

  B. No

  Correct Answer: B

  WhiteSource is the leader in continuous open source software security and compliance management. WhiteSource integrates into your build process, irrespective of your programming languages, build tools, or development environments. It works automatically, continuously, and silently in the background, checking the security, licensing, and quality of your open source components against WhiteSource constantly-updated definitive database of open source repositories.

  Reference: https://azuredevopslabs.com/labs/vstsextend/whitesource/

• Question 428:

  Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while

  others might not have a correct solution.

  After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

  You plan to update the Azure DevOps strategy of your company.

  You need to identify the following issues as they occur during the company's development process:

  1.

  Licensing violations

  2.

  Prohibited libraries

  Solution: You implement automated security testing.

  Does this meet the goal?

  A. Yes

  B. No

  Correct Answer: B

  Instead use implement continuous integration.

  Note: WhiteSource is the leader in continuous open source software security and compliance management. WhiteSource integrates into your build process, irrespective of your programming languages, build tools, or development environments. It works automatically, continuously, and silently in the background, checking the security, licensing, and quality of your open source components against WhiteSource constantly-updated definitive database of open source repositories.

  Reference: https://azuredevopslabs.com/labs/vstsextend/whitesource/

• Question 429:

  You use a Git repository in Azure Repos to manage the source code of a web application. Developers commit changes directly to the master branch. You need to implement a change management procedure that meets the following requirements:

  1.

  The master branch must be protected, and new changes must be built in the feature branches first.

  2.

  Changes must be reviewed and approved by at least one release manager before each merge.

  3.

  Changes must be brought into the master branch by using pull requests. What should you configure in Azure Repos?

  A. branch policies of the master branch

  B. Services in Project Settings

  C. Deployment pools in Project Settings

  D. branch security of the master branch

  Correct Answer: A

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

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

• Question 430:

  Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while

  others might not have a correct solution.

  After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

  Your company has a project in Azure DevOps for a new web application.

  You need to ensure that when code is checked in, a build runs automatically.

  Solution: From the Continuous deployment trigger settings of the release pipeline, you enable the Pull request trigger setting.

  Does this meet the goal?

  A. Yes

  B. No

  Correct Answer: B

  Instead, In Visual Designer you enable continuous integration (CI) by:

  1.

  Select the Triggers tab.

  2.

  Enable Continuous integration.

  Reference: https://docs.microsoft.com/en-us/azure/devops/pipelines/get-started-designer