Az cosmosdb sql container update
← Back to DP-420 Terminology Reference
Category: Throughput & Scaling
Summary: CLI: updates container config (indexing, TTL, unique keys), not throughput.
Overview
The Azure CLI command 'az cosmosdb sql container update' updates configuration settings of an existing Azure Cosmos DB for NoSQL container, such as its indexing policy, TTL, unique key policy, or conflict resolution policy, without needing to delete and recreate the container. It does not modify the container's provisioned throughput — that's handled by the dedicated 'az cosmosdb sql container throughput update' command instead.
More Info & Links
DP-420 Style Practice Questions
Q1. What can 'az cosmosdb sql container update' modify on an existing container?
- A. Settings such as indexing policy, TTL, unique key policy, or conflict resolution policy
- B. The container's provisioned throughput (RU/s)
- C. The account's consistency level
- D. The account's region replication list
Q2. Which CLI command would you use instead to change a container's provisioned RU/s?
- A. az cosmosdb sql container throughput update
- B. az cosmosdb sql container update
- C. az cosmosdb sql container redistribute-partition-throughput
- D. az cosmosdb sql container throughput migrate
Answer Key
Answers are listed at the very end so you can attempt the questions first.
- Q1 (az cosmosdb sql container update): A. Settings such as indexing policy, TTL, unique key policy, or conflict resolution policy — This command updates container-level configuration such as indexing policy and TTL, but not throughput.
- Q2 (az cosmosdb sql container update): A. az cosmosdb sql container throughput update — Throughput changes are made with 'az cosmosdb sql container throughput update', not the general container update command.
DP-420: Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB — term detail page
