A cliff-rail timetable site needs each clerk to see their own writes while the Cosmos account stays on the service default. Which consistency level should the developer name?
Select an answer to reveal the explanation.
Short Explanation
Clerks need read-your-writes after a save—not a global fortress. Session is the Cosmos default for that feel inside one session, usually via a session token. Do not jump straight to Strong for every screen.
Full Explanation
Session consistency is the default Cosmos DB account consistency level and is the typical choice for interactive user sessions that require read-your-writes and write-follows-reads within a session. Strong is stronger and costlier; Eventual is weaker and does not guarantee read-your-writes; Bounded staleness uses K versions or T time and is not “Strong with K=0.” The session token is the supporting client mechanism.