Practise the standard verbs for invalidating Varnish caches reliably.
0 / 5 completed
1 / 5
Fill in: 'We ___ a PURGE request to Varnish the instant the underlying content changes, so a stale cached page isn't served for the rest of its full TTL.'
We 'send a request' — the standard, simple collocation for issuing an explicit purge to the cache. The other options are less idiomatic here.
2 / 5
Fill in: 'Relying only on a long default TTL without any purge mechanism can ___ an edited page still serving its old content for hours after the update actually went live.'
We say no purge mechanism will 'leave' stale content served — the standard, natural collocation for the resulting staleness. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ cache objects by a content tag rather than by URL alone, so a single underlying change can invalidate every page that embeds it in one pass.'
We 'tag' cache objects — the standard, established collocation for grouping cached content for bulk invalidation. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ the VCL configuration in staging against real request patterns before deploying it, so a misrouted cache rule doesn't start serving the wrong content to real users.'
We 'test' a configuration — the standard, simple collocation for validating cache-routing logic before it goes live. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the cache hit ratio per backend closely, since a sudden drop after a deploy often means a header change is now bypassing the cache entirely.'
We 'monitor' a hit ratio — the standard collocation for ongoing observation of caching effectiveness. The other options aren't idiomatic here.