Correct Answer: Cosmos DB Change Feed, integrated with an Azure Function (Cosmos DB Trigger).
The Cosmos DB Change Feed listens to the container for any changes (inserts and updates) and outputs a sorted list of documents that were modified. Integrating the Change Feed with...
Correct Answer
Cosmos DB Change Feed, integrated with an Azure Function (Cosmos DB Trigger).
Why This Answer Is Correct
The Cosmos DB Change Feed listens to the container for any changes (inserts and updates) and outputs a sorted list of documents that were modified. Integrating the Change Feed with the Cosmos DB Trigger in Azure Functions provides a serverless, event-driven, sub-second latency synchronization layer with zero polling overhead.
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?
Your application reads Azure Cosmos DB data globally across three regions. The marketing team needs data to eventually be the same across all regions, and can tolerate reading slightly stale data (up to 5 minutes old) in exchange for lower latency reads. Which consistency level should you configure?
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?