DEA-C01 Question 258
Single answerAn analytics team is building a data pipeline to process large volumes of clickstream data in near real-time. They want to use Amazon Kinesis Data Streams to ingest the data and later process it using AWS Lambda. However, they need to ensure the data is retained for 7 days to allow for delayed downstream processing. What configuration should they apply to meet this requirement?
- A
Increase the shard count of the Kinesis Data Stream.
- B
Configure the retention period of the Kinesis Data Stream to 7 days.
- C
Enable enhanced fan-out on the Kinesis Data Stream.
- D
Use Kinesis Data Firehose instead of Kinesis Data Streams.
Show answer and explanation
Correct answer: B
Explanation
Kinesis Data Streams allows configuring a retention period of up to 7 days (and up to 365 days with extended retention). By setting the retention period to 7 days, the team ensures that the clickstream data is available for delayed downstream processing. Other options like increasing shard count or enabling enhanced fan-out do not affect data retention and do not solve the requirement.
- A. Incorrect.
Increasing the shard count improves throughput but does not affect retention period. This option does not meet the requirement.
- B. Correct.
Configuring the retention period to 7 days ensures that data will be retained for the required duration, allowing delayed downstream processing. This is the correct option.
- C. Incorrect.
Enhanced fan-out improves data delivery performance to consumers but does not impact data retention. Therefore, this is not the correct option.
- D. Incorrect.
Kinesis Data Firehose is designed for data delivery to destinations like S3 or Redshift, but it does not allow configuring a 7-day retention period for data in transit. This does not meet the stated requirement.