Git mental model (snapshots not diffs) - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does Git store changes internally?

Git is often described as storing snapshots rather than diffs. What does this mean?

A Git stores file changes as patches that must be applied manually.

B Git saves only the differences between files for each commit.

C Git stores only the latest file versions and discards history.

D Git saves the entire state of all files at each commit as a snapshot.

💡 Hint

Think about how Git can quickly restore any commit without applying patches.

Git stores a snapshot of the entire project at each commit. It does not save diffs but saves the full state efficiently by reusing unchanged files.

💻 Command Output

intermediate

What does 'git cat-file -p HEAD' show?

Run git cat-file -p HEAD in a repository. What output do you expect?

A The diff between the last two commits.

B The full snapshot of the latest commit's tree and metadata.

C The list of all branches in the repository.

D The current status of uncommitted changes.

💡 Hint

HEAD points to the latest commit object.

git cat-file -p HEAD shows the commit object pointed to by HEAD, including metadata and the tree snapshot.

🔀 Workflow

advanced

How does Git optimize storage of snapshots?

Git stores snapshots for each commit. How does it avoid storing duplicate file data repeatedly?

A Git stores identical files only once using object hashing and references.

B Git compresses all files into a single archive per commit.

C Git stores full copies of all files for every commit without optimization.

D Git deletes unchanged files from previous commits to save space.

💡 Hint

Think about how Git uses SHA-1 or SHA-256 hashes for objects.

Git uses content-addressable storage. Identical files have the same hash and are stored once, referenced by multiple commits.

❓ Troubleshoot

advanced

Why does 'git diff' show no output after a commit?

You just committed changes, but running git diff shows no output. Why?

A Because the commit was empty and did not change any files.

B Because Git lost track of the commit history.

C Because the working directory matches the latest commit snapshot exactly.

D Because the repository is corrupted and cannot show diffs.

💡 Hint

Think about what git diff compares by default.

git diff compares the working directory to the index or last commit. After committing, they match, so no diff appears.

✅ Best Practice

expert

Why prefer snapshots over diffs in Git's design?

Git uses snapshots instead of diffs internally. What is a key advantage of this design?

A It allows fast checkout and recovery by restoring complete file states directly.

B It reduces repository size more than storing diffs would.

C It makes merging changes impossible, simplifying history.

D It requires less CPU power to compute diffs on demand.

💡 Hint

Think about how Git restores files when switching commits.

Storing snapshots lets Git quickly restore any commit without applying a chain of diffs, improving speed and reliability.