A digital education company is designing an analytical data platform to process and analyze student interaction logs on Azure. The platform must meet the following requirements:
* Volume & Ingestion: Ingest of JSON logs daily at a peak velocity of events per second.
* Latency: Raw logs must be queryable via standard SQL within minutes of ingestion.
* Query Patterns: Daily dashboard queries targeting the last hours, and monthly exploratory reports analyzing historical data up to years old. Historical reports must execute without manual intervention or data retrieval delays.
* Business Continuity: The analytical data store must remain available and resilient against a primary datacenter outage.
* Cost Optimization: Storage costs must be minimized by automatically moving older data to a lower-cost tier when it is no longer queried by the daily dashboards.
Which design should you recommend for the analytical storage, lifecycle policy, and query engine?
- AStore the logs in an Azure Data Lake Storage Gen2 (ADLS Gen2) account configured with Locally Redundant Storage (LRS). Implement a lifecycle policy to transition logs older than 30 days to the Cool tier, and use an Azure Synapse Analytics serverless SQL pool to execute the monthly historical reports.
- BStore the logs in an Azure Data Lake Storage Gen2 (ADLS Gen2) account configured with Read-Access Geo-Redundant Storage (RA-GRS). Implement a lifecycle policy to transition logs older than 30 days to the Archive tier, and use an Azure Synapse Analytics serverless SQL pool to execute the monthly historical reports.
- Store the logs in an Azure Data Lake Storage Gen2 (ADLS Gen2) account configured with Read-Access Geo-Redundant Storage (RA-GRS). Implement a lifecycle policy to transition logs older than 30 days to the Cool tier, and use an Azure Synapse Analytics serverless SQL pool to execute the monthly historical reports.Answer
- DStore the logs in an Azure Data Lake Storage Gen2 (ADLS Gen2) account configured with Read-Access Geo-Redundant Storage (RA-GRS). Implement a lifecycle policy to transition logs older than 30 days to the Cool tier, and provision an Azure Synapse Analytics dedicated SQL pool to execute the monthly historical reports.