Question 210
At the Eastbrook analytics division, after adding an external software supplier, a monorepo contains millions of files and full checkout slows every build worker. What is the primary reason this approach is unreliable?
Explanation
Correct Answer
This explanation matches the reported facts: full working-tree materialization can waste resources when a job needs only selected projects. A corrective test should establish that a clean build retrieves its required paths and produces the same tested output with reduced checkout time. This directly addresses the reported issue at the Eastbrook analytics division.
Incorrect Answers
That statement concerns signed commit policy; here the reported facts point to a different issue: full working-tree materialization can waste resources when a job needs only selected projects. For the Eastbrook analytics division, the priority is to use appropriate sparse checkout or Scalar/Git optimization for the workload without omitting required source.
Self-approval eliminates meaningful challenge for sensitive repository changes. This can occur in other projects, but it is not the primary explanation at the Eastbrook analytics division.
Although generic peer approval may not cover specialist risks in critical automation files, the situation does not describe that specific cause; it instead indicates that full working-tree materialization can waste resources when a job needs only selected projects. For the Eastbrook analytics division, the priority is to use appropriate sparse checkout or Scalar/Git optimization for the workload without omitting required source.