AZ-104 Question 142
Single answerYou manage an Azure subscription that runs a Windows Server VM (size: Standard_D2s_v3) in the East US region. Your organization wants to scale this VM to Standard_D8s_v3. However, from the Azure portal's Size blade, you notice the larger size is not listed. What should you do to ensure the desired size is available for selection?
- A
Deallocate the VM first, then resize it to the larger size while it is in the stopped state
- B
Migrate the VM to a region that automatically shows all size options
- C
Attach a larger OS disk, which will unlock the larger VM size options
- D
Recreate the VM using a custom image that supports the new size
Show answer and explanation
Correct answer: A
Explanation
Azure sometimes restricts which VM sizes are visible or selectable when a VM is running. Deallocating the VM first expands the list of available VM sizes in the portal and is often the recommended step to successfully resize a VM to a larger SKU.
- A. Correct.
Stopping (deallocating) the VM first can unlock additional VM sizes that are not shown when the VM is running, allowing you to then select the desired larger size
- B. Incorrect.
Although moving to another region might display different sizes, it’s not necessary if the size is supported in the current region. You should first try deallocation
- C. Incorrect.
While an OS disk must meet minimum requirements for certain sizes, merely increasing the disk might not reveal every larger VM size without deallocation
- D. Incorrect.
Recreating the VM is a more complex approach and is usually not required. Deallocating the existing VM typically allows you to choose a larger size if it’s supported