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?
Click on the arrows to vote for the correct answer
A. B.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.
https://docs.microsoft.com/en-us/azure/devops/repos/git/branch-policiesThe given scenario mentions that a pull request strategy needs to be implemented in order to reduce the history volume in the master branch of the Git repository used for source control in Azure DevOps.
The proposed solution is to implement a pull request strategy that uses an explicit merge. An explicit merge strategy involves merging the changes from a branch explicitly into another branch, usually the master branch in this case.
Now, whether this solution meets the goal or not depends on the specific requirements and constraints of the organization. An explicit merge can be an effective way to reduce the history volume in the master branch as it creates a new commit that includes all the changes from the pull request, without retaining the entire history of the pull request branch.
However, it is important to note that an explicit merge can also introduce conflicts and cause integration issues if multiple developers are working on the same codebase and branch simultaneously. Additionally, explicit merges can also make it difficult to trace the complete history of the codebase, as the history of the pull request branch is lost.
Therefore, the solution may or may not meet the goal depending on the specific requirements and constraints of the organization. It is important to carefully evaluate the benefits and drawbacks of using an explicit merge strategy for pull requests before implementing it in production.