DP-203 · Question #351
You have an Azure subscription that contains an Azure Synapse Analytics workspace named ws1 and an Azure Cosmos DB database account named Cosmos1. Cosmos1 contains a container named container1 and…
The correct answer is A. Enable Azure Synapse Link for Cosmos1. C. In ws1, create a linked service that references Cosmos1. D. Enable the analytical store for container1. To query Cosmos DB data from a Synapse serverless SQL pool, you must first enable Azure Synapse Link on the Cosmos DB account (A) - this is the account-level feature that bridges the two services. Next, enable the analytical store on the specific container (D) - this activates…
Question
You have an Azure subscription that contains an Azure Synapse Analytics workspace named ws1 and an Azure Cosmos DB database account named Cosmos1. Cosmos1 contains a container named container1 and ws1 contains a serverless SQL pool. You need to ensure that you can query the data in container1 by using the serverless SQL pool. Which three actions should you perform? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
Options
- AEnable Azure Synapse Link for Cosmos1.
- BDisable the analytical store for container1.
- CIn ws1, create a linked service that references Cosmos1.
- DEnable the analytical store for container1.
- EDisable indexing for container1.
How the community answered
(24 responses)- A79% (19)
- B13% (3)
- E8% (2)
Explanation
To query Cosmos DB data from a Synapse serverless SQL pool, you must first enable Azure Synapse Link on the Cosmos DB account (A) - this is the account-level feature that bridges the two services. Next, enable the analytical store on the specific container (D) - this activates the column-store copy of data that Synapse reads without impacting transactional workloads. Finally, create a linked service in ws1 referencing Cosmos1 (C) - this registers the connection so the serverless SQL pool knows how to reach it via OPENROWSET.
Why the distractors fail: Option B (disable analytical store) is the opposite of what's needed - the analytical store must be on. Option E (disable indexing) has no bearing on Synapse Link connectivity and would actually harm Cosmos DB query performance for its own transactional workloads.
Memory tip: Think of it as a 3-step handshake - Account (Synapse Link on), Container (analytical store on), Workspace (linked service created). All three levels must be wired up before data flows.
Topics
Community Discussion
No community discussion yet for this question.