How to Configure Spark Pool Access to External Data Lake Storage?
You have an Azure subscription that contains an Azure Data Lake Storage account named dl1 and an Azure Analytics Synapse workspace named workspace1. You need to query the data in dl1 by using an Apache Spark pool named Pool1 in workspace1. The solution must ensure that the data is accessible Pool1. Which two actions achieve the goal? Each correct answer presents a complete solution. NOTE: Each correct answer is worth one point.
Community Votes
100% of anonymous learners picked answer BC. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
It tests how to grant Spark pool access to external ADLS Gen2 storage, commonly confused with governance tools like Microsoft Purview or unrelated features like Synapse Link.
This question tests configuring external data access for Azure Synapse Spark pools, with the community consensus confirming that linking the Data Lake Storage as a managed service or setting it as primary storage are required steps.
Option D (Microsoft Purview) is frequently chosen incorrectly because candidates assume registering a data source enables access, but Purview only handles metadata, lineage, and governance, not runtime connectivity.
Community Discussion (6 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option B and C correctly address how an Azure Synapse Spark pool accesses external storage. Configuring the Data Lake Storage account as the workspace’s primary storage automatically mounts it to the Spark cluster, granting immediate read/write permissions. Alternatively, creating a linked service establishes a secure, authenticated connection endpoint that Pool1 can reference to query dl1 without duplicating data. Both methods satisfy the requirement for runtime accessibility.Why the Other Options Are Wrong
Option A is incorrect because Azure Synapse Link specifically integrates Azure Cosmos DB with Synapse for analytical processing, not ADLS Gen2. Option D is a frequent distractor; Microsoft Purview is strictly a data governance and cataloging tool that tracks lineage and metadata. Registering a datastore in Purview does not provision compute resources or configure authentication for Spark jobs to actually read the files.Community Comment Notes
Candidates overwhelmingly selected BC, aligning with official Microsoft guidance. Comment [1] correctly points out that Purview handles lineage tracking rather than access control, and cites the official troubleshooting documentation for Spark storage access. Comment [2] reinforces that governance tools do not enable compute-to-storage connectivity. The consensus confirms that linking or mounting the storage account is the only viable path for Spark pool access.Official Reference
- https://learn.microsoft.com/en-us/troubleshoot/azure/synapse-analytics/spark/spark-jobexec-storage-access#common-issues-and-solutions
- https://learn.microsoft.com/en-us/azure/synapse-analytics/security/workspace-manage-linked-services
- https://learn.microsoft.com/en-us/azure/data-factory/concepts-linked-services
Exam Strategy
Focus on distinguishing between data connectivity configurations and data governance tools when designing Azure Synapse solutions. Always verify whether a requirement involves runtime compute access versus metadata tracking before selecting options involving Purview or cataloging services.