This question is about CPU feature compatibility, not storage or networking uniformity. Nutanix documentation and KB guidance explain that VM migration can fail when clusters contain nodes with different CPU generations or different exposed CPU features. A VM that is already running with features negotiated on a newer-generation CPU may not live-migrate successfully to an older or feature-different node until it is power-cycled or configured with advanced processor compatibility. That makes C the correct answer. ( portal.nutanix.com , portal.nutanix.com , portal.nutanix.com )

The important subtlety is that “same core count, memory, storage, subnet, and software version” does not guarantee CPU-feature equivalency. Firmware or ADS activity is not the primary issue described. Affinity rules can restrict placement, but the classic symptom after mixing repurposed nodes is CPU compatibility. Nutanix also documents that advanced processor compatibility settings persist across migrations and power cycles, reinforcing that CPU exposure is the real gating factor here.

A required RPO of 5 minutes immediately points to NearSync replication, because Nutanix documents NearSync protection policies as supporting recovery points in 1–15 minute intervals. The second requirement—automatically protect new mission-critical VMs—points to a Protection Policy approach in Prism Central, because protection policies can use categories and policy-based assignment to scale protection dynamically as new matching VMs are added. Combining those two requirements makes Protection Policy with NearSync replication the correct answer. ( Nutanix )

Protection Domains can support NearSync in older or alternate workflows, but the phrase “new mission critical VMs should be automatically protected” is the clue that pushes this question toward policy-based protection rather than manually maintained membership. Asynchronous replication also fails the first requirement because its RPO target is not the 5-minute class represented by NearSync. Nutanix’s modern DR design encourages policy-driven protection for scalable, category-based administration. Therefore B is the best fit for both the RPO and automatic-inclusion requirements. ( Nutanix )

A Nutanix vDisk live migration moves the VM’s virtual disks into a new storage container while the VM remains online. For that to complete, the destination container must have enough available capacity to receive the migrated vDisk objects. If the target container lacks space, the migration can stall or fail because Nutanix cannot fully place the destination copy and complete the handoff. This makes insufficient storage space in the target storage container the most direct explanation. Nutanix migration and storage workflows consistently rely on adequate target-side capacity before the move can finish successfully. ( portal.nutanix.com )

The distractors are less precise. Source-side snapshots can be part of protection or internal workflow behavior, but the question is specifically about moving to a new container, so target capacity is the key gating factor. “Local storage container” is too vague and is not the normal object referenced in this workflow. Operationally, the right next step is to confirm free space, reservations, and any capacity constraints on the destination container before retrying the migration. That is why B is the best answer.