You need to choose the capacity mode and scale configuration for account2 to support the planned changes and meet the business requirements.
What should you select?
The Litware business requirement states that Azure Cosmos DB costs for IoT processing must be predictable. Provisioned throughput bills a fixed hourly rate for the RU/s you reserve, giving a known, predictable cost, whereas serverless bills per request and varies with load. Within provisioned throughput, manual (standard) throughput holds a fixed RU/s so the cost is constant and predictable; autoscale continuously scales between 10% and 100% of the maximum, making the bill fluctuate, so it fails the predictability requirement. Assigning manual throughput directly to iotcont1 and iotcont2 (dedicated per-container) meets the requirement without relying on database-level shared throughput.
Community Discussion