Azure Expenditure Models: Pay-As-You-Go vs. Elastic

AZ-900 By islever Editorial Last updated

Describe cost management in Azure

Short answer

B The solution does not meet the goal because "elastic expenditure model" is not a recognized Azure billing term; pay-as-you-go follows the Operational Expenditure (OpEx) model.

Question

Note: The question is included in a number of questions that depicts the identical set-up. However, every question has a distinctive result. Establish if
the solution satisfies the requirements.
Your company is planning to migrate all their virtual machines to an Azure pay-as-you-go subscription. The virtual machines are currently hosted on the Hyper-V
hosts in a data center.
You are required make sure that the intended Azure solution uses the correct expenditure model.
Solution: You should recommend the use of the elastic expenditure model.
Does the solution meet the goal?
  1. Yes
  2. No Correct Answer

Key Takeaways

The question tests knowledge of Azure cost management terminology by presenting a non-standard term ('elastic expenditure') and requiring the candidate to identify it as invalid in favor of standard OpEx or consumption-based models.

This question tests the correct terminology for Azure billing models, specifically identifying that 'elastic expenditure' is not a standard term. It establishes that pay-as-you-go subscriptions align with Operational Expenditure (OpEx), making the suggested solution incorrect.

Common mistake: Candidates may incorrectly answer 'Yes' because they confuse the technical capability of elasticity (auto-scaling) with a billing model name, or they assume 'elastic' is a synonym for flexible pricing.

Expert Analysis

Why the Answer Is Correct

The correct answer is B (No). In Microsoft Azure and general cloud computing frameworks, there are two primary financial models: Capital Expenditure (CapEx) and Operational Expenditure (OpEx). The pay-as-you-go subscription model is a classic example of OpEx, where costs are incurred based on actual usage rather than upfront investment. The term "elastic expenditure model" does not exist in Azure documentation or ITIL standards; while services can be elastic (scalable), this is a technical characteristic, not a financial billing model.

Why the Other Options Are Wrong

Option A (Yes) is incorrect because it validates a fabricated term. There is no such thing as an "elastic expenditure model" in Azure's pricing structure. While auto-scaling provides elasticity, the billing remains strictly pay-as-you-go or reserved instance-based, both falling under OpEx.

Community Comment Notes

The community overwhelmingly agrees that the term is invalid. As AntonioTech noted, "The term 'elastic expenditure model' isn't a standard term... The two common expenditure models in Azure are 'pay-as-you-go' and 'reserved instances.'" Another commenter, mrgilbe1, clarified that the question likely stems from a multiple-choice format where options like "Scalable" or "Elastic" were distractors against the correct answer of "Operational Expenditure." Elmi108 also confirmed that "elastic expenditure model is not a recognized Azure option."

Exam Strategy

When evaluating Azure cost questions, always distinguish between technical features (like elasticity/scaling) and financial models (CapEx/OpEx). If a specific named billing model sounds made-up (e.g., 'elastic expenditure'), it is almost certainly incorrect.

Frequently Asked Questions

What is the difference between CapEx and OpEx in Azure?

CapEx involves upfront capital investment for hardware (on-premises). OpEx involves ongoing operational costs for resources consumed (cloud), such as Azure's pay-as-you-go model.

Does Azure offer an elastic billing model?

No. While Azure resources are elastic (can scale up/down), the billing model is either Consumption (Pay-As-You-Go) or Reserved Instances. Both are forms of OpEx.

More AZ-900 FAQ →

Discussion 35 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 30 of 35

  1. AntonioTech 👍 21
    The answer is B. No The term "elastic expenditure model" isn't a standard term or concept used in Azure or cloud computing. The two common expenditure models in Azure are "pay-as-you-go" and "reserved instances." Pay-as-you-go: This is the default and most common expenditure model in Azure. It means you pay for resources you consume on an hourly or per-minute basis. It offers flexibility to scale resources up and down as needed. Reserved Instances: This is an expenditure model where you commit to a one- or three-year term for a particular virtual machine instance type, size, and region. This commitment provides you with a discount compared to pay-as-you-go pricing. Given the options, if you're migrating to a pay-as-you-go subscription, you're already aligning with the pay-as-you-go expenditure model. The term "elastic expenditure model" doesn't accurately represent an established concept in Azure, so the solution is not correct. The correct description for the chosen expenditure model would simply be "pay-as-you-go."
  2. apurba_nag 👍 4 Answered B
    Answer: B. No Explanation: The elastic expenditure model typically refers to the ability to automatically scale resources (e.g., virtual machines, storage) up or down based on demand. However, Azure's pay-as-you-go subscription model does not directly align with this concept. Instead, it charges based on resource usage without inherent elasticity or auto-scaling built-in.
  3. mrgilbe1 👍 4
    This question seems to be adapted from a 4-way multi choice question where the 4 answers are: A. Operational Expenditure B. Capital Expenditure C. Scalable Expenditure D. Elastic Expenditure. C and D are nonsense terms. The correct answer here is A. operational expenditure. B. Capital Expenditure is wrong as you are not buying assets.
  4. MattRam 👍 4
    There is no right answer - the question is poorly formulated as you cannot give a correct answer in the multiple choice options provided. Not even a good trick question.
  5. arjunyv2022 👍 4 Answered B
    Azure’s pay-as-you-go subscription follows the OpEx (Operational Expenditure) Model, not the "Elastic Expenditure Model."
