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 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
Suggested Answer: B

You can use the Set-AzCosmosDBAccountRegion cmdlet to update the regions that an Azure Cosmos DB account uses. You can use this cmdlet to add a region or change the region failover order.The cmdlet requires a resource group name, an Azure Cosmos DB account name, and a list of regions in desired failover order1.

For your scenario, based on the PowerShell command, you are using the Set-AzCosmosDBAccountRegion cmdlet to update the regions for an Azure Cosmos DB account named account1 that is configured for automatic failover. The command specifies two regions: West US and East US. The effect of running the command is thatthe account will be configured for multi-region writes.

Multi-region writes is a feature of Azure Cosmos DB that allows you to write data to any region in your account and have it automatically replicated to all other regions. This feature provides high availability and low latency for write operations across multiple regions.To enable multi-region writes, you need to specify at least two regions in your account and set them as write regions2. In your command, you are setting both West US and East US as write regions by using the -IsZoneRedundant parameter with a value of $true for both regions.


by Ceola at Mar 19, 2025, 06:13 PM

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
Karan
5 months ago
Wait, isn't using deviceId alone enough? Not sure about the random number.
upvoted 0 times
...
Nobuko
5 months ago
I think option D is the best choice! Random number helps distribute writes.
upvoted 0 times
...
Skye
5 months ago
Synthetic keys are a smart move here. DeviceId + sensor value sounds solid.
upvoted 0 times
...
Carman
5 months ago
Definitely avoid timestamp; it creates skew with frequent writes.
upvoted 0 times
...
Lili
5 months ago
Using timestamp as a partition key can lead to hot partitions.
upvoted 0 times
...
Aleta
6 months ago
I recall a practice question where we used a combination of deviceId and another attribute. Maybe deviceId with deviceManufacturer could work, but I need to think more about the write patterns.
upvoted 0 times
...
Candra
6 months ago
I feel like using deviceId with a random number could be a good option to minimize partition skew, but I wonder if it would really help with avoiding hot partitions.
upvoted 0 times
...
Ruth
6 months ago
I think creating a synthetic key with deviceId and sensor1Value could help distribute the writes better, but I'm not entirely sure if it would avoid capacity limits.
upvoted 0 times
...
Nakisha
6 months ago
I remember we discussed partition keys in class, and using a timestamp might lead to hot partitions since all writes would cluster around the same time.
upvoted 0 times
...
Naomi
6 months ago
Using deviceId and sensor1Value seems like a good way to distribute the writes evenly and avoid capacity limits. I think that's the way to go.
upvoted 0 times
...
Ria
7 months ago
I'm a bit confused on the best approach here. Timestamp might work, but I'm not sure if it would avoid hot partitions. I'll need to review the requirements again.
upvoted 0 times
...
Launa
7 months ago
Okay, let's see. Minimizing partition skew and avoiding hot partitions are key. I'm leaning towards using a synthetic key with deviceId and a random number.
upvoted 0 times
...
Romana
7 months ago
Hmm, this seems like a tricky one. I'll need to think carefully about the partition key requirements.
upvoted 0 times
...
Lai
12 months ago
I guess the partition key should be the 'DeviceID' and the 'Sensor Value'... you know, to keep things 'well-partitioned'!
upvoted 0 times
Brynn
10 months ago
D) Create a new synthetic key that contains deviceId and a random number.
upvoted 0 times
...
Arlyne
10 months ago
C) Create a new synthetic key that contains deviceId and deviceManufacturer.
upvoted 0 times
...
Josephine
10 months ago
B) Create a new synthetic key that contains deviceId and sensor1Value.
upvoted 0 times
...
Wilbert
11 months ago
A) Use timestamp as the partition key.
upvoted 0 times
...
...
Isreal
12 months ago
Using a synthetic key that includes deviceId and a random number is a creative approach, but it could make it harder to query the data later on.
upvoted 0 times
Allene
10 months ago
I agree, using sensor1Value in the synthetic key can help distribute the data evenly.
upvoted 0 times
...
Thomasena
10 months ago
That sounds like a good option to avoid hot partitions.
upvoted 0 times
...
Jospeh
11 months ago
B) Create a new synthetic key that contains deviceId and sensor1Value.
upvoted 0 times
...
...
Kerry
1 year ago
The option to create a synthetic key with deviceId and deviceManufacturer is interesting, but it might not be the best choice as it may not minimize the partition skew.
upvoted 0 times
Veronika
11 months ago
C) Create a new synthetic key that contains deviceId and deviceManufacturer.
upvoted 0 times
...
Cory
11 months ago
B) Create a new synthetic key that contains deviceId and sensor1Value.
upvoted 0 times
...
Bulah
12 months ago
A) Use timestamp as the partition key.
upvoted 0 times
...
...
Marylin
1 year ago
Creating a synthetic key that includes the deviceId and sensor1Value sounds promising, as it would distribute the data more evenly and avoid hot partitions.
upvoted 0 times
Charisse
11 months ago
Creating a synthetic key with a random number might not evenly distribute the data.
upvoted 0 times
...
Coletta
12 months ago
Timestamp might not be the best choice as it could lead to hot partitions.
upvoted 0 times
...
France
12 months ago
Using a synthetic key with deviceId and sensor1Value could help with that.
upvoted 0 times
...
Hoa
1 year ago
Sensors data should be evenly distributed to avoid hot partitions.
upvoted 0 times
...
...
Dominga
1 year 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
Juan
12 months ago
C) Create a new synthetic key that contains deviceId and deviceManufacturer.
upvoted 0 times
...
Corazon
1 year ago
B) Create a new synthetic key that contains deviceId and sensor1Value.
upvoted 0 times
...
...
Tamar
1 year 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
1 year ago
I agree with Angella, using timestamp as the partition key will help minimize partition skew.
upvoted 0 times
...
Belen
1 year ago
That's a good point, but I still think D is the correct answer based on the command.
upvoted 0 times
...
Tyra
1 year 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
Artie
11 months ago
D) Create a new synthetic key that contains deviceId and a random number.
upvoted 0 times
...
Candra
11 months ago
C) Create a new synthetic key that contains deviceId and deviceManufacturer.
upvoted 0 times
...
Amira
11 months ago
B) Create a new synthetic key that contains deviceId and sensor1Value.
upvoted 0 times
...
Sheridan
11 months ago
A) Use timestamp as the partition key.
upvoted 0 times
...
Lyla
11 months ago
D) Create a new synthetic key that contains deviceId and a random number.
upvoted 0 times
...
Casey
11 months ago
C) Create a new synthetic key that contains deviceId and deviceManufacturer.
upvoted 0 times
...
Taryn
12 months ago
B) Create a new synthetic key that contains deviceId and sensor1Value.
upvoted 0 times
...
Franklyn
1 year ago
A) Use timestamp as the partition key.
upvoted 0 times
...
...
Lyndia
1 year ago
Haha, multi-region writes? In your dreams! This is a simple failover command, not some advanced configuration.
upvoted 0 times
...
Angella
1 year ago
I think we should use timestamp as the partition key to avoid hot partitions.
upvoted 0 times
...
Francisca
1 year ago
But wouldn't that also mean that the account will be unavailable for writes during the change?
upvoted 0 times
...
Solange
1 year 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
1 year 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
1 year 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
Kasandra
12 months ago
C) Create a new synthetic key that contains deviceId and deviceManufacturer.
upvoted 0 times
...
Shaquana
12 months ago
B) Create a new synthetic key that contains deviceId and sensor1Value.
upvoted 0 times
...
Ty
12 months ago
A) Use timestamp as the partition key.
upvoted 0 times
...
...

Save Cancel