You have a container named container1 in an Azure Cosmos DB for NoSQL account named account1 that is set to the session default consistency level. The average size of an item in contained is 20 KB…

Question

Options

• AIn App1, modify the connection policy settings
• BIn App1, change the consistency level of read requests to consistent prefix
• CIn account1, provision a dedicated gateway and integrated cache
• DIn account1, change the default consistency level to bounded staleness

• A
  8% (4)
• B
  4% (2)
• C
  77% (41)
• D
  11% (6)

Explanation

The main goal of the integrated cache is to reduce costs for read-heavy workloads. Low latency, while helpful, is not the main benefit of the integrated cache because Azure Cosmos DB is already fast without caching. Point reads and queries that hit the integrated cache won't use any RUs. In other words, any cache hits will have an RU charge of 0. Cache hits will have a much lower per-operation cost than reads from the backend database. Workloads that fit the following characteristics should evaluate if the integrated cache will help - Read-heavy workloads - Many repeated point reads on large items - Many repeated high RU queries - Hot partition key for reads https://docs.microsoft.com/en-us/azure/cosmos-db/integrated-cache

No community discussion yet for this question.