Exam AZ-900 topic 1 question 10 discussion

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."

scalable, not elastic.

The answer is B. No

Os dois modelos de despesas comuns no Azure são "pagamento conforme o uso" e "instâncias reservadas".

La respuesta es b

"Elastic expenditure" is not a valid term in Azure pricing.

Azure’s pay-as-you-go subscription follows the OpEx (Operational Expenditure) Model, not the "Elastic Expenditure Model."

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.

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.

It's yes

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

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."

This model is not relevant for this question

There are 2 types: operational expenditures - pays as you go capital expenditure - pay in the advance

Answer is 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.

So the answer is no - B.