Is this exercise free to use?

Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.

Do I get feedback if I answer incorrectly?

Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct collocation and why the other options don't fit.

Can I retry this exercise?

Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.

Do I need an account to track my progress?

No account is required. Your progress and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.

Is "GitLab CI Cache Strategy Language Collocations" part of a larger series?

Yes — it's one exercise in Collocations. See that category page for the full list of related collocation exercises.

Can I link directly to this exercise?

Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.

Where can I find more exercises like this one?

See Collocations for related exercises, or browse the main Collocations hub for other IT English word pairings.

Intermediate Collocations #ci-cd#engineering#devops#gitlab

GitLab CI Cache Strategy Language Collocations

Practise the standard verbs for building an effective GitLab CI cache strategy.

0 / 5 completed

1 / 5

Fill in: 'We ___ the cache key to the lockfile's hash so a dependency change automatically busts the cache instead of silently reusing outdated packages.'

2 / 5

Fill in: 'Using a single fixed cache key across every branch can ___ two pipelines running concurrently overwriting each other's cached dependencies mid-job.'

3 / 5

Fill in: 'We ___ the cache per job stage rather than globally, so an unrelated job further down the pipeline doesn't restore a cache meant for a completely different step.'

4 / 5

Fill in: 'We ___ pipeline duration before and after introducing a cache to confirm it's actually saving minutes, not just adding an extra restore step to every job.'

5 / 5

Fill in: 'We ___ a stale cache deliberately when a build starts behaving oddly, since a corrupted cache entry can silently reproduce the same failure on every subsequent run.'

Frequently Asked Questions

What does the "GitLab CI Cache Strategy Language Collocations" exercise practise?

Practise the standard verbs for building an effective GitLab CI cache strategy.

How many questions are in this exercise?

This exercise has 5 questions, each multiple-choice with an explanation shown after you answer.

What English level is this exercise for?

This exercise is tagged Intermediate. If the vocabulary feels difficult, browse Collocations for a related exercise to start with instead.

Show more questions (7)