Your current bot application in Azure has LUIS integration. You are tasked to identify where the Natural Language Processing has failed or can be improved for your global user base across multiple geographies. You also have the requirement to analyze sentiment and user metrics. To achieve this objective, you decide to log and store the conversation data in Azure. For prototyping, you use in-memory storage. However, now that you have rolled out the solution for production use, you need to decide which storage solution to use for storing conversation data. 
Given the scenario above, choose the most appropriate data store.

Answer options:

A.Azure Blob
B.SQL managed instance
C.CosmosDB
D.Table Storage

Correct Answer: C
Option A is incorrect. Currently, the user state supports in-memory, CosmosDB, SQL, and Table storage for storing user states. Hence, this answer choice is not correct.
Option B is incorrect. SQL managed instance, even though supported, is not the optimal choice to support multiple geographies. Cosmos DB is suited to support multiple geographies.
Option C is correct. It is an ideal choice as the conversation state is stored in JSON documents. Cosmos DB, being a NoSQL document database, is suited to support this scenario. It supported multiple geographies. CosmosDB also offers scalability, low latency, and high availability. You can perform the analytics functions on CosmosDB to get metrics around LUIS failures and sentiments.
Option D is incorrect. Azure Table Storage, even though supported, is not the optimal choice to support multiple geographies. Cosmos DB is suited to support multiple geographies.
Reference:
To learn more about storing state data for your bot using CosmosDB, use the link given below: 

https://docs.microsoft.com/en-us/previous-versions/azure/bot-service/dotnet/bot-builder-dotnet-state-azure-cosmosdb?view=azure-bot-service-3.0