Hard1 markMultiple Choice
Domain 2.4: Non-Relational Data StorageDomain 2Cosmos DBConsistency LevelsGlobal Distribution

AZ-305 · Question 27 · Domain 2.4: Non-Relational Data Storage

You are designing a globally distributed application using Azure Cosmos DB. The database is replicated across 4 regions.

The application is a social media feed. When a user posts an update, it is critical that the user immediately sees their own post. However, it is acceptable if users in other regions see the post with a slight delay. You want to maximize read throughput and minimize latency.

Which Cosmos DB consistency level should you recommend?

Answer options:

A.

Strong

B.

Bounded Staleness

C.

Session

D.

Eventual

How to approach this question

Identify the consistency level that specifically guarantees 'read-your-own-writes'.

Full Answer

C.Session✓ Correct
Session
Session consistency is the most widely used consistency level for globally distributed applications. It provides 'read-your-own-writes' guarantees, meaning a user will always see the data they just wrote during their session. For other users outside that session, the data is eventually consistent. This perfectly matches the social media feed scenario, providing low latency and high throughput while meeting the specific user experience requirement.

Common mistakes

Choosing Strong consistency. While Strong guarantees the user sees their post, it forces synchronous replication across all 4 regions, severely degrading latency and throughput.

Practice the full Azure Solutions Architect Expert AZ-305 Practice Exam 2

55 questions · hints · full answers · grading

More questions from this exam