New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft DP-420 Exam - Topic 1 Question 66 Discussion

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

You have an application named App1 that reads the data in an Azure Cosmos DB Core (SQL) API account. App1 runs the same read queries every minute. The default consistency level for the account is set to eventual.

You discover that every query consumes request units (RUs) instead of using the cache.

You verify the IntegratedCacheiteItemHitRate metric and the IntegratedCacheQueryHitRate metric. Both metrics have values of 0.

You verify that the dedicated gateway cluster is provisioned and used in the connection string.

You need to ensure that App1 uses the Azure Cosmos DB integrated cache.

What should you configure?

Show Suggested Answer Hide Answer
Suggested Answer: C

Because the integrated cache is specific to your Azure Cosmos DB account and requires significant CPU and memory, it requires a dedicated gateway node. Connect to Azure Cosmos DB using gateway mode.


Contribute your Thoughts:

0/2000 characters
Evangelina
3 months ago
The default consistency level is already set to eventual, so that shouldn't be the issue.
upvoted 0 times
...
Michael
3 months ago
I agree, that makes the most sense for caching!
upvoted 0 times
...
Rikki
3 months ago
I thought the integrated cache would work automatically, this is surprising!
upvoted 0 times
...
Melissa
3 months ago
Wait, are you sure it’s not about the consistency level?
upvoted 0 times
...
Melissa
3 months ago
You need to configure the connectivity mode of the App1 CosmosClient.
upvoted 0 times
...
Lucy
4 months ago
I thought the default consistency level could impact performance, but I’m not confident if it would affect the integrated cache usage.
upvoted 0 times
...
Shonda
4 months ago
I feel like the indexing policy isn't related to the cache directly, but I can't recall exactly why.
upvoted 0 times
...
King
4 months ago
I think we practiced a similar question where adjusting the connectivity mode made a difference. Maybe that's the key here?
upvoted 0 times
...
Taryn
4 months ago
I remember reading about the integrated cache, but I'm not sure if changing the consistency level would help with the cache hit rate.
upvoted 0 times
...
Emiko
4 months ago
I'm a bit confused here. The question mentions the default consistency level is set to "eventual", but I'm not sure if that's related to the cache issue. Maybe we need to look at the consistency level settings as well.
upvoted 0 times
...
Gregoria
5 months ago
I'm pretty confident this has to do with the connectivity mode of the CosmosClient. The question states the dedicated gateway cluster is provisioned, so I'm guessing we need to set the connectivity mode to "Gateway" to utilize the cache.
upvoted 0 times
...
Reita
5 months ago
Okay, let's see. The question mentions that the queries are consuming request units instead of using the cache, and the cache metrics are both 0. I think the key is to figure out how to enable the cache.
upvoted 0 times
...
Eloisa
5 months ago
Hmm, this seems like a tricky one. I'll need to carefully review the details about the Azure Cosmos DB integrated cache and how to configure it.
upvoted 0 times
...
Launa
7 months ago
D) the default consistency level of the Azure Cosmos DB account seems like the right choice. If the consistency level is set to eventual, that could be preventing the cache from being used effectively.
upvoted 0 times
...
Luis
7 months ago
I think the answer is C) the connectivity mode of the App1 CosmosClient. If the cache is not being used, the connectivity mode may need to be changed to allow for caching.
upvoted 0 times
Marcos
6 months ago
C) the connectivity mode of the App1 CosmosClient
upvoted 0 times
...
Tyra
7 months ago
B) the consistency level of the requests from App1
upvoted 0 times
...
Rosita
7 months ago
A) the indexing policy of the Azure Cosmos DB container
upvoted 0 times
...
...

Save Cancel