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.

• ✗

  You always pay the same amount regardless of usage

  Why it's wrong here

  This statement is false because Azure uses a pay-as-you-go model, where you are billed based on actual resource consumption, such as virtual machine hours, storage operations, and data egress. Your monthly invoice fluctuates with workload changes, so you do not pay the same amount regardless of usage. While Reserved Instances or Savings Plans provide discounted rates for a commitment, they still require you to estimate and match your usage, and any overage is charged at the standard variable rate. Predictability comes from budgeting and monitoring tools, not from invariant billing.

• ✓

  Costs can be forecasted and controlled using consumption-based pricing and planning tools

  Why this is correct

  Azure's consumption-based pricing charges you only for what you use, making costs variable in theory. However, with tools like the Azure Pricing Calculator, TCO Calculator, and Cost Management + Budgets, you can accurately forecast spending and set limits or alerts. For example, you can define budgets and configure alerts to notify you when spending approaches a threshold, and use Azure Advisor to optimize resource utilization. Thus, 'predictable costs' in Azure mean the ability to plan and govern spending, not a fixed bill.

• ✗

  Cloud services are always cheaper than on-premises solutions

  Why it's wrong here

  This is incorrect because cloud economics depend on workload characteristics and total cost of ownership. For steady-state, predictable workloads with high utilization, on-premises or private cloud can be more cost-effective after factoring in licensing and egress charges, while cloud often adds cost for data transfer and 24/7 operations. Azure can reduce capital expenditure and offer elasticity, but it does not guarantee a lower price than on-premises; it is a trade-off between capital and operational expense plus flexibility. Cost predictability is about knowing and controlling expenses, not ensuring they are always minimal.

• ✗

  Hardware costs are fixed for the contract term

  Why it's wrong here

  Azure operates a shared responsibility model where you do not own or lease physical hardware; you access compute, storage, and networking as a service. There are no hardware procurement contracts, depreciation schedules, or fixed hardware-cost terms; even when you choose a Reserved Instance, you are committing to a specific level of compute power for a term, but the underlying hardware is still managed by Azure and remains invisible to you. Billing is based on service consumption (e.g., vCPU hours or storage GB) rather than hardware assets. Therefore, hardware costs are neither fixed nor contractually bound; you pay for capability on demand.

Go deeper

Related to this question