The requirement states:
* Custom apps use Volume Groups
* VM + VG must remain consistent together
* Lowest possible RPO is required (RPO # 0)
* Must survive cluster failure
Nutanix data protection documentation clearly states:
"Synchronous replication provides an RPO of zero by ensuring every write is committed on both sites before acknowledgement." Additionally:
"When protecting application VMs using Volume Groups, both the VM and the Volume Group must be placed in the same Consistency Group to ensure write-order fidelity and to preserve database or application integrity during failover." This is critical because Volume Groups operate at the block layer, and placing them in separate groups breaks atomic write-order correctness.
Option analysis:
A). Metro AHV provides HA-style zero RPO but is not the required mechanism here because the question specifically references protection policies and VGs, which Metro does not orchestrate in the same way.
B). Synchronous replication alone is not sufficient unless VMs and VGs are inside the same consistency group.
C). This is the correct and complete solution: synchronous replication + consistency grouping ensures RPO0 and atomic updates.
D). NearSync has RPO 1-15 minutes, not the lowest possible RPO.
Therefore, placing both VMs and VGs in the same consistency group under Synchronous Replication is the correct method.

Receive Side Scaling (RSS) VirtIO-Net Multi-Queue improves network performance by distributing network processing across multiple CPU cores.
* Option C (Enable RSS VirtIO-Net Multi-Queue) is correct:
* This settingreduces CPU bottlenecksby allowing multiple queues to handle network packets.
* It isessential for high-throughput network applications.
* Option A (Add more vCPUs) is incorrect:
* CPU resources are important, butwithout enabling RSS, additional vCPUs will not optimize network traffic distribution.
* Option B (Enable AHV Turbo Technology) is incorrect:
* AHV Turbo improvesdisk I/O, notnetwork I/O.
* Option D (Add more RAM) is incorrect:
* RAM does not directly impact network performance.
References:
Nutanix AHV Best Practices Guide #Optimizing Network Performance with RSS Multi-Queue Nutanix KB #Enabling Multi-Queue for High-Performance Applications

Agent VMs, such as CVMs (Controller VMs) or Witness VMs, have strict affinity and anti-affinity rules to ensure they remain on specific hosts and maintain data consistency and high availability. If an agent VM is powered off and then manually started on another host, it becomes unresponsive because it breaks these rules.
From theNutanix Enterprise Cloud Administration (ECA)course materials:
"Agent VMs have specific configuration and affinity constraints. Manually starting them on another host violates these constraints, resulting in the agent VM becoming unresponsive to the cluster." Further clarification:
"The cluster expects the agent VM to be on a particular host. Moving it manually to another host breaks this expectation and causes the VM to be unable to properly join the cluster services, leading to an unresponsive state." Therefore, it is essential to avoid manually starting agent VMs on different hosts, as doing so can disrupt cluster services.