Distributed vs centralized version control in Git - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to clone a remote Git repository to your local machine.

Git

git [1] https://github.com/user/repo.git

Drag options to blanks, or click blank then click option'

Aclone

Bmerge

Cpush

Dcommit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'commit' instead of 'clone'

Using 'push' which sends changes, not copies repo

The git clone command copies a remote repository to your local machine, creating a full copy including history. In distributed VCS like Git, every clone is a full backup; unlike centralized VCS like SVN.

2fill in blank

medium

Complete the command to send your local commits to the remote repository.

Git

git [1] origin main

Drag options to blanks, or click blank then click option'

Apush

Bfetch

Cclone

Dpull

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'fetch' or 'pull' which only download changes

Using 'clone' which copies repo

The git push command uploads your local commits to the remote repository, sharing your changes. In distributed systems, anyone can push to shared repos.

3fill in blank

hard

Complete the command to update your local repository with changes from remote.

Git

git [1] origin main

Drag options to blanks, or click blank then click option'

Acommit

Bpull

Cclone

Dpush

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'push' instead of 'pull'

Using 'clone' which copies repo instead of updating

The git pull command fetches and merges changes from the remote repository into your local branch. Equivalent to fetch + merge in Git's distributed model.

4fill in blank

hard

Fill both blanks to create a new branch and switch to it in Git.

Git

git [1] -b [2]

Drag options to blanks, or click blank then click option'

Acheckout

Bmain

Cfeature

Dcommit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'commit' instead of 'checkout'

Using 'main' as new branch name when 'feature' is intended

The command git checkout -b feature creates a new branch named 'feature' and switches to it. Branching is cheap and local in distributed Git, unlike centralized systems.

5fill in blank

hard

Fill all three blanks to push commits and set the upstream tracking branch, enabling easy future syncs in distributed Git.

Git

git [1] --set-upstream [2] [3]

Drag options to blanks, or click blank then click option'

Apush

Borigin

Cmain

Dpull

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pull' which fetches instead of pushes

Wrong remote/branch or omitting '--set-upstream'

The git push --set-upstream origin main (or git push -u origin main) pushes the branch and configures it to track the remote branch. This is essential in distributed version control for streamlined workflows without a central server dependency.

Practice

1. Which statement best describes distributed version control systems like Git?

easy

A. Changes are only saved on the server, not locally.

B. Each user has a full copy of the repository including history.

C. Users cannot work offline and must always connect to the server.

D. There is only one central server where all files are stored.

Solution

1. Step 1: Understand distributed version control

   Distributed systems like Git give every user a complete copy of the repository, including all history.

2. Step 2: Compare with centralized systems

   Centralized systems rely on one main server, unlike distributed ones where users work independently.

3. Final Answer:

   Each user has a full copy of the repository including history. -> Option B

4. Quick Check:

   Distributed = full local copy [OK]

Hint: Distributed means full local copy for each user [OK]

Common Mistakes:

• Confusing distributed with centralized control
• Thinking users must always connect to server
• Believing changes are only saved on server

2. Which of the following commands initializes a new Git repository locally?

easy

A. git clone https://example.com/repo.git

B. git commit -m 'start'

C. git push origin main

D. git init

Solution

1. Step 1: Identify command to create new repo

   The command git init creates a new local Git repository.

2. Step 2: Understand other commands

   git clone copies an existing repo; git commit saves changes; git push sends changes to remote.

3. Final Answer:

   git init -> Option D

4. Quick Check:

   Initialize repo = git init [OK]

Hint: Use git init to start a new local repo [OK]

Common Mistakes:

• Using git clone to create a new empty repo
• Confusing commit with init
• Trying to push before creating repo

3. Given a centralized version control system, what happens if the central server goes offline?

medium

A. Users cannot commit or update until the server is back online.

B. Users can continue working and commit locally without issues.

C. Users automatically get a full copy of the repo to work offline.

D. Users can push changes to a backup server automatically.

Solution

1. Step 1: Understand centralized system dependency

   Centralized systems depend on the main server for commits and updates.

2. Step 2: Effect of server downtime

   If the server is offline, users cannot commit or update until it returns.

3. Final Answer:

   Users cannot commit or update until the server is back online. -> Option A

4. Quick Check:

   Centralized needs server online [OK]

Hint: Centralized needs server online to commit [OK]

Common Mistakes:

• Assuming offline commits are possible in centralized systems
• Thinking users get full repo copies automatically
• Believing backup servers sync automatically

4. You cloned a Git repository but forgot to fetch the latest changes. Which command fixes this?

medium

A. git fetch origin

B. git clone --update

C. git push origin main

D. git init

Solution

1. Step 1: Identify command to update local repo

   git fetch origin downloads latest changes from remote without merging.

2. Step 2: Understand other commands

   git clone --update is invalid; git push sends changes; git init creates new repo.

3. Final Answer:

   git fetch origin -> Option A

4. Quick Check:

   Update local repo = git fetch [OK]

Hint: Use git fetch to get latest remote changes [OK]

Common Mistakes:

• Using git clone again instead of fetch
• Trying to push before fetching
• Running git init on existing repo

5. In a distributed version control system like Git, how can multiple users work on the same project without a central server?

hard

A. They cannot work without a central server in distributed systems.

B. They use a single shared folder on a network drive.

C. They share patches and merge changes manually between local repos.

D. They must push all changes to a cloud server immediately.

Solution

1. Step 1: Understand distributed collaboration

   In distributed systems, users have full repos and can share changes as patches or pull requests.

2. Step 2: How users share changes without central server

   They exchange patches or pull changes directly between local repositories manually or via other means.

3. Final Answer:

   They share patches and merge changes manually between local repos. -> Option C

4. Quick Check:

   Distributed = manual patch sharing possible [OK]

Hint: Distributed allows manual patch sharing without central server [OK]

Common Mistakes:

• Thinking distributed needs central server always
• Assuming network shared folder is standard practice
• Believing immediate cloud push is required