Metro Availability requires that VMs always read data from their primary site to maintain optimal performance and prevent remote data access latency.
* Option C (Migrate the VM to its primary site and set appropriate rules) is correct:
* If a VMfails over to the secondary sitebut is still running in the primary site, it will read data remotely, causinghigh latency and performance issues.
* The solution is tomigrate the VM back to the primary siteand configureDRS rulesorhost affinity settingsto prevent unwanted movement.
* Option A is incorrect:
* The command listsactive Metro Availability protection domainsbut doesnot resolvethe issue.
* Option B is incorrect:
* Must-affinity rules can help, but they should be configuredafter migrating the VM back to the primary site.
* Option D is incorrect:
* RunningNCC health checkswill onlydiagnose the issue, not resolve it.
References:
* Nutanix Bible #Metro Availability and Data Locality
* Nutanix Best Practices #VM Affinity Rules for Metro Availability
* Nutanix KB #Troubleshooting Remote Data Access in Metro Availability