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 Exam DP-420 Topic 10 Question 44 Discussion

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

You have a database named db1 in an Azure Cosmos DB for NoSQL

You are designing an application that will use dbl.

In db1, you are creating a new container named coll1 that will store in coll1.

The following is a sample of a document that will be stored in coll1.

The application will have the following characteristics:

* New orders will be created frequently by different customers.

* Customers will often view their past order history.

You need to select the partition key value for coll1 to support the application. The solution must minimize costs.

To what should you set the partition key?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Shawn at Jul 17, 2024, 08:59 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Helene
1 months ago
I'd set the partition key to 'hasCoupon'. That way, the database will always know which orders have coupons and which don't. *winks*
upvoted 0 times
...
Rochell
1 months ago
The partition key should be 'id', of course! That's the most common and reliable choice for any database, right? *chuckles* Just kidding, 'customerId' is probably the way to go here.
upvoted 0 times
Lavelle
16 days ago
I think 'customerId' would work well to group orders by customer.
upvoted 0 times
...
Leonor
22 days ago
Agreed, 'customerId' makes the most sense for this scenario.
upvoted 0 times
...
...
Jacquelyne
2 months ago
Hmm, I'm not sure. 'orderDate' might be a good option to group orders chronologically and support the order history feature. But I guess 'customerId' is the safest choice.
upvoted 0 times
...
Glenna
2 months ago
I would go with 'orderId' as the partition key. This way, each order is isolated and can be accessed quickly, which is important for the application's performance.
upvoted 0 times
...
Hoa
2 months ago
Setting the partition key to 'customerId' makes the most sense to me. This will allow Azure Cosmos DB to efficiently distribute the data and handle the frequent creation of new orders and customers viewing their past orders.
upvoted 0 times
Lynda
17 days ago
Definitely 'customerId' for the partition key, it aligns well with the application requirements.
upvoted 0 times
...
Aimee
20 days ago
I think 'customerId' is the most logical option for the partition key.
upvoted 0 times
...
Fannie
22 days ago
I agree, setting the partition key to 'customerId' would be the best choice.
upvoted 0 times
...
...
Dick
3 months ago
That makes sense too. We need to consider both factors to minimize costs.
upvoted 0 times
...
Nu
3 months ago
I disagree, I believe we should set the partition key to orderId because new orders will be created frequently by different customers.
upvoted 0 times
...
Dick
3 months ago
I think we should set the partition key to customerId because customers will often view their past order history.
upvoted 0 times
...

Save Cancel