You are troubleshooting the current issues caused by the application updates. Which action can address the application updates issue without…

Bounded staleness is frequently chosen by globally distributed applications that expect low write

latencies but require total global order guarantee. Bounded staleness is great for applications

featuring group collaboration and sharing, stock ticker, publish-subscribe/queueing etc.

Scenario: Application updates in con-product frequently cause HTTP status code 429 "Too many

requests". You discover that the 429 status code relates to excessive request unit (RU) consumption

during the updates.

Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels