Home › Azure AZ-204 › cloudcomputing › az204storage › Cosmos DB's Change Feed emits document changes i…
Cosmos DB's Change Feed emits document changes in order. Which scenario is its CANONICAL use case?
AEncrypt data at rest
BReplace Cosmos's primary query interface
CProvide a synchronous transaction log accessible to clients
DDrive downstream processors (materialised views, ETL into Synapse, real-time analytics) reactively to Cosmos changes
Answer & Solution
Correct answer: D. Drive downstream processors (materialised views, ETL into Synapse, real-time analytics) reactively to Cosmos changes
Change Feed is for downstream reactive consumers — materialised views, event publishing, ETL. It's not a transaction log API, not encryption, not the primary query path.
Related questions
An app must encrypt user-uploaded blobs using a key the customer controls, rotates, and auWhich Azure storage feature lets you fire an Azure Function when a new blob is uploaded?What is the trade-off when using Cosmos DB session consistency (the default)?Which Cosmos DB feature lets a single container handle a sudden 10x traffic burst WITHOUT Which Azure storage feature continuously replicates blobs to a paired region for region-diWhich Azure storage feature lets you grant a client temporary download access to a specifiWhich Cosmos DB concept determines the physical sharding strategy — how documents are distWhat is Cosmos DB's consistency model that guarantees clients see writes in the same globa