Az cosmosdb sql container throughput update

From Ilianko

← Back to DP-420 Terminology Reference

Category: Throughput & Scaling

Summary: CLI: changes a container's manual RU/s or autoscale max RU/s.

Overview

The Azure CLI command 'az cosmosdb sql container throughput update' changes the provisioned throughput (RU/s) assigned to a container that uses manual (standard) Provisioned Throughput, or updates the maximum RU/s ceiling for a container using Autoscale Throughput. It is the CLI equivalent of adjusting throughput in the Azure portal's Scale tab for a specific container.

More Info & Links

DP-420 Style Practice Questions

Q1. What does 'az cosmosdb sql container throughput update' change?

  • A. The container's provisioned RU/s (manual) or maximum RU/s ceiling (autoscale)
  • B. The container's indexing policy
  • C. The container's partition key path
  • D. The account's default consistency level

Q2. If a container currently uses Autoscale Throughput, what does 'throughput update' change?

  • A. The maximum RU/s ceiling the autoscale range can reach
  • B. The minimum RU/s floor only
  • C. The container's partition key
  • D. The consistency level used by the container

Answer Key

Answers are listed at the very end so you can attempt the questions first.

  • Q1 (az cosmosdb sql container throughput update): A. The container's provisioned RU/s (manual) or maximum RU/s ceiling (autoscale) — This command adjusts the throughput (manual RU/s or autoscale max RU/s) assigned specifically to a container.
  • Q2 (az cosmosdb sql container throughput update): A. The maximum RU/s ceiling the autoscale range can reach — For autoscale-enabled containers, this command updates the configured maximum RU/s, which determines the full 10%-100% autoscale range.

DP-420: Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB — term detail page

Retrieved from "https://ilianko.com/index.php?title=Az_cosmosdb_sql_container_throughput_update&oldid=6178"