During a holiday parade, citizen phone apps will spike location and crowd-density telemetry far above normal weekday rates. What should architects do when planning Amazon Kinesis Data Streams and Amazon Data Firehose capacity for that day?
Select an answer to reveal the explanation.
Short Explanation
Parade day is rush hour for telemetry—size the lanes before the floats roll. Provision Kinesis shards and respect Firehose limits for the peak, not the quiet Tuesday baseline. Defaults forever, turning off encryption, or a lone tiny EC2 broker won’t carry the crowd.
Full Explanation
Streaming designs must provision for peak ingest: Kinesis Data Streams throughput scales with shard count (and on-demand mode where appropriate), and Firehose has delivery/throughput considerations that should be planned against expected spikes. Leaving only minimal defaults risks throttling during events. Disabling encryption is not a throughput strategy, and replacing managed streams with an undersized self-managed broker adds operational risk. Capacity planning against parade-day peaks is required for reliable high-performing ingest.