Examkin

Soru

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

A retail company is migrating its inventory management system to Azure. The database must track relationships between products, suppliers, and orders, enforcing referential integrity through foreign keys and supporting complex multi-table joins. The systems architect proposes deploying Azure Cosmos DB to host this relational workload. Is the systems architect's proposal correct?

Cevap: Cevap

Cevap

The correct answer is False.
The correct answer is False because the requirements describe a relational database workload (foreign keys, referential integrity, and complex joins), whereas Azure Cosmos DB is a non-relational (NoSQL) database service.

Adım Adım Çözüm

1
Analyze the workload requirements: tracking relationships (products, suppliers, orders), referential integrity (foreign keys), and complex joins.
Identify that the system requires a relational database management system.
Foreign keys and complex joins are standard features of relational databases.
2
Evaluate the proposed Azure service: Azure Cosmos DB.
Identify that Azure Cosmos DB is a non-relational (NoSQL) database service.
Cosmos DB is built for non-relational, schema-free data models.
3
Assess the fit of Azure Cosmos DB for the relational workload.
Conclude that Cosmos DB is not suitable for a workload that relies on native relational constraints and multi-table joins, making the proposal incorrect.
Azure Cosmos DB is not a relational database, so the proposal is False.

Anahtar Kavram

Azure Cosmos DB is a non-relational (NoSQL) database service, which is not designed to natively handle relational workloads requiring strict referential integrity (foreign keys) and complex multi-table joins.
Bu soruyu puanla

Konular

Azure Database Services (Relational, Non-Relational, and Cosmos DB)

Bu konudan daha fazla soru