Show 25 more comments
  1. Soumyat85 👍 3
    B. No The solution does not meet the goal. There is no specific expenditure model called the "elastic expenditure model" in Azure. When migrating virtual machines to an Azure pay-as-you-go subscription, the appropriate expenditure model to consider is the "pay-as-you-go" or "consumption-based" model. This means that you will be billed based on the actual usage of Azure resources, such as virtual machines, storage, and networking, on an hourly or per-minute basis. Therefore, the correct solution would be to recommend the use of the "pay-as-you-go" expenditure model, not the "elastic expenditure model."
  2. Williamyla 👍 3
    B. No.The elastic expenditure model is not the correct term in this context. For Azure pay-as-you-go subscriptions, the appropriate expenditure model is the consumption-based model. This model charges you based on the actual usage of resources, which aligns with the pay-as-you-go approach.
  3. elmi108 👍 3 Answered B
    No, the solution is not valid because the "elastic expenditure model" is not a recognized Azure option. You should recommend either "Pay-As-You-Go" or "Reserved Instances" depending on your company's needs.
  4. Molota 👍 3 Answered B
    There are 2 types of expenditure modele Capital Expenditure (CAPEX) Operational Expenditure (OPEX) so elastic expenditure isn't a model, wrong solution provided
  5. Kanders 👍 3
    B. No - does not meet the goal; no such model as elastic - there is either Capital Expenditure (CapEx) or Operating Expenditure (OpEx)
  6. Olufavour 👍 3
    Elasticity Model! There is nothing like that in Azure Model.
  7. Rohit0107 👍 2 Answered A
    Explanation: The elastic expenditure model refers to a consumption-based pricing model, which aligns with Azure's pay-as-you-go subscription model. Here's how it matches: Requirement Elastic Model Migrating to pay-as-you-go ✅ Supported Scales with demand ✅ Automatically adjusts Cost-efficient for variable loads ✅ You pay only for what you use No upfront costs ✅ True
  8. Zaidsdb 👍 2 Answered B
    In summary, the recommended elastic expenditure model is not a standard Azure expenditure model, and it's unclear what this means without more context about your company's requirements. However, depending on your company's specific needs, the pay-as-you-go model could be a suitable option.
  9. kahla 👍 2 Answered B
    The company is migrating VMs from on-premises (Hyper-V) to Azure. They will use an Azure pay-as-you-go subscription. The question asks if the “elastic expenditure model” is the correct model in this case. 🧠 What is the Elastic Expenditure
  10. rafaelfiss 👍 2
    The question is leading to a misinterpretation between the distinct cloud-basic concepts of Operational Expenses (Opex) and Elasticity (dynamic resource allocation). Answer is NO
  11. NOTEBOOK_789 👍 2
    Answer should be 'No' because Elasticity is a Characteristic of Cloud. And, Capex and Opex is a expenditure models
  12. AlefZERO 👍 2 Answered B
    There are 2 types: operational expenditures - pays as you go capital expenditure - pay in the advance
  13. dev2dev 👍 2
    Elasticity is attribute of resource performance related to how easility they can scale up or down.
  14. glazdub 👍 2 Answered B
    elastic is a feature of cloud computing paradigm.
  15. yicoj20415 👍 2 Answered B
    there is no expenditure model like that
  16. Stephane_37 👍 2 Answered B
    B is correct
  17. justlion 👍 2 Answered B
    its B
  18. Meesquared 👍 1 Answered B
    Reason: The question specifically mentions "pay-as-you-go subscription", which is the correct expenditure model name in Azure. The term "elastic expenditure model" is not an official Azure pricing model term. While Azure resources are elastic in nature, Microsoft does not use "elastic expenditure model" to describe pricing. 👉 Therefore, saying "elastic expenditure model" is incorrect terminology, so the solution does NOT meet the goal. ✅ Correct Explanation: Pay-as-you-go = Pay for what you use, scale up/down anytime. Reserved Instances = Commit for 1 or 3 years for a discount. There is no pricing model officially called "elastic expenditure model."
  19. Rcosmos 👍 1
    ✅ A solução propõe: Usar gasto elástico → isso se alinha ao modelo pay-as-you-go. ✅ Conclusão: Sim, recomendar o uso do modelo de gasto elástico está alinhado com o objetivo de usar pagamento conforme o uso, pois ele garante que você pague apenas pelos recursos consumidos, evitando custos fixos desnecessários. ✅ Resposta correta: A. Sim
  20. AlekksMaciel 👍 1 Answered B
    The answer is B. No The term "elastic expenditure model" isn't a standard term or concept used in Azure or cloud computing. The two common expenditure models in Azure are "pay-as-you-go" and "reserved instances."
  21. Barach Aduot 👍 1 Answered A
    Azure uses an elastic expenditure model, meaning you pay for the resources you use and can scale resources up or down based on demand. This fits an Azure pay-as-you-go subscription.
  22. MONIKINHA 👍 1 Answered B
    Os dois modelos de despesas comuns no Azure são "pagamento conforme o uso" e "instâncias reservadas".
  23. Queenesty 👍 1 Answered A
    Azure's pay-as-you-go pricing model is a classic example of an elastic expenditure model
  24. roxxie31 👍 1 Answered B
    No. Elastic expenditure isn’t a model. The answer is operational expenditure (OpEx).
  25. n_l_s_p_t_r_k 👍 1 Answered B
    Non car le modèle de paiement dans azure est le payement à l'utilisation

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Azure Resource Locks for RG Protection

S-grade

Shared Responsibility in Azure SaaS

S-grade

Accessing Azure Cloud Shell via Web Browser

S-grade

Azure VM High Availability SLA Requirements

S-grade

Practice All AZ-900 Questions

Access 90 questions with complete answers and detailed explanations.

View Full AZ-900 Practice Test →

← Back to AZ-900 Study Guide