A utility provider is designing an analytical solution to monitor power grid telemetry. The solution must process daily load profile data stored as Apache Parquet files in Azure Data Lake Storage Gen2. Data analysts need to run ad-hoc, exploratory queries across these files to identify consumption anomalies. The solution must minimize administrative overhead, avoid persistent compute costs, and ensure that the analytical and underlying storage components survive a primary datacenter outage within the region. Which configuration should you recommend?
- Azure Synapse serverless SQL pool querying files in a Zone-Redundant Storage (ZRS) Azure Data Lake Storage Gen2 account using Microsoft Entra ID authenticationAnswer
- BAzure Synapse dedicated SQL pool querying files in a Zone-Redundant Storage (ZRS) Azure Data Lake Storage Gen2 account using PolyBase staging
- CAzure Synapse serverless SQL pool querying files in a Locally Redundant Storage (LRS) Azure Data Lake Storage Gen2 account
- DAzure Synapse serverless SQL pool accessing the storage account via a Shared Access Signature (SAS) token configured with a five-year validity period directly on the token URI
Answer
The configuration using an Azure Synapse serverless SQL pool to query files in a Zone-Redundant Storage (ZRS) Azure Data Lake Storage Gen2 account using Microsoft Entra ID authentication.
The correct configuration uses an Azure Synapse serverless SQL pool to query the Parquet files in a Zone-Redundant Storage (ZRS) Azure Data Lake Storage Gen2 account. Serverless SQL pools require zero setup and charge only for the data processed, which eliminates persistent compute costs and minimizes administrative overhead. Zone-Redundant Storage replicates data across three separate physical datacenters within the region, ensuring survival of a primary datacenter outage.
Step-by-Step Solution
Key Concept
Selecting the appropriate analytical query engine and storage redundancy model based on cost, management overhead, and resilience requirements.
Estimated Time:1m 30s