Examkin

Question

Difficulty: HardAzure Cosmos DB and NoSQL Solutions

You are designing the data storage and diagnostics architecture for a global smart-home automation platform. The platform manages telemetry and configuration data for 10,000,00010,000,000 IoT devices across North America, Europe, and Asia. The solution must meet the following requirements:
- Support real-time telemetry ingestion with a write-to-read ratio of 9:19:1.
- Maintain sub-10 ms10\text{ ms} write latency globally by utilizing an active-active multi-region write configuration.
- Achieve a recovery time objective (RTO) of zero for regional disaster recovery.
- Prevent hot partitions during mass device reconnect events.
- Provide external diagnostic partners with read-only access to device logs for a maximum of 3030 days, with the ability to immediately revoke access if a security compromise occurs.

Which architecture configuration should you recommend?

  1. A
    Configure Azure Cosmos DB for NoSQL with multi-region writes enabled, partitioning the telemetry container by deviceType. Export diagnostics to an Azure Storage account configured with Read-Access Geo-Redundant Storage (RA-GRS) and grant external access using Shared Access Signature (SAS) tokens associated with a stored access policy.
  2. B
    Configure Azure Cosmos DB for NoSQL with multi-region writes enabled, partitioning the telemetry container by deviceId. Export diagnostics to an Azure Storage account configured with Locally Redundant Storage (LRS) and grant external access using Shared Access Signature (SAS) tokens associated with a stored access policy.
  3. Configure Azure Cosmos DB for NoSQL with multi-region writes enabled, partitioning the telemetry container by deviceId. Export diagnostics to an Azure Storage account configured with Read-Access Geo-Redundant Storage (RA-GRS) and grant external access using Shared Access Signature (SAS) tokens associated with a stored access policy.Answer
  4. D
    Configure Azure Cosmos DB for NoSQL with multi-region writes enabled, partitioning the telemetry container by deviceId. Export diagnostics to an Azure Storage account configured with Read-Access Geo-Redundant Storage (RA-GRS) and grant external access using ad-hoc Shared Access Signature (SAS) tokens with a 3030-day lifetime defined directly in the URI.

Answer

Configure Azure Cosmos DB for NoSQL with multi-region writes enabled, partitioning the telemetry container by deviceId. Export diagnostics to an Azure Storage account configured with Read-Access Geo-Redundant Storage (RA-GRS) and grant external access using Shared Access Signature (SAS) tokens associated with a stored access policy.
Partitioning the database container by deviceId guarantees high cardinality, which spreads write throughput uniformly across partitions. Exporting diagnostic data to a Read-Access Geo-Redundant Storage (RA-GRS) account ensures that even if a primary region is offline, diagnostic logs remain accessible from the secondary region. Associating the SAS token with a stored access policy meets the security standard by permitting immediate revocation of external permissions through modification or deletion of the policy.

Step-by-Step Solution

1
Analyze partition key cardinality requirements
Identify that partitioning by deviceId provides high cardinality, which distributes write requests evenly across physical partitions, preventing hot partitions during mass reconnects.
Choosing deviceType (low cardinality) would concentrate data from millions of devices onto a small set of logical partitions, causing partition key exhaustion and performance bottlenecks.
2
Evaluate storage redundancy requirements for regional resilience
Select Read-Access Geo-Redundant Storage (RA-GRS) to provide read availability from a secondary region during a primary region outage.
Locally Redundant Storage (LRS) only replicates data within a single datacenter facility, violating regional disaster recovery guidelines.
3
Select the correct SAS token delegation mechanism
Determine that SAS tokens must be associated with a stored access policy to support immediate revocation.
Ad-hoc SAS tokens defined directly in the URI cannot be revoked prior to expiration unless the master storage keys are rotated, which impacts all active integrations.

Key Concept

Designing partition keys for scalable NoSQL systems, choosing geographic data redundancy tiers, and securing Azure storage endpoints with revocable shared access mechanisms.
Rate this question

Topics

Azure Cosmos DB and NoSQL Solutions

More questions from this topic