Practise the standard verbs for managing Cloudflare cache rules safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ a cache rule for static assets so Cloudflare serves them from the edge instead of hitting origin every time.'
We 'create a rule' — the standard, simple collocation for defining a new caching policy. The other options are less idiomatic here.
2 / 5
Fill in: 'An overly broad cache rule can ___ a personalised, user-specific page served to the wrong visitor entirely.'
We say a broad rule will 'risk' serving the wrong content — the standard, natural collocation for exposing a system to danger. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a cache-busting deploy so a stale edge cache never keeps serving a version we've already replaced.'
We 'trigger' a purge — the standard, established collocation for initiating a cache-invalidation action. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ cache hit ratio in the Cloudflare analytics dashboard to see how effective a rule actually is.'
We 'check' a ratio — the standard, simple collocation for inspecting a metric. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a bypass rule for the admin path so authenticated dashboard pages never get cached at the edge.'
We 'add a rule' — the standard, simple collocation for including a new policy. The other options are less idiomatic here.