AZ-900: Cloud Concepts

Cloud Concepts is one of the skill areas tested on the Azure Fundamentals (AZ-900) exam. Below are free AZ-900 practice questions with worked answers and a concept diagram — each with a plain-language explanation. Practice the first 10 questions of AZ-900 free, no signup.

The concept, in one picture

Concept flowHow cloud spending works (CapEx vs OpEx)
How cloud spending works (CapEx vs OpEx)How you pay: CapEx vs OpExCapExlarge upfront purchase of hardware you ownOpExpay only for services you consume, over timeCloud = OpExpay-as-you-go; no upfront cost, scale anytime

2 free AZ-900 Cloud Concepts questions

Sample AZ-900 question

For each statement about how organizations pay for IT, select Yes if it is correct, or No if it is not.

  • Paying for Azure resources on a pay-as-you-go basis is an example of operational expenditure (OpEx).Yes
  • "Elastic expenditure" is one of Azure's standard billing models.No
  • Buying and owning on-premises servers with a large upfront payment is capital expenditure (CapEx).Yes
Explanation

There are two expenditure models to know: capital expenditure (CapEx) — a large upfront purchase of assets you own, such as on-premises servers — and operational expenditure (OpEx) — paying for services as you consume them, such as Azure pay-as-you-go. 'Elastic expenditure' and 'scalable expenditure' are not real Azure billing terms; elasticity and scalability describe how capacity adjusts to demand, not how you are billed.

Sample AZ-900 question

A payroll web application runs light traffic for most of the month, then experiences a large surge in demand during the final few days when month-end processing occurs. The team wants to add capacity only while the surge lasts and release it afterward so they pay for compute only when it is needed. Which cloud characteristic delivers this behavior?

  • High availability
  • Elasticity
  • Load balancing
  • Fault tolerance
Explanation

Elasticity is the ability to automatically add resources when demand rises and remove them when demand falls, so you pay only for the capacity you actually use — exactly what a predictable month-end spike calls for. High availability is about keeping the service reachable and minimizing downtime, not about scaling with demand. Load balancing distributes incoming requests across instances but does not by itself provision or de-provision capacity. Fault tolerance keeps the app running through component failures, which is unrelated to cost-driven scaling.

Practice AZ-900 free

The first 10 questions of every exam are free. No signup, no email wall.

Start practicing →

Get a free AZ-900 study plan by email

A short plan to work through AZ-900 by skill area, plus a note when we add new questions. Optional — the practice above stays free. No spam, unsubscribe anytime.

More AZ-900 skill areas