exam questions

Exam DP-200 All Questions

View all questions & answers for the DP-200 exam

Exam DP-200 topic 4 question 3 discussion

Actual exam question from Microsoft's DP-200
Question #: 3
Topic #: 4
[All DP-200 Questions]

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You have a container named Sales in an Azure Cosmos DB database. Sales has 120 GB of data. Each entry in Sales has the following structure.

The partition key is set to the OrderId attribute.
Users report that when they perform queries that retrieve data by ProductName, the queries take longer than expected to complete.
You need to reduce the amount of time it takes to execute the problematic queries.
Solution: You increase the Request Units (RUs) for the database.
Does this meet the goal?

  • A. Yes
  • B. No
Show Suggested Answer Hide Answer
Suggested Answer: A 🗳️
To scale the provisioned throughput for your application, you can increase or decrease the number of RUs at any time.
Note: The cost of all database operations is normalized by Azure Cosmos DB and is expressed by Request Units (or RUs, for short). You can think of RUs per second as the currency for throughput. RUs per second is a rate-based currency. It abstracts the system resources such as CPU, IOPS, and memory that are required to perform the database operations supported by Azure Cosmos DB.
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/request-units

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Alekx42
4 years ago
I think "no" should be the answer. As said in the CosmosDB doc, "The same query on the same data will always costs the same number of RUs on repeated executions". If the query needs more RU than the ones availabile, the request is rate-limited and will have to be tried again. In this case we have queries that are consistently slow but are not being rate-limite, which means that the number of RU already provisioned is enough. Increasing the RU only ensures that more queries can be executed at the same time, but does not improve the performance of the slow queries. Source: https://docs.microsoft.com/en-us/azure/cosmos-db/request-units
upvoted 3 times
...
memo43
4 years ago
increase RU and lookupcollection are 2 possible answers. So; answer is CORRECT
upvoted 4 times
...
hoangton
4 years ago
The better solution should have index on ProductName
upvoted 3 times
...
suman13
4 years, 2 months ago
answer is wrong. we should use lookupcollection on ProductName.
upvoted 2 times
Pairon
4 years, 1 month ago
I disagree. Having a look up collection is another correct option, but increasing RUs could be another way to reduce latency, IMHO.
upvoted 11 times
...
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...