You are designing a product catalog for a customer. The product data will be stored in Azure Cosmos DB. The product properties will be different for each product and additional properties will be added to products as needed.
Which Cosmos DB API should you use to provision the database?
The Core (SQL) API is a suitable choice for this scenario. Azure Cosmos DB's Core (SQL) API is designed to handle dynamic and varied data structures, which is a common requirement when product properties can differ widely and change over time. Despite its name, it is not a relational database; it is a NoSQL database that supports schema-less data and allows for efficient querying using a SQL-like language. This flexibility makes it ideal for applications like a product catalog where new properties need to be added without major changes to the database schema.
Ans: Core (SQL) API ref: https://docs.microsoft.com/en-us/learn/modules/choose-api-for-cosmos-db/4-use-the-core-sql-api-to-store-a-product-catalog
As Microsoft recommend, when you create a cosmos dB from scratch and there isn’t any previous work that you could reuse, you should use sql api , unless you need relationships between data, in which case you should use gremnlin.
you are right
are you sure? "he product properties will be different for each product and additional properties will be added to products as needed" indicates NoSQL (Cassandra)
are you sure? "he product properties will be different for each product and additional properties will be added to products as needed" indicates NoSQL (Cassandra)
Answer is Core (SQL) API. Core (SQL) API is a document database, which is also NoSQL database. It has the name SQL because you can use SQL language to query it, not because it is relational DB
A. Cassandra API is correct. the product catalog was an example for cassandra api in the MS Learning Path for this exam.
are you sure about that? https://docs.microsoft.com/en-us/learn/modules/choose-api-for-cosmos-db/4-use-the-core-sql-api-to-store-a-product-catalog "Cassandra - This API isn't a good choice in this particular scenario, because the schema is unknown and will change over time."
"Cassandra This API isn't a good choice in this particular scenario, because the schema is unknown and will change over time." https://docs.microsoft.com/en-us/learn/modules/choose-api-for-cosmos-db/4-use-the-core-sql-api-to-store-a-product-catalog
By all means it is "SQL API" Reference: https://docs.microsoft.com/en-us/learn/modules/choose-api-for-cosmos-db/
"You've decided to look at how the new project is going to store the catalog for your customer facing e-commerce site. The sales team is likely to need support for adding new product categories quickly. The team had issues in the past as the old system that was using a relational database was too structured. Any necessary changes to add properties to products required downtime to update the table schemas, queries, and databases." "Supporting new product categories is an important requirement for your project, and the Core (SQL) schema is flexible and requires a schemaless data store." https://docs.microsoft.com/en-us/learn/modules/choose-api-for-cosmos-db/4-use-the-core-sql-api-to-store-a-product-catalog