Microsoft DP-420 Exam - 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

Aleta

5 months ago

Totally with B! It’s optimized for reading, makes sense!

upvoted 0 times

...

Janae

5 months ago

Wait, embedding users? Isn’t that risky if user data grows?

upvoted 0 times

...

Roslyn

5 months ago

C could work, but it feels a bit complicated.

upvoted 0 times

...

Florinda

5 months ago

I think A is better for scalability, though.

upvoted 0 times

...

Mila

5 months ago

Option B seems solid, embedding users keeps everything together.

upvoted 0 times

...

Colette

6 months ago

I recall that embedding can help with performance, but I’m not certain if the user data being over 2 KB affects that decision in option B.

upvoted 0 times

...

Socorro

6 months ago

I’m a bit confused about whether to use separate containers or embed data. I feel like option A might complicate things with too many documents.

upvoted 0 times

...

Cheryl

6 months ago

I think option B sounds familiar from our practice questions, where we talked about reducing the number of queries needed to fetch users.

upvoted 0 times

...

Aleta

6 months ago

I remember we discussed the importance of optimizing for read operations, but I'm not sure if embedding users in company documents is the best approach.

upvoted 0 times

...

This is a tough one. I'm not sure which option is best. I might need to draw out some diagrams to visualize the different approaches and how they'd work. Gotta make sure I fully understand the requirements before jumping into an answer.

upvoted 0 times

...

Lelia

6 months ago

Hmm, I'm a bit confused on the partition key part. Should I use the company ID or the user ID? I'll need to think through the tradeoffs of each approach.

upvoted 0 times

...

Haydee

6 months ago

This looks like a pretty straightforward data modeling question. I'd start by thinking through the requirements and how to best structure the data to optimize for reading. The key seems to be associating users with their companies.

upvoted 0 times

...

Brent

6 months ago

Okay, I think I've got a strategy. Since the question says to optimize for reading, I'd go with option B and embed the users into the company documents. That way I can quickly retrieve all the users for a given company.

upvoted 0 times

...

Norah

6 months ago

I think the answer is A. The auditee would want to assess the key auditor skills like interviewing, interaction, and the accuracy of the final report.

upvoted 0 times

...

Gilbert

6 months ago

Hmm, this looks like a tricky configuration question. I'll need to carefully examine the exhibit and options to determine the correct setup for 12 time slots.

upvoted 0 times

...

Anabel

6 months ago

Hmm, I'm not too sure about this one. I'll need to think through the different options carefully.

upvoted 0 times

...

Danilo

6 months ago

I'm leaning towards the shop order master file too. I think we practiced a question like this last week!

upvoted 0 times

...

Honey

11 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

Mickie

9 months ago

Definitely. It's all about optimizing for the most common use cases while still allowing for future growth and changes.

upvoted 0 times

...

Lashaun

9 months ago

I see your point. It's important to consider how the data will be accessed and what kind of queries will be common.

upvoted 0 times

...

Ivan

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

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

11 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

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

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

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

11 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

10 months ago

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

upvoted 0 times

...

Lucina

11 months ago

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

upvoted 0 times

...

Aron

11 months ago

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

upvoted 0 times

...

Luisa

11 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