If the organization has changed naming conventions and needs VM disks placed into containers that comply with the new standard, the direct operational method is to move the VM’s virtual disks to the correct container. In Nutanix, that action is done through live vDisk migration. This preserves workload availability while relocating storage placement to the new destination container that matches policy. The question is really about correcting existing placement, not just defining intent for future objects. ( Nutanix Portal )

The other options do not solve the immediate placement problem. A storage policy can influence behavior, but it does not retroactively relocate already placed vDisks unless that policy is tied to an action that changes their storage location. Image placement policy affects images, not existing VM disk residency. Renaming storage containers is not the right operational answer here because naming policy changes usually result in a need to place workloads into the correct containers, and administrators do not rely on renaming alone to change where current VM data lives. Nutanix’s management model supports live movement of VM storage, so A is the practical and technically correct answer. ( Nutanix Portal )