Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft AZ-900 Exam - Topic 1 Question 129 Discussion

Actual exam question for Microsoft's AZ-900 exam
Question #: 129
Topic #: 1
[All AZ-900 Questions]

You have 1,000 virtual machines hosted on the Hyper-V hosts in a data center.

You plan to migrate all the virtual machines to an Azure pay-as-you-go subscription.

You need to identify which expenditure model to use for the planned Azure solution.

Which expenditure model should you identify?

Show Suggested Answer Hide Answer
Suggested Answer: A

One of the major changes that you will face when you move from on-premises cloud to the public cloud is the switch from capital expenditure (buying hardware) to operating expenditure (paying for service as you use it). This switch also requires more careful management of your costs. The benefit of the cloud is that you can fundamentally and positively affect the cost of a service you use by merely shutting down or resizing it when it's not needed.

https://docs.microsoft.com/en-us/azure/architecture/cloud-adoption/appendix/azure-scaffold


Contribute your Thoughts:

0/2000 characters
Joesph
16 days ago
I think elastic makes more sense for scaling needs.
upvoted 0 times
...
Goldie
21 days ago
Definitely operational, since it's pay-as-you-go.
upvoted 0 times
...
Bulah
1 month ago
I feel like elastic and scalable are more about resource management rather than expenditure models. So, I’m leaning towards operational too.
upvoted 0 times
...
Whitley
1 month ago
This question reminds me of a practice test where we discussed the differences between operational and capital expenditures. I think operational is the right choice.
upvoted 0 times
...
Audra
2 months ago
I'm not entirely sure, but I remember something about capital expenditures being more about upfront costs, which doesn't fit here.
upvoted 0 times
...
Tomoko
2 months ago
I think the operational expenditure model makes sense since we're moving to a pay-as-you-go model in Azure.
upvoted 0 times
...

Save Cancel