1 / 5
Fill in: 'We ___ build artifacts across CI runs so unchanged modules don't recompile.'
-
-
-
-
We 'cache artifacts' — the standard, simple collocation. The other options are less idiomatic here.
2 / 5
Fill in: 'A poorly scoped cache key can ___ stale build output into an unrelated branch.'
-
-
-
-
We say a bad cache key will 'leak' stale output — the standard collocation for unwanted cross-contamination. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ cache hit rates to confirm the change actually sped up builds.'
-
-
-
-
We 'track hit rates' — the standard collocation for monitoring cache effectiveness. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ the cache key on the lockfile hash so dependency changes invalidate it automatically.'
-
-
-
-
We 'base' a key on a hash — the standard collocation for deriving a cache key from content. The other options aren't idiomatic here.
5 / 5
Fill in: 'We ___ the cache manually whenever a build starts producing suspicious output.'
-
-
-
-
We 'clear' a cache — the standard, simple collocation for resetting it. The other options are less idiomatic here.