Container Configuration
Question
You have an Azure Cosmos DB account that uses the Core (SQL) API.
Which two settings can you configure at the container level? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.AC
https://www.sqlshack.com/start-your-journey-with-azure-cosmos-db/Azure Cosmos DB is a globally distributed database service that allows developers to build highly responsive and scalable applications. It provides support for various APIs, including Core (SQL), MongoDB, Cassandra, Gremlin, and Azure Table.
When working with Azure Cosmos DB using the Core (SQL) API, you can create and manage containers that store your data. Containers are logical units of storage that can be thought of as tables or collections in a traditional database system. Each container can have its own settings that can be configured as per your requirements.
The two settings that can be configured at the container level in an Azure Cosmos DB account that uses the Core (SQL) API are:
A. The throughput: This setting controls the amount of provisioned throughput that is available to your container. Throughput refers to the number of requests that your container can handle per second. By default, the throughput is set to 400 RU/s (Request Units per second) per container. However, you can increase or decrease the throughput as per your workload requirements. Increasing the throughput can improve the performance of your application, but it can also increase the cost.
B. The partition key: This setting determines how the data in your container is partitioned across the different nodes of the Azure Cosmos DB cluster. Partitioning is a technique used to horizontally scale out your database by distributing the data across multiple nodes. The partition key is a property of your data that is used to determine which partition it belongs to. It's important to choose a partition key that evenly distributes the data across partitions and avoids hotspots. You can change the partition key only when creating a new container, and not after it has been created.
Therefore, the correct answers are A (the throughput) and C (the partition key). Option B (the read region) is incorrect because read regions are configured at the account level, not the container level. Option D (the API) is also incorrect because the API is configured at the account level and cannot be changed once the account has been created.
