A rope-bridge inspection feed must include deletes and intermediate item versions from Cosmos DB. Which change feed configuration should the developer select?
Select an answer to reveal the explanation.
Short Explanation
Need every draft and the shredder events? Flip to all-versions-and-deletes—and know continuous backup is the ticket that unlocks it. Latest-version alone will not show those deletes.
Full Explanation
A rope-bridge inspection feed that must include deletes and intermediate item versions from Cosmos DB should use all-versions-and-deletes mode. That change feed mode surfaces create, update, and delete operations—including intermediate versions—rather than only the latest surviving document shape. Officially, all-versions-and-deletes requires continuous backup on the account, so backup policy and feed mode must be planned together.
Latest-version mode with only periodic container backups will not deliver delete notifications or full intermediate version history the way all-versions-and-deletes does. A timer trigger that avoids soft-deletes and simply reads under Strong consistency still polls current state; it is not the change feed configuration that emits deletes and version history. Overriding Session consistency on each DeleteItem call does not change which change feed mode is active or unlock delete events in latest-version mode.
Exam caveat: continuous backup is a prerequisite for all-versions-and-deletes—not an optional nice-to-have. Accounts on periodic backup need a backup policy change before this feed mode is available.
Operational check: verify continuous backup is enabled, configure the inspection consumer for all-versions-and-deletes, perform an update then a delete on a test item, and assert the consumer receives both the intermediate version and the delete notification.