Examkin

Soru

Zorluk: OrtaAzure Cosmos DB and NoSQL Solutions

A logistics company is designing an Azure-based telemetry and media capture solution for a global fleet of 50,00050,000 delivery vehicles. Each vehicle uploads a JSON telemetry packet and a small dashcam image every 1010 seconds. The solution must support write-heavy ingestion scalability with sub-10 ms10\text{ ms} database latencies, survive regional datacenter outages, and allow secure, temporary access to the dashcam images stored in Azure Blob Storage. Which configuration should you recommend for the storage architecture?

  1. A
    Configure Azure Cosmos DB using the NoSQL API with multi-region writes, setting the partition key of the telemetry container to the vehicle status field. Store the dashcam images in a geo-redundant storage (GRS) account, and access them using short-lived SAS tokens.
  2. B
    Configure Azure Cosmos DB using the NoSQL API with multi-region writes, setting the partition key of the telemetry container to the vehicle ID. Store the dashcam images in a geo-redundant storage (GRS) account, and access them using a static SAS token with a five-year lifetime embedded in the vehicle firmware.
  3. Configure Azure Cosmos DB using the NoSQL API with multi-region writes, setting the partition key of the telemetry container to the vehicle ID. Store the dashcam images in a geo-redundant storage (GRS) account, and access them using short-lived Shared Access Signatures (SAS) generated dynamically via a user delegation key.Cevap
  4. D
    Configure Azure Cosmos DB using the NoSQL API with Locally Redundant Storage (LRS) in a single region, relying on manual backups for disaster recovery. Store the dashcam images in a Locally Redundant Storage (LRS) account, and access them using short-lived SAS tokens.

Cevap

Configure Azure Cosmos DB using the NoSQL API with multi-region writes, setting the partition key of the telemetry container to the vehicle ID. Store the dashcam images in a geo-redundant storage (GRS) account, and access them using short-lived Shared Access Signatures (SAS) generated dynamically via a user delegation key.
The correct option correctly pairs a high-cardinality partition key (vehicle ID) to avoid hot partitions with multi-region write replication for high availability and regional resiliency. Additionally, it leverages GRS for image storage and short-lived SAS tokens generated dynamically, satisfying the security, resilience, and operational requirements.

Adım Adım Çözüm

1
Select the Cosmos DB partition key.
The vehicle ID provides high cardinality, distributing database requests evenly across physical partitions and preventing hot partitions.
Choosing a high-cardinality property is critical for write-heavy workloads to maximize Request Unit efficiency.
2
Configure redundancy and geo-replication.
Select multi-region writes for Azure Cosmos DB and Geo-redundant storage (GRS) for Azure Blob Storage.
This guarantees high availability, sub-10ms read/write latencies globally, and data survival during a regional outage.
3
Establish secure access for media files.
Generate short-lived user delegation SAS tokens dynamically via Microsoft Entra credentials.
This avoids exposing storage account access keys and limits the potential blast radius of compromised tokens.

Anahtar Kavram

Azure Cosmos DB partition key design, multi-region replication, and secure Azure Storage integration.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Azure Cosmos DB and NoSQL Solutions

Bu konudan daha fazla soru