Question

A retail company stores order documents in an Azure Cosmos DB for NoSQL container. Compliance requires that once an order document reaches a 'Completed' status, a copy must be moved to Azure Blob Storage for long-term archival, and the archived record must never be lost even if processing fails temporarily. The team wants a serverless, low-maintenance approach that automatically reacts to changes. Which design best meets these requirements?

Accepted Answer

Deploy an Azure Function with a Cosmos DB trigger (change feed) that writes completed orders to Blob Storage, and rely on the lease container and built-in checkpointing/retry to guarantee each change is processed.

Answer

Schedule an Azure Function on a timer trigger every 5 minutes to query the container for completed orders and write them to Blob Storage.

Answer

Enable analytical store with Azure Synapse Link and run a nightly Spark job that exports completed orders to Blob Storage.

Answer

Configure a post-trigger on the container that writes each completed order directly to Blob Storage during the write operation.