AZ-400 Practice Question: Design and implement a source control strategy
Which TWO options are benefits of using Git LFS (Large File Storage) in a team environment? (Select TWO.)
⚠ Common exam trap
Many exam-takers assume Git LFS automatically handles all binary files (Option B) or that it works only with specific platforms (Option D), when in fact it requires explicit configuration and is widely supported across providers.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Prevents large files from being stored in the Git history
Git LFS replaces large files in the repository with text pointer files, while the actual file content is stored in a separate remote store. This prevents the large files from bloating the Git history, which would otherwise permanently increase repository size for all clones and fetches.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Prevents large files from being stored in the Git history
Why this is correct
LFS replaces large files with small text pointers in the repository, while the actual binary content is stored in a separate external store. This keeps the Git history lightweight and avoids bloating the .git directory with large objects.
- ✗
Automatically detects and tracks all binary files in the repository
Why it's wrong here
LFS requires explicit configuration via .gitattributes patterns to specify which files or file types should be tracked; it does not automatically detect binary files. Without these rules, Git continues to store binary files as regular blobs, so manual tracking setup is necessary.
- ✓
Reduces the size of Git repository clones and fetches for team members
Why this is correct
Because the repository stores only pointer files, clones and fetches download these small references instead of the large binaries. The actual file content is retrieved on demand, significantly reducing the initial transfer size and speeding up team collaboration.
- ✗
Works only with GitHub and Azure Repos
Why it's wrong here
LFS is supported by a wide range of Git hosting services beyond GitHub and Azure Repos, including Bitbucket, GitLab, and self-hosted Git servers. It relies on a standard LFS API that any compatible server can implement, so it is not limited to those two platforms.
- ✗
Eliminates the need for Git when working with large binary files
Why it's wrong here
LFS is a Git extension that integrates with the existing Git workflow rather than replacing Git. It still uses Git for versioning, branching, and history; it only offloads the storage of large binary blobs to an external backend, so Git remains essential for repository management.
Go deeper
Related to this question
Learn chapter
Managing Infrastructure as Code Using Azure
Key term
Git
Git is a version control system that tracks changes to files so multiple people can work on the same project without overwriting each other's work.
Key term
Repository
A repository is a central storage location where software packages, code, or configuration files are kept, managed, and distributed for use by IT systems.
About these practice questions
This AZ-400 question is part of Courseiva's 823-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.