New Year Sale 2026! 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 3 Question 67 Discussion

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

You have a container in an Azure Cosmos DB for NoSQL account that stores data about orders. The following is a sample of an order document.

Documents are up to 2 KB.

You plan to receive one million orders daily.

Customers will frequently view then past order history.

You are the evaluating whether to use orderDate as the partition key.

What are two effects of using orderDate as the partition key? Each correct answer presents a complete solution.

NOTE: Each correct selection is worth one point.

Show Suggested Answer Hide Answer
Suggested Answer: B, D

by Jovita at Aug 12, 2025, 06:01 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
Candra
3 months ago
I doubt that would happen with a million orders daily.
upvoted 0 times
...
Cherry
3 months ago
I think queries will run cross-partition too.
upvoted 0 times
...
Gilma
3 months ago
Definitely agree, that’s a big risk!
upvoted 0 times
...
Alline
3 months ago
Wait, can you really exceed the max number of partition key values?
upvoted 0 times
...
Adell
3 months ago
Using orderDate as a partition key could lead to a hot partition.
upvoted 0 times
...
Carey
4 months ago
I feel like using orderDate might not be the best choice since it could lead to a hot partition, but I can't recall the exact implications on performance.
upvoted 0 times
...
Sabine
4 months ago
I practiced a similar question, and I think exceeding the maximum storage per partition could happen if we have too many orders in a single day.
upvoted 0 times
...
Amira
4 months ago
I'm not entirely sure, but I think queries running cross-partition could be a problem if the data is not evenly distributed.
upvoted 0 times
...
Yoko
4 months ago
I remember that using a date as a partition key can lead to a hot partition issue, especially with high write volumes.
upvoted 0 times
...
Devora
4 months ago
I'm feeling pretty confident about this one. The key things to consider are the maximum number of partition key values and the potential for a hot partition with all the daily orders. I'll make sure to select the two most relevant effects.
upvoted 0 times
...
Christiane
5 months ago
Okay, I think I have a strategy here. If we get one million orders daily, that could lead to a huge number of partition key values over time, which could exceed the limits. And with frequent queries on past orders, that might cause issues with cross-partition queries.
upvoted 0 times
...
Hester
5 months ago
Hmm, I'm a bit confused about the potential issues with using orderDate. I'll need to review the information about partition keys and storage limits.
upvoted 0 times
...
Gwenn
5 months ago
This seems like a tricky question. I'll need to think carefully about the effects of using orderDate as the partition key.
upvoted 0 times
...

Save Cancel