Microsoft DevOps Engineer Expert AZ-400 Practice Question

Your team's Azure Repos Git repository contains several years of history in which artists committed *.png and *.fbx game-asset files that are typically 200-400 MB each. Cloning the repo now takes more than 30 minutes and CI pipelines routinely exceed the 5 GB checkout limit. You must migrate the existing objects to Git Large File Storage (LFS) so that only lightweight pointer files remain in regular Git history, while preserving commit metadata. Which approach meets the goal with the least manual effort?

  • Run git lfs track ".png" ".fbx", commit the updated .gitattributes file, and push the branch normally.

  • Enable the Large File Checkout option in Azure Repos and perform git gc to prune existing large blobs.

  • Use git filter-branch with a tree-filter that calls git lfs track for each commit, then push the result to origin.

  • Install Git LFS locally, then execute git lfs migrate import --include=".png,.fbx" --include-ref=refs/heads/*; afterward push the rewritten history with git push --force-with-lease --all && git push --force-with-lease --tags.

Microsoft DevOps Engineer Expert AZ-400
Design and implement a source control strategy
Your Score:
Settings & Objectives
Random Mixed
Questions are selected randomly from all chosen topics, with a preference for those you haven’t seen before. You may see several questions from the same objective or domain in a row.
Rotate by Objective
Questions cycle through each objective or domain in turn, helping you avoid long streaks of questions from the same area. You may see some repeat questions, but the distribution will be more balanced across topics.

Check or uncheck an objective to set which questions you will receive.

Bash, the Crucial Exams Chat Bot
AI Bot