Question

A retail application uses an Azure Cosmos DB dedicated gateway with the integrated cache enabled to serve a product catalog. The catalog is updated a few times per hour, but the team is willing to serve slightly stale data to maximize cache hits and reduce RU consumption on repeated reads. Currently, every read request is configured with the default MaxIntegratedCacheStaleness of 5 minutes, but the team wants cached entries to remain valid for up to 30 minutes to further cut costs. Which action correctly achieves this while ensuring the cache is actually used?

Accepted Answer

Set the MaxIntegratedCacheStaleness request option to 30 minutes on the read requests and route them through the dedicated gateway connection string.

Answer

Increase the dedicated gateway instance size so the cache holds entries longer, keeping the default staleness setting.

Answer

Change the account default consistency to eventual, which automatically extends the integrated cache retention to 30 minutes.

Answer

Set MaxIntegratedCacheStaleness to 30 minutes but continue using the direct-mode connection string for lowest latency.