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 2 Question 58 Discussion

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

You have a container in an Azure Cosmos DB Core (SQL) API account. The container stores telemetry data from IoT devices. The container uses telemetryId as the partition key and has a throughput of 1,000 request units per second (RU/s). Approximately 5,000 IoT devices submit data every five minutes by using the same telemetryId value.

You have an application that performs analytics on the data and frequently reads telemetry data for a single IoT device to perform trend analysis.

The following is a sample of a document in the container.

You need to reduce the amount of request units (RUs) consumed by the analytics application.

What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Sueann at Feb 08, 2025, 12:23 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Buck
20 days ago
Ah, the joys of Azure Cosmos DB! Where the partition keys are made up and the RUs don't matter. Just toss some more money at it, and all your problems will go away. Truly the cloud equivalent of turning it off and on again.
upvoted 0 times
...
Shad
22 days ago
B is the way to go! Increasing the throughput is the easiest solution, and it will just cost you more money. Why bother with all this partition key nonsense when you can just throw more RUs at the problem?
upvoted 0 times
...
Jeff
28 days ago
Hmm, I'm leaning towards D. Partitioning by date sounds like a more natural fit for time-series data like this. Plus, it might make it easier to manage the data in the long run.
upvoted 0 times
Tatum
15 days ago
Moving the data to a new container with a partition key of date could definitely help reduce the RUs consumed.
upvoted 0 times
...
Huey
21 days ago
I think D is a good choice too. It can help optimize the queries for trend analysis based on date.
upvoted 0 times
...
...
Edison
1 months ago
I'm not sure about that. Wouldn't partitioning by date be better? That way, the application can easily access data for a specific time period, which could be useful for trend analysis.
upvoted 0 times
Talia
1 months ago
Partitioning by date could be a good idea for trend analysis.
upvoted 0 times
...
...
Justa
2 months ago
That's an interesting idea. It could help reduce the RUs consumed by the analytics application.
upvoted 0 times
...
Shonda
2 months ago
I disagree, I believe we should move the data to a new container that has a partition key of deviceId.
upvoted 0 times
...
Ruth
2 months ago
Choosing C seems like the best option here. Partitioning the data by deviceId will allow the analytics application to read data for a single IoT device more efficiently, reducing the RUs consumed.
upvoted 0 times
Ashleigh
9 days ago
Let's go with option C then. It seems like the most efficient solution.
upvoted 0 times
...
Tammy
14 days ago
Moving the data to a new container with deviceId as the partition key sounds like the way to go.
upvoted 0 times
...
Nancey
1 months ago
Agreed, partitioning by deviceId will definitely reduce the RUs consumed.
upvoted 0 times
...
Lashonda
1 months ago
I think option C is the best choice. It will help optimize the analytics application.
upvoted 0 times
...
...
Justa
2 months ago
I think we should decrease the offerThroughput value for the container.
upvoted 0 times
...

Save Cancel