Question

Your company runs an on-premises order processing system that publishes messages to Apache Kafka. You need to continuously ingest these Kafka messages into an Azure Cosmos DB for NoSQL container, and separately stream all document changes from a different Cosmos DB container back out to a downstream Kafka topic for analytics. You want to use the official Cosmos DB Kafka connectors with minimal custom code. Which configuration should you deploy?

Accepted Answer

Use the Cosmos DB sink connector to ingest Kafka messages into the container, and the Cosmos DB source connector (which reads the change feed) to publish document changes to the downstream Kafka topic.

Answer

Use the Cosmos DB source connector to ingest Kafka messages into the container, and the Cosmos DB sink connector to publish document changes to the downstream Kafka topic.

Answer

Use the Cosmos DB sink connector for both directions, configuring one instance to read and one to write.

Answer

Use Azure Data Factory copy activities in both directions since the Kafka connectors only support one-way movement from Cosmos DB to Kafka.