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
Cosmos DB consistency defaults are account-wide. The SDK can override consistency per request to a level weaker than or equal to the account default, which is how a Session account can issue an Eventual read to reduce RU cost. Clients generally cannot strengthen a request above the account default. Changing the account default or recreating containers is unnecessary for a single dashboard query; after an account-level change, recreating SDK clients is a supporting operational note.