A windmill bakery Cosmos account defaults to Session, but one dashboard query can tolerate Eventual to save RU. How should the developer apply that weaker setting?
Select an answer to reveal the explanation.
Short Explanation
Do not rewire the whole bakery for one cheap dashboard glance. Keep Session on the account and ask for Eventual on that one request—overrides go weaker, not stronger. One screen should not force an account-wide flip.
Full Explanation
A windmill bakery Cosmos account that defaults to Session can still issue a cheaper Eventual read for one dashboard query by overriding consistency on that single request to a weaker level. Cosmos account defaults apply broadly, but the SDK allows per-request consistency as long as the requested level is weaker than or equal to the account default. Keeping Session for clerk writes while dialing one tolerant dashboard read to Eventual saves RUs without rewiring the bakery.
Changing the account default to Eventual weakens every clerk write and interactive read, which over-solves a one-query optimization. Raising only that request to Strong is generally not allowed: clients cannot strengthen a request above the account default. Deleting and recreating the container each time the dashboard opens is operationally destructive and unrelated to consistency overrides.
Exam caveat: overrides go weaker (or equal), not stronger. If a screen truly needs Strong, the account default must already be Strong (and multi-region writes must not be enabled).
Operational check: leave the account on Session, pass Eventual on the dashboard FeedIterator or point-read options, compare RU charges to an identical Session read, and after any future account-level consistency change recreate or refresh SDK clients so they pick up the new default.