Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Amazon MLS-C01 Exam - Topic 3 Question 82 Discussion

A Machine Learning Specialist is working for an online retailer that wants to run analytics on every customer visit, processed through a machine learning pipeline. The data needs to be ingested by Amazon Kinesis Data Streams at up to 100 transactions per second, and the JSON data blob is 100 KB in size.What is the MINIMUM number of shards in Kinesis Data Streams the Specialist should use to successfully ingest this data?
B) 10 shards and D) 1,000 shards
A) 1 shards
C) 100 shards

Amazon MLS-C01 Exam - Topic 3 Question 82 Discussion

Actual exam question for Amazon's MLS-C01 exam
Question #: 82
Topic #: 3
[All MLS-C01 Questions]

A Machine Learning Specialist is working for an online retailer that wants to run analytics on every customer visit, processed through a machine learning pipeline. The data needs to be ingested by Amazon Kinesis Data Streams at up to 100 transactions per second, and the JSON data blob is 100 KB in size.

What is the MINIMUM number of shards in Kinesis Data Streams the Specialist should use to successfully ingest this data?

Show Suggested Answer Hide Answer
Suggested Answer: B, D, F

by Quentin at Nov 26, 2023, 11:21 PM

Limited Time Offer

25%

Off

Get Premium MLS-C01 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Melvin
8 months ago
Definitely going with 10 shards for a buffer!
upvoted 0 times
...
Becky
8 months ago
I'm not sure about this, but 1,000 shards sounds excessive.
upvoted 0 times
...
Minna
8 months ago
Wait, 100 KB per transaction? That seems a bit heavy!
upvoted 0 times
...
Reed
8 months ago
I think 10 shards would be safer for peak loads.
upvoted 0 times
...
Corrina
9 months ago
You need at least 1 shard for 100 transactions per second.
upvoted 0 times
...
Jenelle
9 months ago
I vaguely recall that each shard can support 1 MB per second for writes, but I’m not confident about how that relates to the number of shards needed here.
upvoted 0 times
...
Peggie
9 months ago
If the JSON blob is 100 KB and we have 100 transactions per second, that sounds like a lot of data. I feel like we might need more than just one shard.
upvoted 0 times
...
Georgeanna
9 months ago
I think we need to calculate the total data size and then see how many shards we need based on the throughput. I practiced a similar question last week.
upvoted 0 times
...
Markus
9 months ago
I remember that each shard in Kinesis can handle up to 1,000 records per second, but I'm not sure how that translates to the size of the data.
upvoted 0 times
...
Filiberto
9 months ago
This looks straightforward. I'm pretty confident I can solve this by applying the Kinesis Data Streams shard capacity rules. I'll just need to do the math to find the minimum number of shards.
upvoted 0 times
...
Aja
9 months ago
Okay, let's think this through step-by-step. The data is 100 KB per transaction, and the throughput is 100 transactions per second. I'll need to figure out the total data throughput and then determine the minimum number of shards required.
upvoted 0 times
...
Domonique
9 months ago
Hmm, I'm a bit unsure about this one. I'll need to review the Kinesis Data Streams documentation to make sure I understand the shard capacity and how to calculate the minimum number of shards.
upvoted 0 times
...
Edelmira
9 months ago
This seems like a straightforward Kinesis Data Streams question. I'll need to calculate the minimum number of shards required to handle the data throughput.
upvoted 0 times
...
Salena
10 months ago
I'm a bit confused on how to approach this. I know Kinesis Data Streams has a shard capacity, but I'm not sure how to calculate the minimum number of shards needed for this specific scenario. I'll need to review the concepts carefully.
upvoted 0 times
...
Marjory
10 months ago
I'm pretty sure the answer is C. Cholesky decomposition is a common technique for generating correlated multivariate normal random numbers.
upvoted 0 times
...
Caprice
10 months ago
I like the idea of including priority and version of software under test, those seem really important. But I'm not sure about the third field - I'm torn between incident identification and date to be fixed. Hmm, decisions, decisions.
upvoted 0 times
...
Maybelle
10 months ago
Hmm, the key here seems to be finding the right balance between the number of features and the model's performance. I think I'll try evaluating a model with the top 100 features, as suggested in option D, to see if that improves things.
upvoted 0 times
...
Whitney
1 year ago
Wait, are we talking about shards or Sauron's Nazgûl? Because I'm pretty sure 100 shards could take down a whole army of orcs...
upvoted 0 times
...
Anabel
1 year ago
1 shard? Seriously? That's like trying to drink from a fire hose. This is a job for an army of shards!
upvoted 0 times
Malcom
1 year ago
Let's go with 15 shards to be safe and ensure we can handle the data smoothly.
upvoted 0 times
...
Ling
1 year ago
Maybe even more than 10 shards, we need to make sure we can handle the data without any bottlenecks.
upvoted 0 times
...
Jacquelyne
1 year ago
I agree, we need to distribute the workload across multiple shards to handle the incoming data.
upvoted 0 times
...
Giuseppe
1 year ago
I think we should use at least 10 shards to handle this amount of data.
upvoted 0 times
...
...
Corrina
1 year ago
I'm going with 1,000 shards. Can't be too careful when it comes to high-volume data ingestion. Gotta future-proof that pipeline, you know?
upvoted 0 times
...
Eveline
1 year ago
Nah, 10 shards won't cut it. With that kind of throughput, we're looking at at least 100 shards to handle the load. Better safe than sorry!
upvoted 0 times
Kanisha
1 year ago
Definitely, we need to make sure the system can handle the throughput.
upvoted 0 times
...
Adelaide
1 year ago
Agreed, better safe than sorry when it comes to ingesting data.
upvoted 0 times
...
Edelmira
1 year ago
Yeah, 10 shards definitely won't be enough for this kind of throughput.
upvoted 0 times
...
Boris
1 year ago
Agreed, better safe than sorry when it comes to ingesting data.
upvoted 0 times
...
Cristina
1 year ago
I think we should go with 100 shards to handle the load.
upvoted 0 times
...
Lazaro
1 year ago
I think we should go with 100 shards to handle the load.
upvoted 0 times
...
...
Youlanda
1 year ago
I think the answer is 10 shards. 100 KB data blobs at 100 transactions per second should be well within the capacity of 10 shards.
upvoted 0 times
Santos
1 year ago
Using 10 shards seems like the most efficient option for ingesting the data.
upvoted 0 times
...
Louvenia
1 year ago
I think 10 shards is the correct choice for this scenario.
upvoted 0 times
...
Toi
1 year ago
I agree, 10 shards should be enough to handle that data load.
upvoted 0 times
...
...
Aaron
1 year ago
I disagree, I think the Specialist should use 100 shards to ensure smooth data ingestion.
upvoted 0 times
...
Blythe
1 year ago
I agree with Golda, 10 shards should be enough to handle the data.
upvoted 0 times
...
Golda
1 year ago
I think the Specialist should use 10 shards.
upvoted 0 times
...

Save Cancel