Exam 200-901 topic 1 question 10 discussion

What's wrong with "C. prevents over-writing code or configuration files"?

I think its A. You cannot completely prevent over-writing files in Git. It can be rolled back through but you can still overwrite existing files with a commit. So this is not completely preventable. Therefore A. It does facilitate with merging (although in some cases human intervention required if 2 people working on the same file and conflicts are there - git will notify when that's required)

A is correct. [..] If you have a team of developers working on a project, all writing new code or changing previously written code, losing those files could set you back weeks or months. Version control can protect your code by allowing changes to be checked in (through a process known as a code commit) to a hierarchical tree structure of folders with files in them. You often don’t know what a developer might need to change or has changed, but the version control system does. Each check-in is tagged with who made the change and what the person changed within the code. Instead of using inefficient techniques such as file locking, a version control system handles concurrent check-ins, allowing two programmers to commit code at the same time. [..] Another aspect of a version control system is the ability to branch and merge code built independently. This is very useful if you are writing code on a part of an application that could conflict with another part written by another team. Page 170 CCNA DevNet (DEVASC) - 200-901

Benefits of version control systems. Using version control software is a best practice for high performing software and DevOps teams. Version control also helps developers move faster and allows software teams to preserve efficiency and agility as the team scales to include more developers.

It should be A