Distributed vs centralized version control in Git - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Key difference between distributed and centralized version control

Which statement best describes the main difference between distributed and centralized version control systems?

A Distributed systems store the full project history on each user's machine, while centralized systems keep history only on a central server.

B Centralized systems allow offline commits, but distributed systems require constant internet connection.

C Distributed systems do not support branching, whereas centralized systems do.

D Centralized systems automatically merge changes without conflicts, distributed systems require manual merging.

💡 Hint

Think about where the full project history is stored in each system.

Distributed version control systems like Git store the entire project history on every user's machine, enabling offline work and local commits. Centralized systems keep the history only on a central server, requiring network access for most operations.

💻 Command Output

intermediate

Output of git clone in distributed version control

What is the result of running git clone https://github.com/example/repo.git in a distributed version control system?

A The command fails because cloning requires a centralized server.

B A full copy of the repository, including all history, is downloaded to the local machine.

C Only the latest snapshot of files is downloaded without history.

D It creates a local branch but does not download any files.

💡 Hint

Consider what cloning means in Git.

In Git, cloning downloads the entire repository including all commits and history, enabling full offline work.

🔀 Workflow

advanced

Workflow difference in committing changes

Which workflow correctly describes committing changes in a distributed version control system like Git compared to a centralized system?

A Both systems require commits to be made directly on the central server only.

B In centralized systems, commits are made locally and then pushed; in distributed systems, commits go directly to the server.

C In distributed systems, commits are made locally first and then pushed to a remote; in centralized systems, commits go directly to the server.

D Distributed systems do not support commits; they only support merges.

💡 Hint

Think about where commits are stored initially in each system.

Distributed systems allow local commits that are later pushed to a remote repository. Centralized systems require commits to be made directly on the central server.

❓ Troubleshoot

advanced

Resolving conflicts in distributed vs centralized systems

When two developers edit the same file simultaneously, how does conflict resolution differ between distributed and centralized version control systems?

A Distributed systems require manual merging after pulling changes; centralized systems often lock files to prevent conflicts.

B Centralized systems automatically merge conflicting changes; distributed systems discard one developer's changes.

C Distributed systems prevent conflicts by disallowing simultaneous edits; centralized systems allow conflicts freely.

D Both systems handle conflicts identically by automatically merging without user input.

💡 Hint

Consider how each system manages simultaneous edits and merging.

Distributed systems like Git require manual merging when conflicts occur after pulling changes. Centralized systems sometimes use file locking to avoid conflicts by preventing simultaneous edits.

✅ Best Practice

expert

Choosing version control for a remote team with unreliable internet

A remote team has unreliable internet connections. Which version control system type is best suited for their workflow and why?

A Centralized version control, because it ensures all changes are immediately saved on the central server.

B Distributed version control, because it prevents any conflicts by disallowing simultaneous edits.

C Centralized version control, because it requires less disk space on local machines.

D Distributed version control, because it allows local commits and offline work without needing constant server access.

💡 Hint

Think about how offline work is supported.

Distributed version control systems like Git allow developers to commit changes locally without internet access, making them ideal for teams with unreliable connections. Centralized systems require constant server access for commits.