A company's monorepo has a very large history and thousands of branches, which makes clones and routine fetches slow on developer Windows machines. Which Microsoft-developed tooling improves this without splitting the repository?
Show answer and explanation
Answer: B
Scalar is Microsoft's tool for very large Git repositories. It enables features such as partial clone, background fetch and scheduled maintenance, which cut clone time and reduce disk usage. It is now part of Git itself as the scalar command. Deleting local history breaks Git operations and loses the commit record. A centralized system abandons the distributed model without solving the performance problem. Splitting into many repositories is a structural change that fragments ownership and tooling when a tool addresses performance directly.
Why the other options are wrong
- A. Removing the history folder corrupts the repository from Git's point of view and eliminates the commit record. The clone becomes unusable for normal branching work.
- C. Centralized checkout systems do not address Git clone performance. They replace the distributed model and its offline workflows without speeding up the repository itself.
- D. Splitting into many repositories is a large structural change that scatters code ownership and tooling. It is unnecessary when a supported tool addresses performance directly.