ExamTopics Logo
Mail Us[email protected]
Menu
Microsoft Discussions
exam questions

Exam AZ-400 All Questions

View all questions & answers for the AZ-400 exam
Go to Exam

Exam AZ-400 topic 5 question 50 discussion

Actual exam question from Microsoft's AZ-400
Question #: 50
Topic #: 5
[All AZ-400 Questions]

You use Git for source control.

You need to commit a 3-GB ZIP file that contains virtual machines used for testing. The solution must meet the following requirements:

• The file must be versioned.
• The file must be associated with the corresponding code commits.

Which two actions should you include in the solution? Each correct answer presents part of the solution.

NOTE: Each correct selection is worth one point.

  • A. Install the git-fat extension and associate the extension to ZIP files.
  • B. Install the Git LFS extension and associate the extension to ZIP files.
  • C. Install the git-stash extension and associate the extension to ZIP files.
  • D. Use GZip to compress the file before committing the file.
  • E. Store files in Azure Storage and enable blob versions.
Show Suggested Answer Hide Answer
Suggested Answer: BE 🗳️
by Rafi786_khan at Jan. 22, 2024, 8:20 a.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
Rafi786_khan
Highly Voted 1 year, 5 months ago
Answer: B & E Explanation: Git LFS (Large File Storage): This extension is specifically designed for handling large files within a Git repository. It stores the file contents in a separate backend (e.g., GitHub LFS servers), while only storing a pointer to the file within the Git repository itself. This significantly reduces the repository size and improves versioning performance. Associating the ZIP file extension with Git LFS ensures automatic handling of large files. Azure Storage with Blob Versions: This approach stores the actual 3GB ZIP file in Azure Storage, not the Git repository. By enabling blob versions, you maintain version history for the file, allowing you to revert to previous versions if needed. This solution keeps the Git repository lightweight while maintaining version control for the large file.
upvoted 11 times
zhshwx
1 year, 2 months ago
The question says Each correct answer presents part of the solution. Both B and E are complete solutions.
upvoted 1 times
...
...
Rkmylambton
Highly Voted 1 year, 5 months ago
It is not mentioned where we are going to save file. Github LFS Server or Azure Storage. I think B and D can be option.
upvoted 5 times
mcabrito
1 year, 4 months ago
I agree with you.
upvoted 2 times
...
...
dddddddddddww12
Most Recent 6 months, 2 weeks ago
Selected Answer: AB
The git-fat extension is a tool for managing large files in Git repositories by offloading their content to an external storage system while keeping lightweight references in the Git repository. This allows Git to manage large files more efficiently without bloating the repository size.
upvoted 2 times
...
UrbanRellik
1 year, 1 month ago
Selected Answer: BE
B to handle the large file E to handle the storage and versioning.
upvoted 2 times
Freyr
5 months, 3 weeks ago
I think, (E) is not going to be the answer because it is taking git out of the equation which we need as per the question.
upvoted 2 times
...
...
FeriAZ
1 year, 4 months ago
Selected Answer: BE
1. Install the Git LFS (Large File Storage) extension and associate the extension to ZIP files. Git LFS is designed specifically for handling large files in Git repositories. It stores the large file content (the 3-GB ZIP in this case) outside the main Git repository, typically on a server. Git LFS keeps track of the file using a pointer within the repository, ensuring versioning and association with the corresponding code commits. 2. Use GZip to compress the file before adding it to Git LFS. While not strictly necessary for Git LFS functionality, compressing the ZIP file with GZip can further reduce its size before storing it externally. This can optimize storage space and potentially reduce upload/download times.
upvoted 2 times
FeriAZ
1 year, 3 months ago
Number 2 i wrong. The correct explanation is in below: Store files in Azure Storage and enable blob versions (E): While Git LFS doesn't require a specific storage solution, using Azure Blob storage with enabled versioning aligns well with the requirements. Azure Blob storage provides a reliable and scalable location to store the actual content of the large file referenced by Git LFS. Enabling blob versions ensures that historical versions of the file are retained, matching the versioning requirement.
upvoted 1 times
...
...
mcabrito
1 year, 4 months ago
Selected Answer: BD
I believe the BD option is the right choice because at the beginning of the question, it states: 'You use Git for source control.' So, to me, it doesn't make sense to send the file to Azure Storage since it has no relation to Git whatsoever. I understand that it's an option for versioning the file, but in my opinion, this option doesn't align with the context of the question. Therefore, if this question appears on my exam, I will select options BD.
upvoted 3 times
p2006
8 months, 1 week ago
I agree, that is a key benefit of lfs, I think. "Same Git workflow Work like you always do on Git—no need for additional commands, secondary storage systems, or toolsets."
upvoted 1 times
...
...
TheMCT
1 year, 4 months ago
Selected Answer: BE
B & E, correct answer
upvoted 1 times
...
Tuki93
1 year, 5 months ago
https://learn.microsoft.com/en-us/azure/devops/repos/git/manage-large-files?view=azure-devops
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel