DP-420 · Question #30
You have an Azure Cosmos DB Core (SQL) API account that is used by 10 web apps. You need to analyze the data stored in the account by using Apache Spark to create machine learning models. The…
The correct answer is A. In an Apache Spark pool in Azure Synapse, create a table that uses cosmos.olap as the data D. Enable Azure Synapse Link for the account and Analytical store on the container. The correct answers are A and D. First (D), you must enable Azure Synapse Link on the Cosmos DB account and enable the Analytical Store on the container. Synapse Link creates a fully isolated, automatically synced columnar analytical store that operates separately from the…
Question
You have an Azure Cosmos DB Core (SQL) API account that is used by 10 web apps. You need to analyze the data stored in the account by using Apache Spark to create machine learning models. The solution must NOT affect the performance of the web apps. Which two actions should you perform? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
Exhibit
Options
- AIn an Apache Spark pool in Azure Synapse, create a table that uses cosmos.olap as the data
- BCreate a private endpoint connection to the account.
- CIn an Azure Synapse Analytics serverless SQL pool, create a view that uses OPENROWSET and
- DEnable Azure Synapse Link for the account and Analytical store on the container.
- EIn an Apache Spark pool in Azure Synapse, create a table that uses cosmos.oltp as the data
How the community answered
(26 responses)- A73% (19)
- B8% (2)
- C15% (4)
- E4% (1)
Explanation
The correct answers are A and D. First (D), you must enable Azure Synapse Link on the Cosmos DB account and enable the Analytical Store on the container. Synapse Link creates a fully isolated, automatically synced columnar analytical store that operates separately from the transactional store - so analytical queries never consume transactional RUs and do not impact the web apps. Then (A), in Azure Synapse, create a Spark table using cosmos.olap as the data source format, which reads from the analytical store (OLAP path). Option E uses cosmos.oltp, which reads from the transactional store and would consume RUs impacting web apps. Option C (serverless SQL pool with OPENROWSET) reads the transactional store. Option B (private endpoint) is a networking feature unrelated to performance isolation.
Topics
Community Discussion
No community discussion yet for this question.
