Question

Difficulty: EasyData Integration and Analytical Storage

A logistics organization stores historical delivery logs in CSV format within an Azure Data Lake Storage Gen2 account. You need to design an analytical query solution that enables data analysts to run occasional, ad-hoc SQL queries on these files. The solution must meet the following requirements:
- Minimize costs by utilizing a pay-per-query model rather than provisioning persistent database compute resources.
- Ensure the underlying storage account can survive a primary datacenter outage.
- Ensure that the shared access signatures (SAS) used for external analyst access can be revoked immediately if compromised.

Which solution should you recommend?

  1. Use a Synapse serverless SQL pool, store the logs in a geo-redundant storage (GRS) account, and grant access using SAS tokens defined with a stored access policy.Answer
  2. B
    Use a Synapse dedicated SQL pool, store the logs in a geo-redundant storage (GRS) account, and grant access using SAS tokens defined with a stored access policy.
  3. C
    Use a Synapse serverless SQL pool, store the logs in a locally redundant storage (LRS) account, and grant access using SAS tokens defined with a stored access policy.
  4. D
    Use a Synapse serverless SQL pool, store the logs in a geo-redundant storage (GRS) account, and grant access using SAS tokens generated directly without a stored access policy.

Answer

Use a Synapse serverless SQL pool, store the logs in a geo-redundant storage (GRS) account, and grant access using SAS tokens defined with a stored access policy.
The correct solution uses a Synapse serverless SQL pool, which operates on a pay-per-query model and does not require provisioning persistent compute resources. It stores data in a geo-redundant storage (GRS) account to survive a primary datacenter outage, and uses SAS tokens defined with a stored access policy to allow immediate revocation of access permissions if compromised.

Step-by-Step Solution

1
Select the query model based on workload type and budget constraints.
Choose Synapse serverless SQL pool.
Since the queries are occasional and ad-hoc, a serverless pool charges per query and avoids provisioned compute costs.
2
Select the storage redundancy option to protect against datacenter outages.
Choose Geo-Redundant Storage (GRS).
GRS replicates data to a secondary region, ensuring survival during a primary datacenter outage, unlike LRS.
3
Select the SAS configuration that allows revocation.
Use SAS tokens linked to a stored access policy.
A stored access policy allows immediate revocation of associated tokens by changing the policy configuration or deleting it.

Key Concept

Selecting serverless SQL pools for ad-hoc queries, selecting GRS for regional resilience, and utilizing stored access policies for revocable SAS tokens.
Rate this question