Git LFS for large files - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Git LFS track command effect

What is the output or effect after running git lfs track "*.psd" in a Git repository?

Git

git lfs track "*.psd"

A Removes all .psd files from the repository history

B Disables Git LFS tracking for .psd files

C Immediately uploads all existing .psd files to the remote Git LFS server

D Adds an entry to .gitattributes file to track all .psd files with Git LFS

💡 Hint

Think about what the track command does to file patterns in Git LFS.

The git lfs track command adds a pattern to the .gitattributes file. This tells Git to use Git LFS for matching files in future commits. It does not upload files immediately or remove files from history.

❓ Troubleshoot

intermediate

Git LFS push error diagnosis

You run git push origin main after adding large files tracked by Git LFS, but get an error: batch request: This repository is over its data quota. What is the most likely cause?

A You have exceeded the storage or bandwidth limits of your Git LFS hosting service

B The remote repository URL is incorrect

C You forgot to run <code>git lfs install</code> before pushing

D Your Git LFS client is outdated and cannot push files

💡 Hint

Consider what 'over its data quota' means in hosting services.

This error means the Git LFS storage or bandwidth quota on the hosting service (like GitHub) has been exceeded. You need to upgrade your plan or reduce usage.

❓ Configuration

advanced

Configuring Git LFS for a new repository

Which sequence of commands correctly sets up Git LFS tracking for all .zip files and commits the configuration?

A

git lfs install
git lfs track "*.zip"
git add .gitattributes
git commit -m "Track zip files with Git LFS"

B

git lfs track "*.zip"
git add .gitattributes
git commit -m "Track zip files with Git LFS"
git lfs install

C

git add .gitattributes
git lfs install
git lfs track "*.zip"
git commit -m "Track zip files with Git LFS"

D

git lfs install
git add .gitattributes
git lfs track "*.zip"
git commit -m "Track zip files with Git LFS"

💡 Hint

Remember the order: install Git LFS first, then track, then add and commit.

You must first run git lfs install to set up Git LFS hooks. Then track the file pattern, add the .gitattributes file, and commit it.

✅ Best Practice

advanced

Best practice for storing large files in Git

Which practice is best when working with large binary files in a Git repository?

A Commit large binary files directly to the Git repository without Git LFS

B Use Git LFS to store large binary files outside the main Git history

C Compress large files manually and commit the compressed versions without Git LFS

D Store large files in a separate branch within the same repository

💡 Hint

Think about how Git handles large files and history size.

Git LFS is designed to handle large binary files efficiently by storing them outside the main Git history, reducing repository size and improving performance.

🔀 Workflow

expert

Git LFS file retrieval after clone

After cloning a repository that uses Git LFS, what happens when you run git checkout main?

A Git LFS disables itself and large files remain as pointers in the working directory

B Git checkout fails because large files are missing and must be downloaded manually

C Git LFS downloads the actual large files referenced by pointers automatically during checkout

D Git replaces large files with empty placeholders and requires manual download commands

💡 Hint

Consider how Git LFS integrates with Git commands after cloning.

When checking out a branch, Git LFS automatically downloads the real large files replacing the pointer files, so the working directory has the actual content.