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.
Q.1 – Solution: You implement a pull request strategy that uses fast-forward merges.
Does this meet the goal?
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://devblogs.microsoft.com/devops/pull-requests-with-rebase/
Q.2 – Solution: You implement a pull request strategy that uses squash merges.
Does this meet the goal?
Does this meet the goal?
A. Yes
B. No
Correct Answer: A
Q.3 – Solution: You implement a pull request strategy that uses an explicit merge.
Does this meet the goal?
Does this meet the goal?
A. Yes
B. No
Correct Answer: B
Q.4 – Solution: You implement a pull request strategy that uses a three-way merge.
Does this meet the goal?
Does this meet the goal?
A. Yes
B. No
Correct Answer: B