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

Microsoft Exam DP-420 Topic 2 Question 60 Discussion

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

You are designing an Azure Cosmos DB Core (SQL) API solution to store data from IoT devices. Writes from the devices will be occur every second.

The following is a sample of the data.

You need to select a partition key that meets the following requirements for writes:

Minimizes the partition skew

Avoids capacity limits

Avoids hot partitions

What should you do?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Dominga
5 days ago
Using the timestamp as the partition key might seem like a good idea, but it could lead to hot partitions and uneven distribution of data, which would impact the performance of the Azure Cosmos DB solution.
upvoted 0 times
...
Tamar
6 days ago
I disagree, I think creating a new synthetic key with deviceId and sensor1Value would be a better option to avoid capacity limits.
upvoted 0 times
...
Carla
7 days ago
I agree with Angella, using timestamp as the partition key will help minimize partition skew.
upvoted 0 times
...
Belen
8 days ago
That's a good point, but I still think D is the correct answer based on the command.
upvoted 0 times
...
Tyra
8 days ago
I'm just wondering if the exam will ask us to actually run that PowerShell command and see what happens. That would be a real test of our knowledge!
upvoted 0 times
...
Lyndia
10 days ago
Haha, multi-region writes? In your dreams! This is a simple failover command, not some advanced configuration.
upvoted 0 times
...
Angella
13 days ago
I think we should use timestamp as the partition key to avoid hot partitions.
upvoted 0 times
...
Francisca
14 days ago
But wouldn't that also mean that the account will be unavailable for writes during the change?
upvoted 0 times
...
Solange
15 days ago
Nah, I don't think the throughput will increase. That command is probably just changing the failover settings, not the provisioned capacity.
upvoted 0 times
...
Dottie
16 days ago
Hold up, are you sure that's not going to make the account unavailable for writes? I thought that was one of the potential side effects.
upvoted 0 times
...
Mable
19 days ago
The manual failover is definitely the effect of running that command. I remember learning about that in my Azure Cosmos DB training.
upvoted 0 times
...

Save Cancel