At which two levels can you set the throughput for an Azure Cosmos DB account? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Click on the arrows to vote for the correct answer
A. B. C. D.AC
https://docs.microsoft.com/en-us/azure/cosmos-db/set-throughputAzure Cosmos DB is a fully managed NoSQL document database service that provides global distribution and elastic scalability. It supports various data models such as key-value, graph, column-family, and document. Cosmos DB offers automatic indexing, high availability, low latency, and a rich set of APIs for different programming languages.
When creating an Azure Cosmos DB account, you can choose to provision throughput at different levels to support the required workload. Throughput is a measure of the database's processing capacity, which is the number of requests per second that it can handle. The following levels are available for setting throughput in Azure Cosmos DB:
Database level: You can set throughput at the database level, which means that all the containers within the database share the provisioned throughput. When you set throughput at the database level, Cosmos DB automatically distributes the throughput among the containers based on their request rate. This option is useful when all the containers in the database have a similar workload.
Container level: You can set throughput at the container level, which means that the container has its own dedicated throughput. This option is useful when you have containers with different workloads or when you need to scale individual containers independently.
In summary, the correct answers are:
A. Database C. Container