A data-quality investigation needs up to seven days of events.
Existing Kinesis Data Streams records must remain available to consumers during the investigation.
Which configuration change is most appropriate?
Extend the Kinesis Data Streams retention period to at least seven days.
Detailed explanation
A longer retention period keeps the historical records available for rereading and investigation.
A longer retention period keeps the historical records available for rereading and investigation.
Records that were not delivered to S3 cannot be restored by an S3 lifecycle policy.
Records that were not delivered to S3 cannot be restored by an S3 lifecycle policy.
Shard count affects capacity and parallelism, not how long existing records are retained.
Shard count affects capacity and parallelism, not how long existing records are retained.
LATEST starts with new records and does not retain existing records.
LATEST starts with new records and does not retain existing records.
Check official documentation
Compare the following points with the official documentation.
Kinesis Data Streamsのデータ保持期間変更と追加料金の公式説明を確認する。
What to confirm
保持期間と読み取り開始位置が別の設定であることを説明できる。
Key points
- Retention period
- Replay
- LATEST
- Kinesis
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Retention versus position
Retention determines whether data exists; a starting position determines where a consumer begins reading.
Investigation planning
Retention extensions can add cost, so restore the intended setting after the investigation if appropriate.