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

Question

Options

• ARelies on a central server to store the entire project history and allows developers to check out
• BStores project files on a cloud-based server and allows multiple developers to collaborate on the
• CEnsures each developer has their own local copy of the entire code repository, including the
• DRequires developers to manually track and manage different versions of their files using naming

• A
  7% (3)
• B
  2% (1)
• C
  89% (41)
• D
  2% (1)

Explanation

A distributed version control system (DVCS), like Git, gives every developer a full local copy of the entire repository, including its complete history. This means developers can commit, branch, diff, and review history offline without needing a network connection. Option A describes a centralized VCS (e.g., SVN or CVS), where history lives only on a central server. Option B describes general cloud file storage, not a DVCS. Option D describes manual versioning (e.g., naming files 'v1', 'v2'), which is not a formal version control system at all.

No community discussion yet for this question.