Practise the standard verbs for busting stale browser caches on deploy.
0 / 5 completed
1 / 5
Fill in: 'We ___ a content hash into every asset filename so a stale browser cache never serves old code.'
We 'bake in' a hash — the standard, established front-end collocation for embedding a fingerprint into a filename. The other options aren't the recognised term here.
2 / 5
Fill in: 'An unversioned bundle URL can ___ users stuck on an old build long after a deploy has shipped.'
We say an unversioned URL will 'leave' users stuck — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ long cache lifetimes to hashed assets since their filename changes whenever the content does.'
We 'apply' a lifetime — the standard collocation for setting a caching rule on a resource. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ the HTML entry point with no-cache headers so it always fetches the latest asset manifest.'
We 'serve' a page — the standard, simple collocation for delivering it with specific response headers. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ cache headers in dev tools after every deploy to confirm busting is actually working end to end.'
We 'check' headers — the standard, simple collocation for inspecting response metadata. The other options are less idiomatic here.