Question 150
At the Juniperford cloud operations center, designers commit large binary datasets directly into Git and every clone becomes slow. Which issue is most directly indicated by the facts?
Explanation
Correct Answer
The situation indicates that ordinary Git retains complete binary history and can expand clone sizes substantially. The recommended response is to store large tracked binaries using Git LFS and keep lightweight pointers in repository history, with a follow-up check that fresh clones fetch pointers and approved binary objects without downloading every historical version. This directly addresses the reported issue at the Juniperford cloud operations center.
Incorrect Answers
Unverified external copies may not match the last approved configuration or dependent changes. This can occur in other projects, but it is not the primary explanation at the Juniperford cloud operations center.
This explanation belongs to codeowners required review. The immediate weakness in the question is that ordinary Git retains complete binary history and can expand clone sizes substantially. For the Juniperford cloud operations center, the priority is to store large tracked binaries using Git LFS and keep lightweight pointers in repository history.
Although direct pushes bypass independent checks and may introduce untested production changes, the situation does not describe that specific cause; it instead indicates that ordinary Git retains complete binary history and can expand clone sizes substantially. For the Juniperford cloud operations center, the priority is to store large tracked binaries using Git LFS and keep lightweight pointers in repository history.