AWS EventBridge Rule Pattern Language Collocations
Practise the standard verbs for defining EventBridge rule patterns precisely.
0 / 5 completed
1 / 5
Fill in: 'We ___ an EventBridge rule pattern narrowly, rather than a wildcard match that catches events nobody actually intended to trigger.'
We 'define a pattern' — the standard, simple collocation for scoping an EventBridge rule. The other options are less idiomatic here.
2 / 5
Fill in: 'An overly broad content filter can ___ a downstream target flooded with events it was never actually meant to handle.'
We say a broad filter will 'leave' a target flooded — the standard, natural collocation for the resulting overload. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a dead-letter queue on every rule target, rather than silently dropping events a downstream service actually failed to process.'
We 'attach a queue' — the standard, simple collocation for adding a DLQ to a rule target. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every rule pattern against sample events before deploying, rather than assuming syntax nobody's actually tested will match.'
We 'test a pattern' — the standard, simple collocation for validating a rule against sample events. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ rule invocation metrics closely after a change, rather than assuming a redeployed rule is actually matching as expected.'
We 'monitor metrics' — the standard, simple collocation for watching rule behavior post-change. The other options aren't idiomatic here.