Question

A company is implementing Microsoft Dynamics 365 Sales. Several developers are working on a project at the same time. The company plans to control the code changes while the project is in development. The company requires that the history of the code changes must be retained for auditing purposes. Which solution should you use? a) Git b) TFS (Team Foundation Server) c) SVN (Subversion) d) Mercurial

Answer 1

The right solution for controlling the code changes and retaining the history for auditing purposes in a Microsoft Dynamics 365 Sales development environment among multiple developers would be a) Git. Option a is correct.

Step-by-step explanation:

Git is a distributed version control system that is very popular for tracking changes in source code during software development. Its features for coordinate work among programmers make it ideal for collaboration, and its data integrity and support for distributed, non-linear workflows are well-suited for a professional development environment.

All the listed options, including TFS (Team Foundation Server), SVN (Subversion), and Mercurial, are capable of version control. However, Git's robust branching capabilities, its distributed nature, and widespread adoption make it particularly suited for a scenario with many developers working on a project simultaneously.

Git also ensures a comprehensive change history is maintained, which is essential for auditing and understanding the evolution of the code base over time.

Option a is correct.