AWS Data Analytics Quiz

https://aws.amazon.com/iot-core/features/

It’s ‘device shadow’, not ‘device echo’, otherwise all others listed are components of IoT Core.

a) Incorrect – Kinesis Data Firehose has a latency of 60 seconds

b) Correct – Simple Queing Services (SQ) supports less than 10mS for publish and receive

c) Incorrect – Database Migration Services are used to migrate data from source to target database and in general are not suitable for real-time applications.

d) Kinesis Data Streams can support an indefinite number consumers at 70mS latency via ‘enhanced fan-out’

All storage classes including Intelligent tiering, require objects to be stored in a previous class for at least 30 days:

https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html

“The S3 Intelligent-Tiering storage class stores objects in two access tiers: one tier that is optimized for frequent access and another lower-cost tier that is optimized for infrequently accessed data. For a small monthly monitoring and automation fee per object, Amazon S3 monitors access patterns of the objects in the S3 Intelligent-Tiering storage class and moves objects that have not been accessed for 30 consecutive days to the infrequent access tier.”

https://docs.aws.amazon.com/AmazonS3/latest/dev/lifecycle-transition-general-considerations.html

“Before you transition objects from the S3 Standard or S3 Standard-IA storages classes to S3 Standard-IA or S3 One Zone-IA, you must store them at least 30 days in the S3 Standard storage class. For example, you cannot create a Lifecycle rule to transition objects to the S3 Standard-IA storage class one day after you create them. Amazon S3 doesn’t transition objects within the first 30 days because newer objects are often accessed more frequently or deleted sooner than is suitable for S3 Standard-IA or S3 One Zone-IA storage.”

For non fan-out Kinesis consumers, the two consumers share the 2MB/s throughput and therefore get 1MB/s each.

With a limit of 5 API calls shared between a shard’s consumers, that’s a call every 200mS, shared by 2 consumers means 400mS latency.

https://docs.aws.amazon.com/streams/latest/dev/building-consumers.html

a) True –  Only GZIP is supported to Redshift though.
b) True – KDF supports S3, Redshift, ElasticSearch, Splunk
c) False (Correct) – Kinesis Client Library cannot be used with KDF.
d) True – Unlike Kinesis Data Streams, capacity does not need to be provisioned in advance.

Kinesis Data Firehose supports output to S3, Redshift, ElasticSeach, Splunk

a) incorrect – encryption is fully managed server side by AWS. Use of KMS provide some additional user control, but you don’t need to supply the key
b) correct – you supply the data key for SSE-C
c) correct – AWS provides Amazon S3 Encryption client, https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingClientSideEncryption.html
d) incorrect – the bucket policy encryption default overides any HTTP header

Authentication Options for IoT

https://docs.aws.amazon.com/iot/latest/developerguide/authentication.html

a) Incorrect – Both KDS and KDF can be configured within the same agent
b) Correct – Kinesis endpoint(s) are set within the agent.json file
c) Incorrect – The Kinesis Agent handles file rotation, checkpointing and retry upon failure
d) Correct – The Kinesis Agent is only available for Linux “Your operating system must be either Amazon Linux AMI with version 2015.09 or later, or Red Hat Enterprise Linux version 7 or later.“https://docs.aws.amazon.com/streams/latest/dev/writing-with-agents.html