A transformation bug requires the last 24 hours of events to be processed again.
A new consumer must read retained records from the beginning of the available window.
Which two settings are required?
Start the new consumer at TRIM_HORIZON and ensure the stream retention period covers the target data.
Detailed explanation
LATEST starts with records arriving after the consumer starts and skips the existing history.
LATEST starts with records arriving after the consumer starts and skips the existing history.
The records must remain retained until the consumer can read them again.
The records must remain retained until the consumer can read them again.
Recreating the stream discards the existing records and removes the replay source.
Recreating the stream discards the existing records and removes the replay source.
The consumer starts at the oldest record still retained, allowing the available history to be replayed.
The consumer starts at the oldest record still retained, allowing the available history to be replayed.
Check official documentation
Compare the following points with the official documentation.
Kinesis Data StreamsのStartingPosition、TRIM_HORIZON、LATEST、保持期間の公式説明を確認する。
What to confirm
読み取り開始位置とデータ保持期間を組み合わせて再処理条件を説明できる。
Key points
- TRIM_HORIZON
- LATEST
- Retention period
- Replay
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Position and availability
A historical start position cannot recover records that have already expired from retention.
Safe reruns
Replay processing should tolerate duplicates and use checkpoints or idempotent writes where appropriate.