An application needs more data disk capacity, but the VM can keep using the same managed disk. Which two statements are true when you resize a managed data disk? Select two.

You must create a brand-new VM before resizing the disk.

Disk expansion does not require replacing the VM when only storage capacity changes.

Resizing a disk always shrinks it back to a smaller size.

The common Azure operation here is expansion, not automatic shrinking of a managed disk.

The VM size must always change whenever disk capacity changes.

VM compute size and managed disk size are separate settings and do not always change together.

What does this AZ-104 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: You can increase the managed disk size without redeploying the VM. — When a managed data disk needs more capacity, the Azure-side disk size can be increased without redeploying the VM. That changes the available storage, but the guest operating system may still need a partition or filesystem extension to use the new space. This is a common operational step in Azure administration. The process separates disk resizing in Azure from volume expansion inside the VM. Why others are wrong: A new VM is not required just to increase disk capacity. Shrinking a disk is not the usual supported action in this scenario, and changing the VM size is unrelated to the disk size in many cases. The important concept is that Azure disk capacity and in-guest volume size are separate layers, so both sides may need attention.

What should I do if I get this AZ-104 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.