Practise the standard verbs for configuring CloudFront Origin Shield.
0 / 5 completed
1 / 5
Fill in: 'We ___ Origin Shield in the region closest to the origin so a cache miss from any edge location converges on one shared shield cache instead of hitting the origin directly.'
We 'enable Origin Shield' — the standard, established CloudFront collocation for turning on an additional caching layer in front of the origin. The other options aren't the recognised term here.
2 / 5
Fill in: 'Running CloudFront without Origin Shield during a traffic spike can ___ every edge location's cache miss hitting the origin independently at the exact same moment.'
We say missing Origin Shield will 'leave' the origin hit by every edge independently — the standard, natural collocation for the resulting overload. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ requests through Origin Shield before they ever reach the origin, so a thundering herd of cache misses collapses into a single origin request.'
We 'route requests' — the standard, established collocation for directing traffic through an intermediate caching layer. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ Origin Shield's cache hit ratio closely, since a low hit ratio there means the origin is still absorbing far more load than the setup was meant to prevent.'
We 'monitor' a hit ratio — the standard collocation for ongoing observation of a caching-effectiveness metric. The other options aren't idiomatic here.
5 / 5
Fill in: 'We ___ the Origin Shield cache deliberately after an emergency origin fix, so a bad cached response isn't served to every edge location for the rest of its TTL.'
We 'invalidate a cache' — the standard, established collocation for deliberately discarding cached content after an upstream fix. The other options aren't the recognised term here.