Packfiles and compression in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Understanding git packfile creation

What is the output of the command git gc --aggressive --prune=now in a repository with many loose objects?

A It deletes all objects and resets the repository to an empty state.

B It compresses loose objects into packfiles and removes unreachable objects immediately.

C It creates packfiles but does not remove any loose objects.

D It only removes unreachable objects but does not create packfiles.

💡 Hint

Think about what aggressive garbage collection does in Git.

The git gc --aggressive --prune=now command compresses loose objects into packfiles and immediately removes unreachable objects, cleaning up the repository efficiently.

🧠 Conceptual

intermediate

Purpose of delta compression in Git packfiles

Why does Git use delta compression inside packfiles?

A To encrypt objects for security during transfer.

B To create backups of objects in case of corruption.

C To speed up network transfer by sending full copies of objects.

D To store only the differences between similar objects, reducing disk space usage.

💡 Hint

Think about how storing differences can save space.

Delta compression stores only the changes between similar objects, which reduces the size of packfiles and saves disk space.

❓ Troubleshoot

advanced

Diagnosing corrupted packfile error

You run git fsck and get an error about a corrupted packfile. Which command helps you safely rebuild packfiles to fix this?

A git reset --hard HEAD

B git clean -f -d

C git repack -a -d --window=50 --depth=50

D git checkout -- .

💡 Hint

Look for a command that repacks objects.

git repack rebuilds packfiles and can fix corruption by repacking all objects with specified options.

✅ Best Practice

advanced

Optimizing packfile compression for large repositories

Which approach is best to optimize packfile compression for a large repository with many similar files?

A Use <code>git gc --aggressive</code> periodically to maximize compression.

B Avoid using packfiles and keep all objects loose for faster access.

C Disable delta compression to speed up packfile creation.

D Manually delete packfiles to reduce disk usage.

💡 Hint

Aggressive garbage collection improves compression but takes more time.

Running git gc --aggressive compresses objects more thoroughly, which is ideal for large repositories with many similar files.

🔀 Workflow

expert

Sequence to safely reduce repository size using packfiles

What is the correct sequence of commands to safely reduce a Git repository size by compressing objects and removing unreachable data?

A 3,1,2,4

B 1,2,3,4

C 2,1,3,4

D 3,2,1,4

💡 Hint

Think about garbage collection first, then repacking, pruning, and finally checking.

First run git gc to clean and compress, then git repack -a -d to repack all objects, followed by git prune to remove unreachable objects, and finally git fsck to verify integrity.