Your company plans to use an Azure Cosmos SQL DB for data storage. The company plans to use partitioning to meet application performance goals.
You need to verify Cosmos DB partitioning features to ensure that it will meet the company's requirements.
Choose all that apply:
A single logical partition can contain no more than 10 GB of data. This is an enforced upper storage limit that cannot be overridden.
Microsoft guarantees a throughput of 400, not 1000, RU/s for a partitioned container. RUs are used as a way to express a normalized cost of database operations and can be used for throughput comparisons. RU calculations are based on CPU, I/O operations (IOPS), and memory. For example, the cost to read a 1 KB item is 1 RU.
Partitioning is automatic and managed transparently by Azure Cosmos DB. You do not get directly involved with either logical or physical partitioning. Logical partitioning is the horizontal partitioning of the data in a Cosmos DB container. Cosmos DB can scale horizontally by spreading logical partitions across multiple servers. Logical partitioning is based on your defined partition key. Physical partitioning determines where the data is physically stored and uses a hash of the partition key to distribute logical partitions over physical partitions.
Transactions using stored procedures or triggers can be performed against a single partition only. This can be a key factor when determining the value or values to use when defining a partition key. Only those items with the same partition key value are part of the same logical partition. Also, queries are more efficient when run across a single partition, but are supported over multiple partitions.