A team is currently working on a repository in Azure Repos for managing all of the source code. There are a high number of feature requests. That makes it difficult to follow the history of the changes to the master branch. You need to enforce a strategy that would Allows consolidation of all commit histories
Merge the changes into a single commit
You decide to implement the squash merge strategy. 
Would this fulfill the requirement?

Answer options:

A.Yes
B.No

Answer – A 
Yes, this would fulfill the desired requirement. The Microsoft documentation mentions the following. 

For more information on squash merge, please visit the below URL- 

https://docs.microsoft.com/en-us/azure/devops/repos/git/merging-with-squash?view=azure-devops