You need to commit a 3 GB ZIP file (VM images used for testing) to Git so that the file is versioned and associated with the corresponding code commits. Which two actions should you take? (Select two.)

Committing large binary files like a 3 GB ZIP directly to Git is problematic because Git is optimized for small text files and stores a complete history of every change, leading to repository bloat and slow operations. Git LFS (Large File Storage) is designed to handle large files by storing pointers to them in the Git repository while the actual file content is stored on a remote server. This keeps the Git repository small and manageable, making it the correct choice for versioning large files within a Git workflow. Alternatively, storing the large ZIP file in Azure Storage and enabling blob versions allows for version control of the file outside of Git. This approach is suitable when the file doesn't need to be tightly coupled with the Git repository's commit history but still requires versioning. git-fat is an older, less maintained alternative to Git LFS. git-stash is for temporarily saving changes, not for managing large files. GZip compression doesn't fundamentally change how Git handles the file's size in the repository.