Soru

Zorluk: OrtaAzure Database Services (Relational, Non-Relational, and Cosmos DB)

A company plans to migrate an on-premises inventory management application to Microsoft Azure. The application requires a traditional relational database structure with strict schema enforcement, foreign key constraints, and complex SQL joins. The IT team is considering using Azure Cosmos DB for this database workload.

Why is Azure Cosmos DB unsuitable for this specific scenario?

  1. It is a multi-model NoSQL database designed for non-relational workloads rather than a traditional relational database engine.Cevap
  2. B
    It is a Software as a Service (SaaS) database service, which prevents the customer from defining custom tables or schemas.
  3. C
    It is an Infrastructure as a Service (IaaS) offering that requires the customer to manage and perform all operating system patching.
  4. D
    It is a traditional relational database engine that does not support SQL-based query capabilities.

Cevap

It is a multi-model NoSQL database designed for non-relational workloads rather than a traditional relational database engine.
The correct option is correct because Azure Cosmos DB is a NoSQL (non-relational) database service, designed for high-velocity, semi-structured data, and lacks native support for traditional relational database features like foreign key constraints and ACID-compliant joins across multiple distinct tables.

Adım Adım Çözüm

1
Analyze the application requirements.
The application requires a traditional relational structure, strict schema enforcement, foreign keys, and complex SQL joins.
Understanding the technical requirements is the first step to choosing or evaluating a database service.
2
Evaluate the capabilities of Azure Cosmos DB.
Azure Cosmos DB is a fully managed NoSQL (non-relational) database service designed for horizontal scaling, low latency, and semi-structured data.
Comparing service capabilities against the requirements helps identify mismatch points.
3
Identify the mismatch between requirements and Azure Cosmos DB.
Since Azure Cosmos DB is non-relational, it does not natively enforce traditional relational constraints like foreign keys across multiple tables or standard SQL joins.
This determines why Azure Cosmos DB is unsuitable for this workload.

Anahtar Kavram

Azure Cosmos DB is a fully managed, globally distributed NoSQL database service, whereas relational workloads requiring strict schemas, foreign keys, and traditional SQL joins are best suited for relational databases like Azure SQL Database.
Bu soruyu puanla