AZ-400 Question 76
Select 2Your development team maintains a large Git repository in Azure DevOps that includes multiple gigabytes of binary media files. The repository size has ballooned, causing slow cloning and performance issues. Due to corporate firewall restrictions, Git Large File Storage (LFS) may not be fully supported in your environment. Which two actions should you take to manage large files while minimizing repository size and maintaining version control?
- A
Enable Git LFS and configure .gitattributes to track binary file types
- B
Commit large files directly within the standard Git repository
- C
Remove existing large files from history and compress them with a third-party zip tool
- D
Evaluate and configure an alternative like git-fat if Git LFS is not viable
Show answer and explanation
Correct answers: A, D
Explanation
Storing large files natively in Git leads to cumbersome repository sizes and performance bottlenecks. Git LFS or git-fat allows large binaries to be stored externally, with only references residing in the repository, reducing its overall size and speeding up operations. For more guidance, refer to the official Git LFS documentation and community resources on large-file management in Git.
- A. Correct.
Git LFS allows you to store large files outside your main repository, significantly reducing clone and fetch times. You configure which file extensions LFS should track by adding them to .gitattributes, ensuring those files go through the LFS process rather than directly into Git history.
- B. Incorrect.
Committing large files directly into Git bloats the repository and causes performance issues when cloning or fetching. This approach is the root cause of the current problem.
- C. Incorrect.
While compressing files before committing might slightly reduce file sizes, it does not solve the fundamental issue of storing large binary data in Git. Once these compressed archives are still part of the repository� history, they will continue to inflate its size.
- D. Correct.
git-fat is an alternative to Git LFS that can help manage large assets similarly by storing them externally and tracking references in the repository. If you cannot use Git LFS due to firewall or corporate policy restrictions, git-fat offers a workable approach to manage large files.