Azure DevTest Labs vs Reserved VMs for Short-Term VMs
Note: The question is included in a number of questions that depicts the identical set-up. However, every question has a distinctive result. Establish if the solution satisfies the requirements. Your company's developers intend to deploy a large number of custom virtual machines on a weekly basis. They will also be removing these virtual machines during the same week it was deployed. Sixty percent of the virtual machines have Windows Server 2016 installed, while the other forty percent has Ubuntu Linux installed. You are required to make sure that the administrative effort, needed for this process, is reduced by employing a suitable Azure service. Solution: You recommend the use of Azure Reserved Virtual Machines (VM) Instances. Does the solution meet the goal?
Community Insight
The trap is confusing a billing discount (Reserved Instances) with an operational solution (DevTest Labs) designed to automate and reduce administrative effort for ephemeral environments.
This question evaluates the suitability of Azure Reserved VM Instances for short-lived workloads. The correct answer is B because Reserved Instances are a cost-saving pricing model, not a deployment management tool.
Many learners choose 'Yes' assuming any Azure service helps with VMs, failing to recognize that Reserved Instances require long-term commitments incompatible with weekly removal.
Community Discussion (29 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The solution does not meet the goal because Azure Reserved Virtual Machine (VM) Instances are a billing commitment, not a management tool. Reserved VMs provide discounts in exchange for a one- or three-year term commitment, which contradicts the requirement of deploying and removing VMs on a weekly basis. You cannot effectively use a long-term reservation for short-lived, disposable resources.Why the Other Options Are Wrong
Option A is incorrect because the administrative effort would actually increase or remain high without a management layer, and the cost structure is mismatched. There is no option C or D; the binary choice relies on understanding the fundamental purpose of Reserved Instances versus services like Azure DevTest Labs, which are specifically designed for creating reusable templates and managing lifecycle of test/dev VMs efficiently.Community Comment Notes
Community consensus strongly supports Option B. Users highlight that Reserved Instances are for "consistent resource usage" and that they are a "pricing plan," not a deployment tool. Several comments explicitly mention that Azure DevTest Labs would be the appropriate solution for this scenario (Comments 1, 9), confirming that the proposed solution fails to address the administrative efficiency requirement.Exam Strategy
Always distinguish between pricing models (like Reserved Instances or Savings Plans) and operational tools (like DevTest Labs or Automation Accounts). If a question asks about reducing administrative effort for frequent creation/deletion, look for automation or lab services, not billing discounts.
Frequently Asked Questions
Why are Reserved VMs bad for weekly VMs?
Reserved VMs require a 1-3 year commitment. Deploying and deleting VMs weekly makes this commitment impractical and financially wasteful.
What Azure service should I use instead?
Azure DevTest Labs is ideal for this scenario as it allows reusable templates and artifacts to reduce administrative effort for dev/test VMs.
Related Analysis
Practice All AZ-900 Questions
Access 90 questions with complete answers and detailed explanations.
View Full AZ-900 Practice Test →