Practise the standard verbs for building slim Docker images with multistage builds.
0 / 5 completed
1 / 5
Fill in: 'We ___ a multistage build so compile-time dependencies never end up bloating the final runtime image.'
We 'use' a build technique — the standard, simple collocation for adopting an approach. The other options are less idiomatic here.
2 / 5
Fill in: 'A single-stage Dockerfile can ___ the final image with build tools nobody needs at runtime.'
We say a single stage will 'bloat' the image — the standard, natural collocation for unnecessary size growth. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ only the compiled binary from the build stage into the final slim runtime layer.'
We 'copy' an artifact — the standard, established Docker collocation (COPY --from) for pulling files between stages. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ layer caching by ordering instructions so rarely-changing steps sit above frequently-changing ones.'
We 'exploit caching' — the standard collocation for taking advantage of a build optimisation. The other options aren't idiomatic here.
5 / 5
Fill in: 'We ___ final image size after every Dockerfile change to catch an accidental regression early.'
We 'check' size — the standard, simple collocation for measuring a build output. The other options are less idiomatic here.