1 / 5
Fill in: 'We ___ dependency installation into its own layer so it's cached across unrelated code changes.'
-
-
-
-
We 'isolate' a step into a layer — the standard collocation for separating it for cache reuse. The other options aren't idiomatic here.
2 / 5
Fill in: 'A copy of the entire source tree before installing dependencies will ___ the cache on every single commit.'
-
-
-
-
We say an early copy will 'invalidate' the cache — the standard, established Docker collocation. The other options aren't the recognised term here.
3 / 5
Fill in: 'We ___ layer order so rarely-changing instructions sit above frequently-changing ones.'
-
-
-
-
We 'order' layers — the standard collocation for arranging instructions to maximise reuse. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ a remote cache in CI so a cold runner still benefits from a previous build's layers.'
-
-
-
-
We 'use a remote cache' — the standard, simple collocation for adopting a caching mechanism. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ build times before and after a Dockerfile change to confirm the caching actually helped.'
-
-
-
-
We 'measure' build times — the standard, simple collocation. The other options are less idiomatic here.