Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam BDS-C00 Topic 4 Question 90 Discussion

Actual exam question for Amazon's BDS-C00 exam
Question #: 90
Topic #: 4
[All BDS-C00 Questions]

A customer has an Amazon S3 bucket. Objects are uploaded simultaneously by a cluster of servers from multiple streams of data. The customer maintains a catalog of objects uploaded in Amazon S3 using an Amazon DynamoDB table. This catalog has the following fields StreamName, TimeStamp, and ServerName, TimeStamp, and ServerName, from which ObjectName can be obtained.

The customer needs to define the catalog to support querying for a given stream or server within a defined time range.

Which DynamoDB table scheme is most efficient to support these queries?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Beatriz
2 months ago
Option B is the clear winner here. I mean, who doesn't love a good ol' Global Secondary Index? It's like the secret sauce of DynamoDB queries!
upvoted 0 times
Paulene
9 days ago
I think I'll go with Option B as well. Thanks for the input!
upvoted 0 times
...
Margot
10 days ago
Definitely! Global Secondary Indexes can really speed up the query process.
upvoted 0 times
...
Irving
1 months ago
I agree, Option B with the Global Secondary Index seems like the best choice for efficient querying.
upvoted 0 times
...
...
Domingo
2 months ago
Option B is the way to go! Partition keys and sort keys for the win. Now I just need to remember what a 'sort key' is...
upvoted 0 times
Berry
1 months ago
Yes, having StreamName as the Partition Key and TimeStamp followed by ServerName as the Sort Key will make querying for a given stream or server within a defined time range much more efficient.
upvoted 0 times
...
Melissa
1 months ago
I agree, Option B seems like the best choice for this scenario. Sort keys help with organizing the data.
upvoted 0 times
...
...
Man
2 months ago
I agree, Option B looks like the best solution. The global secondary index allows for efficient queries on both stream and server.
upvoted 0 times
...
Jennifer
2 months ago
That's a good point, I see your reasoning. Option D does seem to offer more options for querying.
upvoted 0 times
...
Theron
2 months ago
I disagree, I believe option D is better because it allows for more flexibility in querying.
upvoted 0 times
...
Josue
2 months ago
Option B seems the most efficient to me. Querying by stream or server within a time range can be easily supported with the primary key and secondary indexes defined.
upvoted 0 times
Gladys
22 days ago
Yes, option B with the Global Secondary Index provides the necessary flexibility for the customer's querying needs.
upvoted 0 times
...
Terry
1 months ago
Option B does seem to cover all the requirements for querying by stream or server within a defined time range.
upvoted 0 times
...
Shawn
1 months ago
I agree, option B with the Global Secondary Index seems like the most efficient way to support those queries.
upvoted 0 times
...
Sheridan
2 months ago
I think option B is the best choice. It allows for efficient querying by stream or server within a time range.
upvoted 0 times
...
...
Jennifer
2 months ago
I think option B is the most efficient.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77