DP-420 · Question #87
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…
The correct answer is B. No. Azure Stream Analytics supports Azure Cosmos DB for NoSQL natively as a reference data input - you can configure a Cosmos DB container directly as a reference data source in a Stream Analytics job without any intermediary. Creating an Azure Function to copy data to a second…
Question
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have a container named container1 in an Azure Cosmos DB Core (SQL) API account. You need to make the contents of container1 available as reference data for an Azure Stream Analytics job. Solution: You create an Azure function to copy data to another Azure Cosmos DB Core (SQL) API container. Does this meet the goal?
Exhibit
Options
- AYes
- BNo
How the community answered
(29 responses)- A31% (9)
- B69% (20)
Explanation
Azure Stream Analytics supports Azure Cosmos DB for NoSQL natively as a reference data input - you can configure a Cosmos DB container directly as a reference data source in a Stream Analytics job without any intermediary. Creating an Azure Function to copy data to a second Cosmos DB container is unnecessary, adds latency and complexity, and does not address the Stream Analytics reference data configuration requirement. The correct approach is to add a Cosmos DB reference input directly in the Stream Analytics job configuration.
Topics
Community Discussion
No community discussion yet for this question.
