Amazon BDS-C00 Exam - Topic 4 Question 90 Discussion

Actual exam question for Amazon's BDS-C00 exam

Question #: 90
Topic #: 4

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?

ADefine a Primary Key with ServerName as Partition Key and TimeStamp as Sort Key. Don NOT define a Secondary Index or Global Secondary Index.

BDefine a Primary Key with StreamName as Partition Key and TimeStamp followed by ServerName as Sort Key. Define a Global Secondary Index with ServerName as Partition Key and TimeStamp followed by StreamName.

CDefine a Primary Key with ServerName as Partition Key. Define a Local Secondary Index with StreamName as Partition Key. Define a Global Secondary Index with TimeStamp as Partition Key.

DDefine a Primary Key with ServerName as Partition Key. Define a Local Secondary Index with TimeStamp as Partition Key. Define a Global Secondary Index with StreamName as Partition key and TimeStamp as Sort Key.

Show Suggested Answer

Suggested Answer: B

by Ailene at Apr 19, 2024, 09:19 PM

Limited Time Offer

25%

Off

Get Premium BDS-C00 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Ardella

3 months ago

Not sure if a GSI is really necessary here, though.

upvoted 0 times

...

Carry

3 months ago

B gives the flexibility needed for those queries.

upvoted 0 times

...

Chau

3 months ago

Surprised that D has so many indexes, seems overkill!

upvoted 0 times

...

Latrice

4 months ago

I disagree, I think A is simpler and more efficient.

upvoted 0 times

...

Carole

4 months ago

Option B seems like the best choice for querying by stream and server.

upvoted 0 times

...

Hyun

4 months ago

I’m a bit confused about the difference between Local and Global Secondary Indexes in this context. I think I leaned towards option D in my practice, but I’m not entirely confident.

upvoted 0 times

...

Dino

4 months ago

I practiced a similar question where we had to optimize for both time and stream queries, and I feel like a composite key might be the way to go, but I’m torn between B and D.

upvoted 0 times

...

Micah

4 months ago

I think option B sounds familiar; it might allow for more flexibility with the Global Secondary Index, but I can't recall if it’s the most efficient setup.

upvoted 0 times

...

Shelton

5 months ago

I remember we discussed how using ServerName as the Partition Key could help with queries related to specific servers, but I'm not sure if that's the best choice for time range queries.

upvoted 0 times

...

Maia

5 months ago

I'm feeling pretty confident about this one. I've designed similar DynamoDB tables before, so I think I can apply that experience to select the most efficient option for the given requirements.

upvoted 0 times

...

Gladys

5 months ago

Okay, I think I've got a strategy here. The key is supporting queries by stream, server, and time range. I'll need to carefully choose the partition and sort keys to enable those queries efficiently.

upvoted 0 times

...

Tawna

5 months ago

Hmm, I'm a bit confused by all the different index options. I'll need to review the details on partition keys, sort keys, and global/local secondary indexes to make sure I understand the trade-offs.

upvoted 0 times

...

Josefa

5 months ago

This looks like a tricky DynamoDB table design question. I'll need to carefully consider the query requirements and how the different key options can support them.

upvoted 0 times

...

Man

5 months ago

Okay, let's see. The question mentions migrating a legacy install base, so I'm guessing we'll need to populate objects related to the existing products and contracts, like Assets and Subscriptions. And of course, the Order and Quote objects would be important for the new Salesforce CPQ system.

upvoted 0 times

...

Laticia

5 months ago

Hmm, I'm a bit confused by the different variable syntax options. I'll need to double-check the documentation to make sure I understand how to properly reference the custom column.

upvoted 0 times

...

Tiara

5 months ago

This question seems straightforward, but I want to make sure I understand the key differences between 'PREPARE' and 'EXECUTE' before selecting an answer.

upvoted 0 times

...

Rutha

5 months ago

I have a feeling that “Apply Both Direction DISABLED” wouldn't support any connection, especially for HTTP. I might lean towards Option A, but I'm not 100% sure.

upvoted 0 times

...

Beatriz

10 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 months ago

I think I'll go with Option B as well. Thanks for the input!

upvoted 0 times

...

Margot

9 months ago

Definitely! Global Secondary Indexes can really speed up the query process.

upvoted 0 times

...

Irving

9 months ago

I agree, Option B with the Global Secondary Index seems like the best choice for efficient querying.

upvoted 0 times

...

Domingo

10 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

9 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

9 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

10 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

11 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

11 months ago

I disagree, I believe option D is better because it allows for more flexibility in querying.

upvoted 0 times

...

Josue

11 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