Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft Exam DP-420 Topic 1 Question 51 Discussion

Actual exam question for Microsoft's DP-420 exam
Question #: 51
Topic #: 1
[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

Contribute your Thoughts:

Queen
2 months ago
I agree, using orderDate as the partition key is a bad idea. It's like trying to fit a million orders into a single shoebox - it just ain't gonna work!
upvoted 0 times
...
Celestina
2 months ago
Yikes, I hope they don't choose orderDate as the partition key. That would be a recipe for disaster, like trying to fit a square peg in a round hole!
upvoted 0 times
Lezlie
25 days ago
C) You will exceed the maximum storage per partition.
upvoted 0 times
...
Therese
26 days ago
B) Queries will run cross-partition.
upvoted 0 times
...
Murray
2 months ago
A) You will exceed the maximum number of partition key values.
upvoted 0 times
...
...
Rhea
2 months ago
Not to mention, there will always be a hot partition as new orders come in. That could lead to uneven distribution of the workload.
upvoted 0 times
Dorethea
2 months ago
D) There will always be a hot partition.
upvoted 0 times
...
Broderick
2 months ago
B) Queries will run cross-partition.
upvoted 0 times
...
Rutha
2 months ago
A) You will exceed the maximum number of partition key values.
upvoted 0 times
...
...
Paris
2 months ago
But wouldn't using orderDate as the partition key make queries more efficient for viewing past order history?
upvoted 0 times
...
Yong
2 months ago
Exactly! And with one million orders daily, we'll likely exceed the maximum storage per partition too. This could cause performance problems.
upvoted 0 times
Maricela
2 months ago
Yes, using orderDate as the partition key could lead to exceeding the maximum storage per partition.
upvoted 0 times
...
My
2 months ago
C) You will exceed the maximum storage per partition.
upvoted 0 times
...
Shaunna
2 months ago
A) You will exceed the maximum number of partition key values.
upvoted 0 times
...
...
Kara
3 months ago
I agree with Earleen. Having a hot partition can cause performance issues.
upvoted 0 times
...
Ranee
3 months ago
Using orderDate as the partition key doesn't sound like a good idea. We'll have too many partition key values and that could lead to issues with the maximum number of partitions.
upvoted 0 times
Gerald
2 months ago
C) You will exceed the maximum storage per partition.
upvoted 0 times
...
Cristy
2 months ago
A) You will exceed the maximum number of partition key values.
upvoted 0 times
...
...
Earleen
3 months ago
I think using orderDate as the partition key will lead to a hot partition.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77