A gaming company is designing an analytical data platform to analyze multiplayer match telemetry logs. The solution must meet the following requirements:
- Volume: 500 GB of telemetry data is generated daily.
- Ingestion: Logs are uploaded as Parquet files to Azure Data Lake Storage Gen2 (ADLS Gen2) every 6 hours.
- Query Latency: Analysts run ad-hoc exploratory queries that must return results within 2 minutes.
- Cost: The compute solution must not incur charges when no queries are running.
- Resiliency: The storage solution must survive a primary datacenter outage.
Which design should you recommend?
- An Azure Synapse Analytics serverless SQL pool querying data stored in an ADLS Gen2 account configured with Geo-Redundant Storage (GRS)Cevap
- BAn Azure Synapse Analytics dedicated SQL pool querying data stored in an ADLS Gen2 account configured with Geo-Redundant Storage (GRS)
- CAn Azure Synapse Analytics serverless SQL pool querying data stored in an ADLS Gen2 account configured with Locally Redundant Storage (LRS)
- DAn Azure Function running on a Consumption plan querying data stored in an ADLS Gen2 account configured with Geo-Redundant Storage (GRS)
Cevap
An Azure Synapse Analytics serverless SQL pool querying data stored in an ADLS Gen2 account configured with Geo-Redundant Storage (GRS)
The correct solution uses Azure Synapse Analytics serverless SQL pool to query data stored in a Geo-Redundant Storage (GRS) enabled Azure Data Lake Storage Gen2 account. Synapse serverless SQL pool is designed for ad-hoc, exploratory queries on file-based data lakes, scaling compute automatically and charging only for the query data processed (with zero idle cost). GRS replicates data to a secondary region, protecting against primary datacenter failure.
Adım Adım Çözüm
Anahtar Kavram
Selecting serverless SQL pools for ad-hoc queries on data lakes and configuring Geo-Redundant Storage for resiliency.
Tahmini Süre:1m 30s