Aggregation Persistence with Change Feed Quiz

5 questions Pass: 70% +25 pts (50 with Pro)

Quiz covering Change Feed Implementation

What you'll be asked

  1. Which Azure Cosmos DB feature is primarily used to trigger a function whenever a new document is inserted or an existing document is updated in a container?
  2. When implementing an aggregation pattern using the Change Feed, why is it recommended to use the Change Feed Processor library instead of manually polling the Change Feed API?
  3. You are building a real-time dashboard that displays the total count of orders. You decide to use the Change Feed to update a 'summary' document. What is the best strategy to handle concurrency when multiple instances of your processor update the same summary document?
  4. If your Change Feed processor crashes, how does it know where to resume processing after it restarts?
  5. You are aggregating data across multiple partitions into a single document. You notice that your Change Feed processor is falling behind during peak traffic. Which architectural change would most effectively improve throughput while maintaining data integrity?

Answers and explanations come after you submit.