Examkin

Question

Difficulty: Very hardData Integration and Analytical Storage

A multinational logistics company is designing an Azure-based data integration and analytical storage solution for real-time fleet telemetry. The system must meet the following requirements:

- Ingest telemetry data at a velocity of 18,00018,000 events per second, peaking at 25,00025,000 events per second.
- Process a total daily volume of 12 TB12\text{ TB} of raw JSON telemetry.
- Store the raw telemetry in an Azure Data Lake Storage Gen2 (ADLS Gen2) account with a retention period of 5 years5\text{ years}, ensuring the storage survives a primary datacenter outage.
- Enable data analysts to run ad-hoc, exploratory SQL queries on the raw JSON files with a target latency of under 30 seconds30\text{ seconds} for the last 24 hours24\text{ hours} of data, without incurring the cost of running persistent compute clusters.
- Grant external auditing firms temporary, read-only access to specific raw data folders for up to 12 hours12\text{ hours}, ensuring that access can be revoked immediately if needed.

Which two configurations or services should you recommend to meet these requirements? (Select TWO)

  1. Configure the ADLS Gen2 storage account to use Geo-Zone-Redundant Storage (GZRS) and use Azure Synapse serverless SQL pools to perform ad-hoc SQL queries on the raw telemetry files.Answer
  2. B
    Provision an Azure Synapse dedicated SQL pool to run the ad-hoc exploratory SQL queries directly on the raw telemetry JSON files in the data lake.
  3. Create a stored access policy on the storage container and generate a Shared Access Signature (SAS) token linked to this policy for the external auditing firms.Answer
  4. D
    Generate a Shared Access Signature (SAS) token with a 1-year lifetime directly on the ADLS Gen2 directory to grant access to the external auditing firms.
  5. E
    Configure the ADLS Gen2 storage account to use Locally Redundant Storage (LRS) to minimize replication costs while using Azure Event Hubs Capture to replicate data for disaster recovery.

Answer

Configure the ADLS Gen2 storage account to use Geo-Zone-Redundant Storage (GZRS), use Azure Synapse serverless SQL pools to perform ad-hoc SQL queries, and create a stored access policy on the storage container to generate linked Shared Access Signature (SAS) tokens for external access.
To satisfy the requirements, GZRS should be selected for the storage account to ensure survival of a primary datacenter outage. Azure Synapse serverless SQL pools should be recommended because they query raw data directly on-demand, avoiding persistent compute cluster costs. Lastly, using a stored access policy linked to SAS tokens allows immediate revocation of temporary access without changing main account keys.

Step-by-Step Solution

1
Analyze storage redundancy requirements for disaster recovery.
Locally Redundant Storage (LRS) is ruled out because it cannot survive a primary datacenter outage. Geo-Zone-Redundant Storage (GZRS) is selected to provide regional disaster resilience.
The requirement states that the stored telemetry must survive a primary datacenter outage, requiring geo-replication or zone-redundant geo-replication.
2
Analyze ad-hoc query compute requirements.
Azure Synapse serverless SQL pools are selected instead of dedicated SQL pools.
The system must enable ad-hoc SQL queries on raw files without provisioning persistent compute clusters, which matches the on-demand, serverless capabilities of Synapse serverless SQL pools.
3
Analyze secure, temporary external access requirements.
A stored access policy is created on the container, and a SAS token is generated linked to this policy.
This allows immediate revocation of the SAS token by modifying or deleting the policy, which is required to secure the 12-hour external auditing access.

Key Concept

Designing secure, cost-optimized, and resilient data integration and analytical storage architectures in Azure.
Rate this question

Topics

Data Integration and Analytical Storage

More questions from this topic