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 62 discussion

A company launched a service that produces millions of messages every day and uses Amazon Kinesis Data Streams as the streaming service.
The company uses the Kinesis SDK to write data to Kinesis Data Streams. A few months after launch, a data analyst found that write performance is significantly reduced. The data analyst investigated the metrics and determined that Kinesis is throttling the write requests. The data analyst wants to address this issue without significant changes to the architecture.
Which actions should the data analyst take to resolve this issue? (Choose two.)

  • A. Increase the Kinesis Data Streams retention period to reduce throttling.
  • B. Replace the Kinesis API-based data ingestion mechanism with Kinesis Agent.
  • C. Increase the number of shards in the stream using the UpdateShardCount API.
  • D. Choose partition keys in a way that results in a uniform record distribution across shards.
  • E. Customize the application code to include retry logic to improve performance.
Show Suggested Answer Hide Answer
Suggested Answer: CD 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
zanhsieh
Highly Voted 3 years, 8 months ago
CD. If wrong partition keys are distributed well, then retrying would still hit the hot shards. https://aws.amazon.com/blogs/big-data/under-the-hood-scaling-your-kinesis-data-streams/
upvoted 33 times
awssp12345
3 years, 8 months ago
agreed.
upvoted 2 times
...
GeeBeeEl
3 years, 8 months ago
D i agree with because of this other link https://aws.amazon.com/premiumsupport/knowledge-center/kinesis-data-stream-throttling-errors/ "use a random partition key to ingest your records. If the operations already use a random partition key, then adjust the key to correct the distribution." Why would you want to increase the number of shards, is that in the link?
upvoted 1 times
...
...
Paitan
Highly Voted 3 years, 8 months ago
C and D for me.
upvoted 7 times
...
MLCL
Most Recent 1 year, 10 months ago
Selected Answer: CD
More shards and better partitioning is always the answer for write performance issues.
upvoted 4 times
...
pk349
2 years, 1 month ago
CD: I passed the test
upvoted 1 times
...
Chelseajcole
2 years, 4 months ago
Why no B? Kinesis should have better performance than KPL
upvoted 2 times
...
cloudlearnerhere
2 years, 6 months ago
Selected Answer: CD
Correct answers are C & D as the common causes are hitting shard limits and. increasing shard count and choosing an appropriate partition key would help solve the issue.
upvoted 3 times
...
thirukudil
2 years, 7 months ago
Selected Answer: CD
throttling writes mean there is no sufficient shards. so we need to increase the shard counts. Introducing partition key helps in uniform distribution of writes across the shards which in turn we can avoid hot shards
upvoted 3 times
...
Arka_01
2 years, 8 months ago
Selected Answer: CD
None of the other options makes sense.
upvoted 1 times
...
rocky48
2 years, 10 months ago
Selected Answer: CD
answer is CD
upvoted 1 times
...
Bik000
3 years ago
Selected Answer: CD
Answer is C & D
upvoted 1 times
...
aws2019
3 years, 6 months ago
C and D
upvoted 1 times
...
Donell
3 years, 7 months ago
C,D is the answer.
upvoted 1 times
...
ariane_tateishi
3 years, 7 months ago
Considering the link bellow the option E isn't a valid option. "If there is a retry mechanic in the producer, failed records are tried again. This can also cause a delay in processing." https://aws.amazon.com/pt/premiumsupport/knowledge-center/kinesis-data-stream-throttling/
upvoted 1 times
...
lostsoul07
3 years, 7 months ago
C,D is the right answer
upvoted 3 times
...
Par301
3 years, 7 months ago
When there are failed records that aren't able to enter the Kinesis data stream, the stream throttles. If there is a retry mechanic in the producer, failed records are tried again. This can also cause a delay in processing. https://aws.amazon.com/premiumsupport/knowledge-center/kinesis-data-stream-throttling/ So an existing retry logic can also result in throttling. I think C&D will make more sense as they are meant for performance increase. Retry logic is more for handling errors and not handling performance.
upvoted 5 times
...
Draco31
3 years, 7 months ago
C and D for me. "A few months after launch, a data analyst found that write performance is significantly reduced" means the load is increasing constantly and will not decrease, and it's not a temporary spike. So we are facing a lack of shard or bad partition key is burning some shards over time
upvoted 6 times
...
kamparia
3 years, 7 months ago
It's C & E for me. D is not an option because changing the partition key affects the architecture.
upvoted 1 times
MWL
3 years ago
"changing the partition key" just change the code to use different key during putting item. No architecture changed.
upvoted 2 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 ...