Answer-first summary for fast verification
Answer: No
The correct answer is 'No' because the term 'elastic expenditure model' is not a recognized Azure expenditure model. Azure's official expenditure models are 'pay-as-you-go' (operational expenditure/OpEx) and 'reserved instances' (which can align with capital expenditure/CapEx for committed usage). The community discussion, with the top comment having 19 upvotes and multiple others reinforcing this point, clearly indicates that 'elastic expenditure model' is not standard Azure terminology. While pay-as-you-go provides elasticity in resource scaling, the expenditure model itself is not called 'elastic.' The proposed solution uses incorrect terminology, so it does not meet the goal of ensuring the correct expenditure model is used.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
Your company is planning to migrate all its virtual machines from on-premises Hyper-V hosts to an Azure pay-as-you-go subscription. You need to ensure the intended Azure solution uses the correct expenditure model.
Proposed Solution: Recommend the use of the elastic expenditure model.
Does the proposed solution meet the goal?
A
Yes
B
No