A peat-bog research kiosk writes a sample id to Cosmos DB and must immediately read that same committed value from another region for a printed label. Which consistency level should the developer choose?
Select an answer to reveal the explanation.
Short Explanation
When the printer must stamp what just got written, you want the latest committed write—not a maybe-yesterday copy. That is Strong consistency: linearizable reads of the newest commit. Reminder: Strong does not pair with multi-region writes.
Full Explanation
Strong consistency provides linearizability so a read returns the most recent committed write across regions configured for that guarantee. Eventual can lag; Consistent prefix targets ordered visibility of batched writes rather than cross-region immediacy for every single write; Session relies on a session token for read-your-writes within one client session. Official docs also note Strong is incompatible with multi-region write accounts.