You have a container in an Azure Cosmos DB for NoSQL account. Data update volumes are unpredictable. You need to process the change feed of the container by using a web app that has multiple…

Question

Options

• AConfigure the same processor name for all the instances
• BConfigure a different processor name for each instance
• CConfigure a different instance name for each instance
• DConfigure a different lease container configuration for each instance
• EConfigure the same instance name for all the instances
• FConfigure the same lease container configuration for all the instances

• A
  72% (23)
• B
  16% (5)
• D
  6% (2)
• E
  6% (2)

Explanation

A: Implementing the change feed processor. The point of entry is always the monitored container, from a Container instance you call GetChangeFeedProcessorBuilder. C: You define the compute instance name or unique identifier with WithInstanceName, this should be unique and different in each compute instance you are deploying. F: The lease container: The lease container acts as a state storage and coordinates processing the change feed across multiple workers. The lease container can be stored in the same account as the monitored container or in a separate account. https://docs.microsoft.com/en-us/azure/cosmos-db/sql/change-feed-processor

No community discussion yet for this question.