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 pricing advantage where a provider aggregates demand across many customers to lower per-unit infrastructure costs. This benefit is fundamentally about cost efficiency and purchasing power, not about automatically receiving the latest technology without customer-managed upgrades. Large-scale providers can afford state-of-the-art facilities, but the term itself describes why prices can be lower, not the continuous delivery of current technology to customers.

• ✓

  Always-current technology without customer-managed upgrades

  Why this is correct

  This is the correct answer because in a public cloud model, the provider is responsible for maintaining, patching, and upgrading the underlying infrastructure, including hardware and platform services. Customers always consume the latest available technology without needing to plan for or perform system upgrades themselves, and hardware failures are handled with current-generation replacements. This operational benefit removes the customer's burden of refresh cycles and allows them to focus on application development rather than infrastructure maintenance.

• ✗

  Geographic distribution of data centers

  Why it's wrong here

  Geographic distribution of data centers refers to Azure's global network of regions and availability zones, which supports data residency, latency, and disaster recovery. It does not describe the benefit of running on current hardware and software because the provider's global footprint is about placement, not the ongoing refresh of technology. While distribution helps customers deploy near users, it does not automatically give them the latest features without performing upgrades.

• ✗

  Predictable billing with reserved capacity

  Why it's wrong here

  Predictable billing with reserved capacity is a cost-management benefit achieved by pre-committing to consume services for one or three years, often in exchange for discounted rates. This is distinct from the benefit of always-current technology because reserved capacity focuses on budgeting and financial planning, not on whether the underlying infrastructure is upgraded by the provider. Committing to capacity does not influence the provider's hardware refresh cycle or eliminate the customer's need to manage upgrades.