An enterprise is designing a telemetry analytics platform on Azure to ingest and store clickstream logs from regional applications. The platform must meet the following requirements:
* Storage and Volume: Ingest and store of historical logs in CSV format within a hierarchical namespace storage account, with a nightly batch pipeline appending of new data at a rate of .
* Exploratory Queries: Enable data analysts to run ad-hoc, exploratory SQL queries on the raw files with a target query latency of under . Compute cost must only be incurred during query execution.
* Resilience: The underlying storage must remain available for read access during a primary Azure region outage.
* Security: Grant third-party partners read-only access to a specific directory in the data lake, with the ability to instantly revoke access if credentials are compromised.
Which storage configuration, analytics service, and authorization mechanism should you recommend to meet these requirements?
- AConfigure the storage account to use Locally Redundant Storage (LRS). Deploy Azure Synapse Analytics serverless SQL pools to query the CSV files. Generate Shared Access Signatures (SAS) linked to a Stored Access Policy for external partners.
- Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS). Deploy Azure Synapse Analytics serverless SQL pools to query the CSV files. Generate Shared Access Signatures (SAS) linked to a Stored Access Policy for external partners.Cevap
- CConfigure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS). Deploy an Azure Synapse Analytics dedicated SQL pool to query the CSV files. Generate Shared Access Signatures (SAS) linked to a Stored Access Policy for external partners.
- DConfigure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS). Deploy Azure Synapse Analytics serverless SQL pools to query the CSV files. Generate long-lived Shared Access Signatures (SAS) with expiration times defined directly in the SAS token URI for external partners.