A media company stores user activity logs in Azure Data Lake Storage (ADLS) Gen2 in CSV format. You need to design an analytical solution to meet the following requirements:
- Storage Volume: of historical CSV log files.
- Ingestion Velocity: Logs are uploaded hourly at a rate of per hour.
- Query Pattern: Data analysts perform ad-hoc, exploratory queries intermittently to identify user trends.
- Query Latency: Response times of up to seconds are acceptable.
- Resiliency: The analytical data must survive a primary datacenter outage within the region.
- Cost: Minimize compute cost when no queries are running.
Which combination of storage redundancy and query engine should you configure?
- Configure ADLS Gen2 with Geo-Redundant Storage (GRS) and use Azure Synapse Analytics Serverless SQL pools to query the CSV files.Answer
- BConfigure ADLS Gen2 with Locally Redundant Storage (LRS) and use Azure Synapse Analytics Serverless SQL pools to query the CSV files.
- CConfigure ADLS Gen2 with Geo-Redundant Storage (GRS) and load the logs into an Azure Synapse Dedicated SQL Pool for analysis.
- DConfigure ADLS Gen2 with Geo-Redundant Storage (GRS), grant analyst access using an ad-hoc Shared Access Signature (SAS) token with a -year lifetime, and use Azure Synapse Analytics Serverless SQL pools.
Answer
Configure ADLS Gen2 with Geo-Redundant Storage (GRS) and use Azure Synapse Analytics Serverless SQL pools to query the CSV files.
The correct solution uses Geo-Redundant Storage (GRS) to ensure that the data survives a primary datacenter outage, and queries the CSV files directly using Azure Synapse Serverless SQL pools. Serverless SQL pools charge only for data processed per query, making them highly cost-effective for ad-hoc, intermittent query patterns on files stored in a data lake.
Step-by-Step Solution
Key Concept
Selecting the optimal Azure Synapse query model (Serverless vs. Dedicated) and storage redundancy based on cost, latency, and resiliency requirements.