Practise the standard verbs for configuring Envoy rate limiting reliably.
0 / 5 completed
1 / 5
Fill in: 'We ___ a global rate limit service in front of Envoy, rather than relying on each upstream to enforce its own inconsistent cap.'
We 'configure a rate limit service' — the standard, simple collocation for setting up centralized limiting. The other options are less idiomatic here.
2 / 5
Fill in: 'A misconfigured descriptor key can ___ legitimate traffic throttled alongside an actual abusive client.'
We say a bad descriptor will 'leave' legitimate traffic throttled — the standard, natural collocation for the resulting side effect. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ rate limit thresholds per route explicitly, rather than one blanket number that fits no actual service's real traffic pattern.'
We 'set thresholds' — the standard, simple collocation for fixing per-route limits. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every rate limit rule against staging load tests, rather than pushing a config nobody's actually validated under traffic.'
We 'test a rule' — the standard, simple collocation for validating a limit before production. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ 429 response rates on a dashboard continuously, rather than learning about over-throttling only from an angry customer email.'
We 'monitor rates' — the standard, simple collocation for watching throttling metrics over time. The other options aren't idiomatic here.