Correct Answer: Bounded Staleness consistency
Bounded Staleness consistency guarantees that reads lag behind writes by at most a defined staleness window (time or number of operations). Configuring a 5-minute staleness bound g...
Correct Answer
Bounded Staleness consistency
Why This Answer Is Correct
Bounded Staleness consistency guarantees that reads lag behind writes by at most a defined staleness window (time or number of operations). Configuring a 5-minute staleness bound gives the marketing team low-latency global reads while ensuring data is never more than 5 minutes out of date.
This question evaluates your knowledge of Azure Cosmos DB — a core concept tested in Microsoft Certified: Azure Developer Associate (AZ-204). Understanding Azure Cosmos DB is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
You are designing a multi-tenant SaaS application using Azure Cosmos DB for NoSQL. Each tenant's data must be logically isolated and queries should never cross tenant boundaries. Query performance must be predictable. How should you partition the container?
You are designing a multi-tenant SaaS application where each tenant's data must be isolated and queries must be highly efficient for per-tenant reads. The application will have thousands of tenants. Which Cosmos DB partition key design is most appropriate?
You are developing a high-throughput shopping cart service using Azure Cosmos DB for NoSQL. The service needs to update a customer's shopping cart document by adding an item. To ensure high efficiency, minimize RU/s consumption, and prevent concurrent modification conflicts without loading the entire document first, which feature should you use?
You are building a microservices architecture. You need a data sync solution where changes to documents in your primary Azure Cosmos DB database automatically trigger a downstream search index service to update its records in real-time. Which Cosmos DB feature allows you to listen for changes without polling the database?