This website uses cookies to ensure you get the best experience.
Learn more.
A Lambda consumer reads SQS batches. One record fails after the others succeed, and downstream writes must not duplicate during retries. Which implementation choices are appropriate? Select 2 answers.
Published
- Delete all messages immediately before processing the batch.
- Return success for every failed record without preserving it.
- Make target writes idempotent and configure a visibility timeout suitable for processing and retries.
- Enable supported partial-batch responses and identify failed messages in the required response shape.
- Assume standard SQS provides exactly-once application side effects.
Comments — 0
Sign in to comment