Microsoft DP-420 Exam - Topic 5 Question 55 Discussion

Actual exam question for Microsoft's DP-420 exam

Question #: 55
Topic #: 5

You have an Azure subscription.

You plan to create an Azure Cosmos DB for NoSQL database named DB1 that will store author and book data for authors that have each published up to ten books. Typical and frequent queries of the data will include:

* All books written by an individual author

* The synopsis of individual books

You need to recommend a data model for DB1. The solution must meet the following requirements:

* Support transactional updates of the author and book data.

* Minimize read operation costs.

What should you recommend?

ACreate a single container that stores author items and book items, and then items that represent the relationship between the authors and their books.

BCreate three containers, one that stores author items, a second that stores book items, and a third that stores items that represent the relationship between the authors and their books.

CCreate two containers, one that stores author items and another that stores book items. Embed a list of each author's books in the corresponding author item.

DCreate a single container that stores author items and book items. Embed a list of each author's books in the

Show Suggested Answer

Suggested Answer: D

by Alison at Dec 10, 2024, 01:49 PM

Limited Time Offer

25%

Off

Get Premium DP-420 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Kaycee

3 months ago

Embedding books in author items sounds smart, but what about updates?

upvoted 0 times

...

Yan

3 months ago

Wait, can Cosmos DB really handle that many transactions efficiently?

upvoted 0 times

...

Ressie

3 months ago

Three containers in option B seem excessive for this use case.

upvoted 0 times

...

Wilson

4 months ago

I disagree, option A would be more efficient for queries.

upvoted 0 times

...

Evangelina

4 months ago

I think option C is the best choice for embedding books with authors.

upvoted 0 times

...

Delbert

4 months ago

I recall that embedding data can help with performance, but I’m uncertain if option C or D is better for transactional updates. They both seem viable.

upvoted 0 times

...

Elin

4 months ago

I practiced a similar question where we had to balance transactional updates and read costs. I feel like option A might be too complex with multiple relationships.

upvoted 0 times

...

Ellsworth

4 months ago

I'm not entirely sure, but I think having a single container for both authors and books could simplify things. That might be option D?

upvoted 0 times

...

Essie

5 months ago

I remember discussing the importance of minimizing read operation costs, so maybe option C is a good choice since it embeds books within the author items.

upvoted 0 times

...

German

5 months ago

This is a tough one. I'm not sure if embedding the book list is the best approach - what if an author publishes a new book? That would require updating the author item, which could get expensive. Maybe option B with a separate container for the author-book relationship is a safer bet.

upvoted 0 times

...

Arlene

5 months ago

Okay, I think I've got it. We want to minimize read costs, so embedding the book list in the author item makes the most sense. That way we can quickly fetch all the books for a given author. Option C is the way to go here.

upvoted 0 times

...

Sommer

5 months ago

Hmm, I'm a bit confused on the relationship between authors and books. Do we need a separate container to store that, or can we embed it in the author or book items? I'll have to think through the tradeoffs carefully.

upvoted 0 times

...

Mira

5 months ago

This looks like a classic Cosmos DB data modeling question. I'd start by considering the requirements - we need to support transactional updates and minimize read costs. That points me towards option C or D.

upvoted 0 times

...

Jennifer

1 year ago

Option C is the way to go! Embedding the book list in the author item is like putting all your books on the same shelf - easy to find what you need.

upvoted 0 times

Ricarda

1 year ago

I think I'll go with option C for my Azure Cosmos DB data model. Thanks for the recommendation!

upvoted 0 times

...

Dino

1 year ago

It definitely simplifies the data structure and makes querying for author and book data more straightforward.

upvoted 0 times

...

Rachael

1 year ago

I agree, having two containers and embedding the book list in the author item makes sense for efficient queries.

upvoted 0 times

...

Hayley

1 year ago

Option C is the way to go! Embedding the book list in the author item is like putting all your books on the same shelf - easy to find what you need.

upvoted 0 times

...

Carin

1 year ago

I don't know, man. Option D sounds like a recipe for a hot mess. Why would you want to cram both author and book data into a single container? That's just asking for trouble.

upvoted 0 times

Danica

1 year ago

C) Create two containers, one that stores author items and another that stores book items. Embed a list of each author's books in the corresponding author item.

upvoted 0 times

...

Ryan

1 year ago

B) Create three containers, one that stores author items, a second that stores book items, and a third that stores items that represent the relationship between the authors and their books.

upvoted 0 times

...

Maryln

1 year ago

A) Create a single container that stores author items and book items, and then items that represent the relationship between the authors and their books.

upvoted 0 times

...

Rosendo

1 year ago

That's a good point, Lenita. Option C could definitely help minimize read operation costs.

upvoted 0 times

...

Lenita

1 year ago

I see your point, Gerry, but I think option C is the most efficient as it embeds the list of books directly in the author item.

upvoted 0 times

...

Velda

1 year ago

Definitely going with option C. It's a simple and efficient data model that meets all the requirements. Plus, it keeps the author and book data nicely organized.

upvoted 0 times

Kerry

1 year ago

Embedding the list of books in the author item does sound like a clean solution.

upvoted 0 times

...

Skye

1 year ago

I agree, option C seems like the best choice for this scenario.

upvoted 0 times

...

Gerry

1 year ago

I disagree, I believe option B is better as it separates the data into different containers for better organization.

upvoted 0 times

...

Altha

1 year ago

Option B seems overcomplicated for this use case. The extra container for the author-book relationship is unnecessary if we can just embed the book list in the author item.

upvoted 0 times

...

Rosendo

1 year ago

I think option A is the best choice because it keeps all the data in one container.

upvoted 0 times

...

Eric

1 year ago

I'd recommend option C. Embedding the book list in the author item makes sense for the given query patterns, and it also supports transactional updates.

upvoted 0 times