Exam AWS Certified Solutions Architect - Associate SAA-C02 topic 1 question 26 discussion

Correct, valid targets for KDF are S3, Redshift(copy via S3) and ElasticSearch ,no EBS. Further, 'real time' implies Kinesis. Another reason why B is incorrect is each shard need not be assigned to one sensor. Multiple sensors can use same shard. Thanks to the 'partition key' , if each sensor uses different key, hashing ensures that one random shard (remains same as partition key not changing)gets assigned to the sensor. Within a shard,data is always ordered ('sequence no').

Its A. Why not C? SQS FIFO has message id for grouping.Messages with same msg id are processed together,hence no need of indiv SQS FIFO queues.

SQS FIFO and KDS receive data in ordered sequence.

Kinesis Data Stream maintains ordering within shard,thanks to 'sequence numbers'. And one can ensure each sensor uses same shard by keeping its 'paritition key' the same. Further,multiple sensors may be mapped to same shard(internal hashing can map 2 different partition keys to same shard), but we always ensure that each sensor data(tied to one shard) is always ordered. Answer is A. Further,not B due to my above explanation on multiple sensors being able to use same shard.Also valid consumers for KDF are S3, Redshift(copy thru S3) and ElasticSearch, NO EBS.

The Answer is A https://aws.amazon.com/kinesis/data-streams/faqs/ How does Amazon Kinesis Data Streams differ from Amazon SQS? Amazon Kinesis Data Streams enables real-time processing of streaming big data. It provides ORDERING of records, as well as the ability to read and/or replay records in the same order to multiple Amazon Kinesis Applications.