Section 19: AWS Integration & Messaging: SQS, SNS & Kinesis: Quiz

Question 1

Answer 1

D. Do nothing SQS scaled automatically. no notes.

Question 2

Answer 2

A. Increase the DelaySeconds parameter. Note is: Good job!
SQS Delay Queues is a period of time during which Amazon SQS keeps new SQS messages invisible to consumers. In SQS Delay Queues, a message is hidden when it is first added to the queue. (default: 0 mins, max.: 15 mins)

Question 3

Answer 3

C. Increase visability timeout. Note is: Good job!
SQS Visibility Timeout is a period of time during which Amazon SQS prevents other consumers from receiving and processing the message again. In Visibility Timeout, a message is hidden only after it is consumed from the queue. Increasing the Visibility Timeout gives more time to the consumer to process the message and prevent duplicate reading of the message. (default: 30 sec., min.: 0 sec., max.: 12 hours)

Question 4

Answer 4

B. SQS Dead Letter Queue. Note is: success alert
Good job!
SQS Dead Letter Queue is where other SQS queues (source queues) can send messages that can’t be processed (consumed) successfully. It’s useful for debugging as it allows you to isolate problematic messages so you can debug why their processing doesn’t succeed.

Question 5

Answer 5

D. SQS FIFO Queue. Note is: success alert
Good job!
SQS FIFO (First-In-First-Out) Queues have all the capabilities of the SQS Standard Queue, plus the following two features. First, The order in which messages are sent and received are strictly preserved and a message is delivered once and remains available until a consumer process and deletes it. Second, duplicated messages are not introduced into the queue.

Question 6

Answer 6

B. SNS + SQS Fan Out Pattern. Note is: Good job!
This is a common pattern where only one message is sent to the SNS topic and then “fan-out” to multiple SQS queues. This approach has the following features: it’s fully decoupled, no data loss, and you have the ability to add more SQS queues (more applications) over time.

Question 7

Answer 7

B. Add more shards. Note is: Good job!
The capacity limits of a Kinesis data stream are defined by the number of shards within the data stream. The limits can be exceeded by either data throughput or the number of reading data calls. Each shard allows for 1 MB/s incoming data and 2 MB/s outgoing data. You should increase the number of shards within your data stream to provide enough capacity.

Question 8

Answer 8

C. For each record sent to Kenisis add a partition key that represents the identify of the users. Note is: Question 8:
You have a website where you want to analyze clickstream data such as the sequence of clicks a user makes, the amount of time a user spends, and where the navigation begins, and how it ends. You decided to use Amazon Kinesis, so you have configured the website to send these clickstream data all the way to a Kinesis data stream. While you checking the data sent to your Kinesis data stream, you found that the users’ data is not ordered and the data for one individual user is spread across many shards. How would you fix this problem?

Question 9

Answer 9

C. Amazon Kenesis Data Analytics. Note is: Good job!
Use Kinesis Data Analytics with Kinesis Data Streams as the underlying source of data.

Question 10

Answer 10

C. Kinesis Data Streams + Kinesis Data Firehose. Note is: Good job!
This is a perfect combo of technology for loading data near real-time data into S3 and Redshift. Kinesis Data Firehose supports custom data transformations using AWS Lambda..

Question 11

Answer 11

A. Amazon Kinesis Data Streams. Note is: success alert
Good job!
Note: Kinesis Data Firehose is now supported, but not Kinesis Data Streams.

Question 12

Answer 12

B. Amazon SNS. No note.

Question 13

Answer 13

A. SNS Message Filtering. Note is: success alert
Good job!
SNS Message Filtering allows you to filter messages sent to SNS topic’s subscriptions.

Question 14

Answer 14

B. Implement a Dead Letter Queue with a redrive policy. no note.

Question 15

Answer 15

B. Enable Long Polling. No note.

Question 16

Answer 16

C. Use the SQS Extended Client Library

Question 17

Answer 17

C. Forteen days. Note is: Good job!
You can configure the Amazon SQS message retention period to a value from 1 minute to 14 days. The default is 4 days.

Question 18

Answer 18

B. MessageGroupId. No note.

Question 19

Answer 19

A. MessageDeduplicationId. No notes.

Question 20

Answer 20

C. 10. Note is: Question 20:
A Kinesis Data Stream that you manage experiencing an increase in traffic due to a sale day. Your Kinesis Data Streams currently has 6 shards, and you have been asked to split shards to become 10 shards. You have been using a consuming application based on Kinesis Client Library (KCL) and are running on a set of EC2 instances. What’s the maximum number of EC2 instances that can be deployed to process the messages in shards?

Question 21

Answer 21

B. 10. Note is: Good job!
You can have as many consumers as “MessageGroupID” for your SQS FIFO queues.

Question 22

Answer 22

D. 365 days. no notes.

Question 23

Answer 23

C. Contact AWS Support to increase your Kinesis Stream’s capacity.

Question 24

Answer 24

B. Enhanced Fan Out Consumer. No note.

Question 25

Answer 25

A. Shard Splitting.