Examkin

Question

Difficulty: Very hardAzure Cosmos DB and NoSQL Solutions

You are designing an Azure migration strategy for several legacy databases. Match each workload scenario on the left with the correct Azure Cosmos DB API on the right to ensure the migration requires minimal application refactoring while meeting performance and architectural requirements.

  • A telemetry ingestion application that processes high-frequency time-series data from IoT devices. The legacy database uses a wide-column storage model, and developers query it using CQL-based scripts that must be preserved.Azure Cosmos DB for Apache Cassandra
  • A fraud-detection application that analyzes relationships between financial transactions, user accounts, and device fingerprints to find suspicious circular paths. The application requires complex multi-hop query traversals using vertices and edges.Azure Cosmos DB for Apache Gremlin
  • An e-commerce product catalog that is being migrated from an on-premises database. It stores documents in BSON format, relies on nested arrays, and utilizes existing application drivers that communicate over port 27017.Azure Cosmos DB for MongoDB
  • A globally distributed user session state store that currently utilizes Azure Table Storage. The business requires migrating to a database that guarantees sub-10ms read and write latencies with a 99.999% availability SLA and dedicated throughput.Azure Cosmos DB for Table

Answer

Match the wide-column CQL telemetry application to Azure Cosmos DB for Apache Cassandra; match the graph-based fraud-detection application to Azure Cosmos DB for Apache Gremlin; match the BSON-based product catalog to Azure Cosmos DB for MongoDB; and match the low-latency Table Storage workload to Azure Cosmos DB for Table.
Matching each legacy system to its corresponding wire-compatible Azure Cosmos DB API allows developers to preserve client-side code, drivers, and query structures while gaining the benefits of a fully managed cloud database.

Step-by-Step Solution

1
Analyze the technical requirements of the first scenario (CQL and wide-column).
Identify that the Cassandra Query Language (CQL) and wide-column store map directly to the Cassandra API.
This minimizes development effort by allowing the reuse of existing Cassandra drivers and queries.
2
Analyze the technical requirements of the second scenario (vertices, edges, multi-hop traversals).
Identify that a property graph model utilizing TinkerPop/Gremlin maps directly to the Gremlin API.
Graph databases are optimized for traversing relationships between entities.
3
Analyze the technical requirements of the third scenario (BSON, port 27017, nested arrays).
Identify that these details describe MongoDB database communications, which map to the MongoDB API.
Cosmos DB for MongoDB supports the MongoDB wire protocol, allowing applications to connect using standard MongoDB client drivers.
4
Analyze the technical requirements of the fourth scenario (Azure Table Storage migration with sub-10ms latency and 99.999% SLA).
Identify that the Table API provides a drop-in replacement for Table Storage with premium performance guarantees.
Azure Cosmos DB for Table offers turnkey global distribution, dedicated throughput, and single-digit millisecond latency SLAs compared to standard Azure Table Storage.

Key Concept

Selecting the appropriate Azure Cosmos DB API based on legacy database systems, query APIs, protocols, and performance requirements.
Rate this question

Topics

Azure Cosmos DB and NoSQL Solutions

More questions from this topic