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
Answer: B
Explanation:
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
Latest AZ-400 Dumps Valid Version with 289 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund