Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.
exam questions

Exam AWS Certified Data Analytics - Specialty All Questions

View all questions & answers for the AWS Certified Data Analytics - Specialty exam

Exam AWS Certified Data Analytics - Specialty topic 1 question 119 discussion

A power utility company is deploying thousands of smart meters to obtain real-time updates about power consumption. The company is using Amazon Kinesis
Data Streams to collect the data streams from smart meters. The consumer application uses the Kinesis Client Library (KCL) to retrieve the stream data. The company has only one consumer application.
The company observes an average of 1 second of latency from the moment that a record is written to the stream until the record is read by a consumer application. The company must reduce this latency to 500 milliseconds.
Which solution meets these requirements?

  • A. Use enhanced fan-out in Kinesis Data Streams.
  • B. Increase the number of shards for the Kinesis data stream.
  • C. Reduce the propagation delay by overriding the KCL default settings.
  • D. Develop consumers by using Amazon Kinesis Data Firehose.
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
srinivasa
Highly Voted 3 years, 1 month ago
Answer: C https://docs.aws.amazon.com/streams/latest/dev/kinesis-low-latency.html
upvoted 10 times
...
kalakonda
Most Recent 10 months ago
Option A is correct. Checked in Bing app
upvoted 2 times
...
whenthan
1 year, 3 months ago
Selected Answer: C
Kinesis Data Streams records are available to be read immediately after they are written. There are some use cases that need to take advantage of this and require consuming data from the stream as soon as it is available. You can significantly reduce the propagation delay by overriding the KCL default settings to poll more frequently
upvoted 3 times
...
pk349
1 year, 6 months ago
C: I passed the test
upvoted 2 times
...
np2021
1 year, 8 months ago
I dug around the documentation, and the default is 1sec, but you can reduce to almost immediate (low millis). It's not recommended as sustainable on high traffic and you may end up with other issues on shards etc but the question doesnt care about this. Also the name of the property to change is not the same as in the question which is a little misleading, but the effect/solution is right (C).
upvoted 2 times
...
Arjun777
1 year, 9 months ago
Option A, using enhanced fan-out, can help achieve the desired reduction in latency by allowing multiple consumers to receive data from the same stream at the same time without having to share the same shard. This can help increase the overall throughput of the stream and reduce the time it takes for records to be processed and delivered to the consumer application.
upvoted 1 times
akashm99101001com
1 year, 8 months ago
"The company has only one consumer application."
upvoted 5 times
...
...
cloudlearnerhere
2 years ago
Correct answer is C as the default propagation delay for the KCL consumer is 1 second and reducing the delay can help reduce the latency. Propagation delay is defined as the end-to-end latency from the moment a record is written to the stream until it is read by a consumer application. This delay varies depending upon a number of factors, but it is primarily affected by the polling interval of consumer applications. Option A is wrong as enhanced fan-out in Kinesis Data Streams enables consumers to receive records from a stream with a throughput of up to 2 MB of data per second per shard. It doesn't reduce the latency for KCL. Option B is wrong as increasing shards doesn't reduce the latency for KCL. Option D is wrong as Kinesis Data Firehose calls Kinesis Data Streams GetRecords() once every second for each Kinesis shard.
upvoted 2 times
cloudlearnerhere
2 years ago
For most applications, we recommend polling each shard one time per second per application. This enables you to have multiple consumer applications processing a stream concurrently without hitting Amazon Kinesis Data Streams limits of 5 GetRecords calls per second. Additionally, processing larger batches of data tends to be more efficient at reducing network and other downstream latencies in your application. The KCL defaults are set to follow the best practice of polling every 1 second. This default results in average propagation delays that are typically below 1 second. Kinesis Data Streams records are available to be read immediately after they are written. There are some use cases that need to take advantage of this and require consuming data from the stream as soon as it is available. You can significantly reduce the propagation delay by overriding the KCL default settings to poll more frequently, https://docs.aws.amazon.com/streams/latest/dev/kinesis-low-latency.html
upvoted 1 times
...
...
rocky48
2 years, 4 months ago
Selected Answer: C
Answer: C https://docs.aws.amazon.com/streams/latest/dev/kinesis-low-latency.html
upvoted 1 times
...
lakeswimmer
2 years, 11 months ago
Answer C idleTimeBetweenReadsInMillis set between 200ms and 500ms
upvoted 4 times
...
Thiya
2 years, 12 months ago
Answer is C
upvoted 2 times
...
ali98
3 years ago
Answer C
upvoted 3 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...