A city wants to migrate permitting VMs between the on-premises civic site and a cloud landing zone, including network stretch assist. Which product supports that use case?
Select an answer to reveal the explanation.
Short Explanation
Moving a permitting app to another site is a moving van plus a temporary network bridge, not a shuffle inside one cluster. HCX is the product that does that migration and stretch. vMotion stays in one vSphere world; vSAN and Intelligence are not the mover.
Full Explanation
VMware HCX is the exam-guide product for migrating permitting workloads between an on-premises civic site and a cloud landing zone, including network stretch assist so agency addressing can move without a big-bang cutover. Think of HCX as the city's moving van plus a temporary network bridge between halls. vMotion relocates a VM among hosts inside a vSphere environment and is not the inter-site or site-to-cloud migration product the township needs for that landing zone. vSAN is software-defined storage for shared datastores; it does not become the inter-site workload migration engine. NSX Intelligence analyzes flows and can recommend security policy, but it is not a site-to-site mover and does not stretch networks for a permitting migration. Exam caveat: HCX and NSX often appear together in architectures, yet the VCTA-NV use-case item that asks for workload mobility with network stretch points at HCX, not at Intelligence or at intra-cluster vMotion. Operational check: before a civic cutover, validate HCX service mesh health between sites, confirm stretch or migration workflows for a pilot permitting VM, and ensure operators are not treating a single-cluster vMotion as proof of site-to-cloud mobility.