Topic 1 · Question 10
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?
A. Yes
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."