AZ-900 Describe cloud concepts Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Economies of scale

  Why it's wrong here

  Economies of scale is a cost-based advantage: cloud providers aggregate demand across millions of customers, achieving lower per-unit costs that are passed on as lower prices. This benefit reduces your operating expenditure, but it does not address the challenge of predicting future workload demand. Because it is unrelated to resource right-sizing or on-demand elasticity, it cannot be the correct answer for the described capacity planning benefit.

• ✓

  Stop guessing capacity requirements

  Why this is correct

  This benefit eliminates the need to forecast infrastructure capacity upfront, a notoriously difficult and wasteful part of traditional IT. Instead, you can provision the minimum required resources and scale up or down automatically as actual demand changes, using services like Virtual Machine Scale Sets or Azure Autoscale. By paying for only what you use, you avoid both over-provisioning costs and under-provisioning performance risks. This directly matches the description of stopping capacity guesswork.

• ✗

  Increased speed and agility

  Why it's wrong here

  Speed and agility in cloud computing refer to the ability to develop, test, and launch applications in days or hours rather than weeks, by provisioning pre-built infrastructure and services on demand. This accelerates time-to-market and enables experimentation, but it is about rapid delivery, not about optimizing resource allocation to actual usage patterns. The benefit of stopping capacity guessing is specifically about right-sizing elastic workloads, which is distinct from deployment velocity.

• ✗

  Go global in minutes

  Why it's wrong here

  Achieving global reach in minutes means you can deploy applications to Azure regions around the world with just a few console clicks or API calls, enabling low-latency experiences for users everywhere. This benefit focuses on geographic distribution and regulatory/data residency compliance, not on matching compute or storage capacity to fluctuating demand. Since it is a location and availability advantage rather than a capacity scalability advantage, it does not fit the 'stop guessing capacity' benefit.