Examkin

Soru

Zorluk: OrtaAzure Cosmos DB and NoSQL Solutions

An international enterprise is planning a migration and modernization of its data tier to Azure. The migration plan requires 99.999%99.999\% availability for both reads and writes, sub-10 ms10\text{ ms} latency at the 99th percentile, and active-active global distribution across 44 Azure regions. The data storage tier must support an 85:1585:15 read-to-write ratio for the product catalog and a 20:8020:80 ratio for the device telemetry stream. As part of the modernization process, several disparate data systems must be migrated to Azure Cosmos DB.

Match each workload scenario to the most appropriate Azure Cosmos DB API.

  • A telemetry ingestion pipeline migrating from an on-premises Apache Cassandra cluster that uses CQL-based queries.API for Cassandra
  • A new customer profile store requiring query flexibility with SQL-like query syntax over structured JSON documents.API for NoSQL
  • An interactive social graph platform that tracks complex network relationships, user interactions, and connections.API for Gremlin
  • A legacy retail catalog system currently running on MongoDB and utilizing existing MongoDB drivers and tools.API for MongoDB

Cevap

The correct matches pair the telemetry pipeline with the API for Cassandra, the customer profile store with the API for NoSQL, the social graph platform with the API for Gremlin, and the legacy retail catalog with the API for MongoDB.
The correct pairings align the specific workload structure, data model, and migration drivers with their designated Azure Cosmos DB API. Legacy Cassandra systems with CQL map to the API for Cassandra; new JSON document requirements map to the native API for NoSQL; graph relational structures map to the API for Gremlin; and MongoDB legacy workloads map to the API for MongoDB.

Adım Adım Çözüm

1
Analyze the database type and migration compatibility for the legacy Cassandra workload.
The workload uses CQL (Cassandra Query Language), mapping it directly to the API for Cassandra to preserve developer tools and application logic.
Using the matching API reduces rewrite effort and risk.
2
Evaluate the requirement for the customer profile store.
The profile store requires JSON documents and SQL-like querying, which aligns with the native API for NoSQL.
The API for NoSQL provides optimal performance and feature support for general document-oriented workloads in Azure Cosmos DB.
3
Identify the data model for the social network interaction workload.
The workload requires representing entities as vertices and connections as edges, which is the graph data model supported by the API for Gremlin.
A graph model is required to efficiently query deep relationships and traversals.
4
Review the migration requirements for the legacy retail catalog.
The catalog is built on MongoDB, so migrating to the API for MongoDB allows compatibility with the existing MongoDB wire protocol and drivers.
This avoids code modification for MongoDB-compatible drivers and client libraries.

Anahtar Kavram

Selecting the appropriate Azure Cosmos DB API based on database model compatibility and migration source systems.

Alternatif Yöntem

Instead of evaluating by workload type first, you can filter by API capability (e.g., look for graph, column-family, and document capabilities) and map them back to the source systems.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Azure Cosmos DB and NoSQL Solutions

Bu konudan daha fazla soru