DP-203 · Question #425
You have an Azure Blob storage account named storage1 and an Azure Synapse Analytics serverless SQL poo1 named Pool1. From Pool1, you plan to run ad-hoc queries that target storage1. You need to ensur
The correct answer is D. a database scoped credential. To use SAS tokens in OPENROWSET queries without defining an explicit external data source, a database-scoped credential containing the SAS token must be created first so Synapse serverless SQL can locate the credential automatically.
Question
You have an Azure Blob storage account named storage1 and an Azure Synapse Analytics serverless SQL poo1 named Pool1. From Pool1, you plan to run ad-hoc queries that target storage1. You need to ensure that you can use shared access signature (SAS) authorization without defining a data source. What should you create first?
Options
- Aa stored access policy
- Ba server-level credential
- Ca managed identity
- Da database scoped credential
How the community answered
(25 responses)- A4% (1)
- B12% (3)
- C4% (1)
- D80% (20)
Why each option
To use SAS tokens in OPENROWSET queries without defining an explicit external data source, a database-scoped credential containing the SAS token must be created first so Synapse serverless SQL can locate the credential automatically.
A stored access policy defines reusable constraints for SAS tokens at the storage account level but is not a Synapse SQL object and cannot be referenced directly by OPENROWSET for authorization.
A server-level credential applies to all databases on the server and is used for different scenarios such as managed identity authentication; it does not support SAS-based authorization for OPENROWSET without a data source.
A managed identity uses Azure AD-based authentication rather than SAS tokens and represents a different authorization mechanism entirely.
A database-scoped credential stores the SAS token at the database level in the serverless SQL pool. When a query targets a storage path without an explicit data source, Synapse serverless SQL automatically matches the storage URL against existing database-scoped credentials to apply the correct authorization, eliminating the need to define a separate external data source.
Concept tested: Synapse serverless SQL SAS authorization database-scoped credential
Source: https://learn.microsoft.com/en-us/azure/synapse-analytics/sql/develop-storage-files-storage-access-control
Topics
Community Discussion
No community discussion yet for this question.