AZ400-Q: handle large binary assets
A repository contains large design binaries committed repeatedly to normal Git history. Clone and CI checkout times are growing. Future binary changes must remain versioned without continuing to bloat normal Git objects. What should the team use?
- A) Rename the binaries with a
.txtextension. - B) Put the binaries in a pipeline variable group.
- C) Add more pull-request reviewers.
- D) Adopt Git LFS for eligible future binary assets and plan a separate history-remediation process for existing large blobs. ✓
Answer: D. Git LFS stores eligible large content outside ordinary Git object history. Existing history needs a deliberate migration/remediation plan; merely adding LFS patterns does not rewrite it.
Why not the others: Filename changes and reviews do not change object storage. Variable groups are not source control for binaries.