Autoscale Throughput

From Ilianko
Revision as of 15:07, 26 October 2026 by Anko (talk | contribs) (Recreated DP-420 term page: Autoscale Throughput (Throughput & Scaling))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

← Back to DP-420 Terminology Reference

Category: Throughput & Scaling

Summary: Automatically scales RU/s between 10%-100% of a configured maximum based on demand.

Overview

Autoscale throughput automatically and instantly scales the provisioned RU/s for a container or database between 10% and 100% of a configured maximum, based on usage, without manual intervention. It helps handle variable workloads while capping maximum cost, billing based on the highest RU/s scaled to within each hour.

More Info & Links

DP-420 Style Practice Questions

Q1. What does autoscale throughput do in Azure Cosmos DB?

  • A. Automatically scales RU/s between 10% and 100% of a configured maximum based on demand
  • B. Removes the need to ever configure throughput
  • C. Provides unlimited free throughput
  • D. Only works with the serverless capacity mode

Q2. How is billing calculated for autoscale throughput?

  • A. Based on the highest RU/s scaled to within each hour
  • B. A flat rate regardless of scaling activity
  • C. Based only on storage consumed
  • D. Based on the number of read regions only

Answer Key

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

  • Q1 (Autoscale Throughput): A. Automatically scales RU/s between 10% and 100% of a configured maximum based on demand — Autoscale automatically adjusts provisioned RU/s within a 10%-100% range of a set maximum, based on usage.
  • Q2 (Autoscale Throughput): A. Based on the highest RU/s scaled to within each hour — Autoscale billing is based on the peak RU/s reached during each hour.

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