Kinesis Data Streams traffic rises sharply during weekday afternoons and write throttling occurs.
Increase write capacity before the peak without losing existing records.
Which action is most appropriate?
Plan a resharding operation that increases the number of shards in the provisioned stream.
Detailed explanation
Adding shards increases write and read capacity and can reduce throttling during the peak.
Adding shards increases write and read capacity and can reduce throttling during the peak.
Retention changes how long past records can be read; it does not increase current write capacity.
Retention changes how long past records can be read; it does not increase current write capacity.
This concentrates records on one shard and can make the hot-shard problem worse.
This concentrates records on one shard and can make the hot-shard problem worse.
CloudTrail retention does not change Kinesis ingestion capacity.
CloudTrail retention does not change Kinesis ingestion capacity.
Check official documentation
Compare the following points with the official documentation.
Kinesis Data Streamsのシャード容量、リシャーディング、スロットリングの公式説明を確認する。
What to confirm
容量拡張とデータ保持設定を区別し、ピーク前のスケーリング計画を説明できる。
Key points
- Shard
- Resharding
- Write capacity
- Throttling
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Capacity versus retention
Retention affects historical reads; resharding changes current write and read capacity.
Key skew
A biased partition key can still throttle one shard after the stream is expanded.