Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Microsoft DP-420 Exam - Topic 13 Question 21 Discussion

You plan to store order data in Azure Cosmos DB for NoSQL account. The data contains information about orders and their associated items.You need to develop a model that supports order read operations. The solution must minimize the number or requests.
B) Create a single database that contains one container. Create a separate document for each order and embed the order items into the order documents.
A) Create a single database that contains one container. Store orders and order items in separate documents in the container.
C) Create a database for orders and a database for order items.
D) Create a single database that contains a container for order and a container for order items.

Microsoft DP-420 Exam - Topic 13 Question 21 Discussion

Actual exam question for Microsoft's DP-420 exam
Question #: 21
Topic #: 13
[All DP-420 Questions]

You plan to store order data in Azure Cosmos DB for NoSQL account. The data contains information about orders and their associated items.

You need to develop a model that supports order read operations. The solution must minimize the number or requests.

Show Suggested Answer Hide Answer
Suggested Answer: B

Azure Cosmos DB is a multi-model database that supports various data models, such as documents, key-value, graph, and column-family3.The core content-model of Cosmos DB's database engine is based on atom-record-sequence (ARS), which allows it to store and query different types of data in a flexible and efficient way3.

To develop a model that supports order read operations and minimizes the number of requests, you should consider the following factors:

The size and shape of your data

The frequency and complexity of your queries

The latency and throughput requirements of your application

The trade-offs between storage efficiency and query performance

Based on these factors, one possible model that you could implement isB. Create a single database that contains one container. Create a separate document for each order and embed the order items into the order documents.

This model has the following advantages:

It stores orders and order items as self-contained documents that can be easily retrieved by order ID1.

It avoids storing redundant data or creating additional containers for order items1.

It allows you to view the order history of a customer with simple queries1.

It leverages the benefits of embedding data, such as reducing the number of requests, improving query performance, and simplifying data consistency2.

This model also has some limitations, such as:

It may not be suitable for some order items that have data that is greater than 2 KB, as it could exceed the maximum document size limit of 2 MB2.

It may not be optimal for scenarios where order items need to be queried independently from orders or aggregated by other criteria2.

It may not support transactions across multiple orders or customers, as transactions are scoped to a single logical partition2.

Depending on your specific use case and requirements, you may need to adjust this model or choose a different one.For example, you could use a hybrid data model that combines embedding and referencing data2, or you could use a graph data model that expresses entities and relationships as vertices and edges.


by Helene at May 25, 2023, 03:29 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Levi
10 months ago
D feels like overkill with two containers, not needed!
upvoted 0 times
...
Jerilyn
10 months ago
Definitely leaning towards B, embedding items makes sense.
upvoted 0 times
...
Tasia
11 months ago
Surprised that option C is even a choice, that seems inefficient.
upvoted 0 times
...
Talia
11 months ago
I disagree, option A could work too!
upvoted 0 times
...
Norah
11 months ago
Option B seems like the best choice for minimizing requests.
upvoted 0 times
...
Angelyn
11 months ago
I recall that having separate databases for orders and items could lead to more requests, which isn't ideal. I think option D might not be the best choice.
upvoted 0 times
...
Katina
11 months ago
I practiced a similar question, and I feel like separating orders and order items into different containers might complicate things. So, I lean towards option B.
upvoted 0 times
...
Carrol
12 months ago
I'm not entirely sure, but I remember something about keeping related data together to minimize requests. Maybe option A could work too?
upvoted 0 times
...
Dwight
12 months ago
I think option B makes the most sense since embedding order items in the order documents could reduce the number of requests needed to read the data.
upvoted 0 times
...
Josphine
12 months ago
Hmm, I'm a bit confused by the different options here. I'll need to re-read the question and think through the security implications of each choice.
upvoted 0 times
...
Evette
1 year ago
Based on the information provided, I think the answer is 1 additional policy. The new parent policy will be the top-level policy, and the existing policies will become the child policies under it.
upvoted 0 times
...

Save Cancel