Kladde.Verlauf has one account. Tenants are offices, and an office is a value of the partition key (Lesson 1.4), not an account of its own. Still, the topic belongs here: the exam asks about managing many accounts, and whether you need a fleet can be decided with the Kladde's figures. The lesson stays with what Learn says.

Prior knowledge. Autoscale and maximums are in Lesson 1.1, tenants as key values in Lesson 1.4, the sources of observation in Lesson 3.3.

What was run. A Bicep file was compiled with az bicep build, and a C# program (.NET 10, no packages) checks a plan against the rules from Learn. Not run against Azure is everything that creates a fleet. All figures in the example plans are assumptions of the task.

Status of the feature: how to read the pages

First the status, because it changes what you write into a design. The pages "fleets overview", "fleet pools", "create a fleet" and "fleet analytics" were read:

  • The pages on fleets and pools carry no preview note. The type in Bicep (Microsoft.DocumentDB/fleets and fleetspaces), however, could be compiled only with an API version ending in preview (2025-11-01-preview). Open: whether the feature is generally available.
  • Fleet analytics is a preview according to Learn, without a service-level commitment, and Learn advises against production workloads for previews.

Rule of thumb for design: a preview belongs in a plan as a decision of the client, not as a prerequisite.