Exam AZ-900 topic 1 question 11 discussion

Answer is NO. Because we have two expenditure models. One is Cap-Ex, another is Op-Ex. So Scalable Expenditure is not the right answer.

Answer is No. Operating expenditures are ongoing costs of doing business. Consuming cloud services in a pay-as-you-go model could qualify as an operating expenditure. https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/strategy/business-outcomes/fiscal-outcomes

Scalable Expenditure is not an example of Azure expenditure models

The answer is Yes as per chat GPT,The scalable expenditure model refers to a consumption-based or operational expense (OpEx) approach — meaning you only pay for the resources you use.

Moving to Azure on a pay-as-you-go subscription is an example of a scalable (elastic) expenditure model. Azure VMs allow auto-scaling, and charges are incurred only when VMs are running, aligning with scalable OpEx. This model enables cost control and flexibility, which is a primary benefit of migrating to the cloud.

The scalable expenditure model is another way to describe cloud-based consumption pricing, where costs scale based on actual usage. This model is inherent to Azure's pay-as-you-go subscription. ✔️ Why this meets the goal: Pay-as-you-go is scalable by design — as you add or remove resources, costs adjust accordingly. There's no upfront investment; you pay only for what you use, which aligns with Opex (operational expenditure). It's ideal for cloud migrations from environments like Hyper-V, especially when flexibility and cost efficiency are key.

No, its Operating expenditures (OP-EX).

Só temos dois modelos de Gasti CapEx e Opex

Describe the consumption-based model - Training | Microsoft Learn

For more clarity. The "pay-as-you-go" model is typically considered an operational expenditure (OpEx). This is because it involves ongoing costs for services or resources, rather than a one-time capital expenditure (CapEx) for purchasing assets. In a pay-as-you-go model, you pay for what you use, which aligns with the nature of operational expenses. CapEx, on the other hand, refers to the upfront costs of acquiring or upgrading physical assets like buildings, machinery, or equipment. So, in this context, "pay-as-you-go" would be classified as OpEx.

No, its Operating expenditures (OP-EX).

B. No The solution does not meet the goal. "Scalable expenditure model" is not a valid expenditure model in Azure. The recommended expenditure model for the pay-as-you-go subscription is the Consumption model. The Consumption model allows for billing based on actual usage of Azure resources, such as virtual machines and storage, and provides the ability to monitor and manage costs through Azure cost management tools. Therefore, the proposed solution of using the "scalable expenditure model" does not meet the goal, and the recommended expenditure model for the pay-as-you-go subscription is the Consumption model.

The answer is B. No The term "scalable expenditure model" still isn't a standard term in Azure or cloud computing. The 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. 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 "scalable expenditure model" is not an accurate description of an established concept in Azure, so the solution is not correct. The appropriate description for the chosen expenditure model is "pay-as-you-go."

The solution does not meet the goal. There is no such thing as a "scalable expenditure model" in Azure. The two expenditure models in Azure are pay-as-you-go and reserved instances. Pay-as-you-go 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 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. Since the question states that the company is planning to migrate all of their virtual machines to an Azure pay-as-you-go subscription, the correct expenditure model is pay-as-you-go. Therefore, the solution does not meet the goal

I think I might be the only person to pick A - yes. For this reason. First don't get bogged down in the weeds about Cap-Ex and Op-Ex. i.e. "Scalable" doesn't match one of these. Get over it. But you know what does happen. If I buy Hardware that would be CAP-EX. If I am preparing to scale out and using Azure... then ... you guessed it. That is OP-EX. So yes... we finally circle back to a term that you all seem to focus on ina binary black/white way. Then finally let's go with what is acutally presented. We are told we are planning to migrate to Virtual Machines in an Azure Pay as you go subscription model (Op=Ex). The SOLUTION: says we should recommend scalable expenditure. Reason this carefully, Isn't therefore, Azure a scalable expentiure model that reflects the cheries buzz-word Pay-AS-You Go? Why yes it does... and for that reason the answer should be A yes.

https://azure.microsoft.com/en-in/pricing/offers/ms-azr-0003p

No, instead of scalable, you need elastic. "Scalable : environments only care about increasing capacity to accommodate an increasing workload. Elastic : environments care about being able to meet current demands without under/over provisioning, in an autonomic fashion. "