Microsoft Exam DP-420 Topic 5 Question 25 Discussion

Actual exam question for Microsoft's DP-420 exam

Question #: 25
Topic #: 5

You need to create a data store for a directory of small and medium-sized businesses (SMBs). The data store must meet the following requirements:

* Store companies and the users employed by them. Each company will have less than 1,000 users.

* Some users have data that is greater than 2 KB.

* Associate each user to only one company.

* Provide the ability to browse by company.

* Provide the ability to browse the users by company.

* Whenever a company or user profile is selected, show a details page for the company and all the related users.

* Be optimized for reading data.

Which design should you implement to optimize the data store for reading data?

AIn a directory container, create a document for each company and a document for each user. Use company ID as the partition key.

BIn a company container, create a document for each company. Embed the users into company documents. Use the company ID as the partition key.

CCreate a user container that uses the user ID as the partition key and a company container that container that uses the company ID as the partition key. Add the company ID to each user documents.

DIn a user container, create a document for each user. Embed the company into each user document. Use the user ID as the partition key.

Show Suggested Answer

Suggested Answer: A

by Louisa at Sep 02, 2023, 01:26 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Honey

1 months ago

Haha, this question is a real brain-teaser! I'm kind of torn between options B and C. I guess it really depends on the specifics of the data and how you expect the application to be used. If you're mostly just browsing by company, then B might be the way to go. But if you need more flexibility in querying, C could be the better choice.

upvoted 0 times

Ivan

1 days ago

That's true, but C might offer more flexibility in the long run. It really depends on the specific needs of the application.

upvoted 0 times

...

Felice

18 days ago

I agree, it's a tough decision. I think B could be simpler if you mainly care about browsing by company.

upvoted 0 times

...

Sol

1 months ago

Option D seems like a good fit too. Embedding the company information into the user documents could make it easier to retrieve user details, and using the user ID as the partition key is a sensible choice. However, I'm not sure how well it would scale if the number of users per company starts to grow.

upvoted 0 times

Lajuana

1 days ago

True, scalability is a key factor to consider. Option A provides a good balance between optimizing data reading and scalability for the directory of SMBs.

upvoted 0 times

...

Jina

16 days ago

I agree, Option A would definitely make it easier to browse by company. It's important to consider scalability when designing the data store.

upvoted 0 times

...

Sage

23 days ago

Option A seems like the best choice for optimizing data reading. Using the company ID as the partition key for both company and user documents would make it efficient to browse by company.

upvoted 0 times

...

Sheridan

2 months ago

I'm not a big fan of embedding user data into the company documents. It might work for small companies, but for larger ones with hundreds of users, it could lead to bloated documents and performance issues. I think option C is a better approach, with separate containers for users and companies.

upvoted 0 times

Shonda

14 days ago

I see your point about option C, having separate containers would definitely make it easier to manage the data.

upvoted 0 times

...

Lucina

1 months ago

I think option A could work too, as long as the companies and users are not too large.

upvoted 0 times

...

Aron

1 months ago

I agree with you, option C seems like the best choice for scalability and performance.

upvoted 0 times

...

Luisa

2 months ago

The requirements definitely call for a document-based data store, and option B seems the most suitable. Embedding the users into the company documents will allow for efficient browsing by company, and using the company ID as the partition key will optimize for reading.

upvoted 0 times