Practise the standard verbs for configuring AWS SQS visibility timeouts.
0 / 5 completed
1 / 5
Fill in: 'We ___ the visibility timeout to comfortably exceed the consumer's worst-case processing time so a slow message isn't redelivered to a second worker mid-processing.'
We 'set a timeout' — the standard, simple collocation for configuring how long a message stays hidden after being received. The other options are less idiomatic here.
2 / 5
Fill in: 'Setting the visibility timeout too short for a slow handler can ___ the same message processed twice by two different workers simultaneously.'
We say a short timeout will 'leave' a message processed twice — the standard, natural collocation for the resulting duplication. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the visibility timeout dynamically for a message that's taking longer than expected, rather than letting it expire mid-processing and get redelivered.'
We 'extend a timeout' — the standard, established SQS collocation for pushing back a message's hidden window from within the handler. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ the redrive policy alongside the visibility timeout so a message that keeps failing lands in a dead-letter queue instead of looping forever.'
We 'configure' a policy — the standard collocation for setting up how repeatedly failing messages are handled. The other options aren't idiomatic here.
5 / 5
Fill in: 'We ___ the approximate age of the oldest message in the queue, since a growing backlog can mean consumers aren't keeping up with the visibility timeout's pace.'
We 'monitor' message age — the standard collocation for ongoing observation of a queue-health metric. The other options aren't idiomatic here.