GH-900 practice question 15 of 15

A distributed version control system is best described as a system that:

Full set: 144 questions
Answer options
A: Relies on a central server to store the entire project history and allows developers to check out files for editing.
B: Stores project files on a cloud-based server and allows multiple developers to collaborate on the same codebase simultaneously.
C: Ensures each developer has their own local copy of the entire code repository, including the complete project history and metadata. Correct answer
D: Requires developers to manually track and manage different versions of their files using naming conventions and manual backups.
Correct Answer:
C. Ensures each developer has their own local copy of the entire code repository, including the complete project history and metadata.
Explanation

The defining characteristic of a Distributed Version Control System (DVCS), such as Git or Mercurial, is its decentralized architecture. Each developer clones a complete copy of the repository, which includes the entire history of all changes, branches, and metadata. This "full-fat" local copy allows developers to perform most operations—such as committing, viewing history, and creating branches—entirely offline. This contrasts sharply with centralized systems, where developers only have a working copy of the files and must connect to a central server to access the project's history or commit changes.

Why Incorrect

A. This describes a Centralized Version Control System (CVCS) like Subversion (SVN), where a single central server is the authoritative source for the project's history.
B. While DVCS often use cloud servers for collaboration (e.g., GitHub), this is a hosting implementation, not the core architectural principle that defines the system as distributed.
D. This describes the absence of a version control system, where versioning is done manually and is prone to error, which is the problem VCS is designed to solve.

References

1. Chacon, S., & Straub, B. (2014). Pro Git (2nd ed.). Apress. In Chapter 1.1, "About Version Control," the text explicitly contrasts DVCS with CVCS, stating: "In a DVCS... clients don’t just check out the latest snapshot of the files: they fully mirror the repository, including its full history. Thus, if any server dies... any of the client repositories can be copied back up to the server to restore it." This directly supports the concept in option C.

2. MIT Missing Semester. (2020). Lecture 6: Version Control (Git). MIT. The courseware explains, "With distributed version control systems, you have a full copy of the project’s history on your disk, so you can do many operations locally." This reinforces that each developer has a complete local repository. (See section on "Git's Data Model").

3. Loeliger, J., & McCullough, M. (2012). Version Control with Git (2nd ed.). O'Reilly Media. Chapter 1, "Introduction to Git," describes the architecture: "Git is a distributed version control system (DVCS). Instead of a single central repository that all users access, each user has his or her own repository, with the complete history of the project." (p. 6).

Scroll to Top