After a synchronous replication failover, VMs may be running on one site while their storage container remains active on the original site. This forces I/O traffic to traverse the inter-site link, causing high latency. Manually promoting the storage container on the new active site realigns the storage location with the compute (VM) location. This re-establishes data locality, ensuring I/O operations are served locally and restoring optimal performance.

A. Snapshot retention periods are related to data protection schedules and space consumption, not real-time I/O performance or data locality.

C. Reconfiguring the replication schedule affects how often data is synchronized, not the performance of I/O for already-failed-over VMs.

D. Acropolis Dynamic Scheduler (ADS) balances workloads within a cluster. It does not manage data locality across different sites in a metro configuration.

1. Nutanix Prism Element Data Protection and Recovery Guide (AOS 6.7), Chapter: Metro Availability for AHV and ESXi, Section: Planned Failover Scenario for Metro Availability. The documentation states: "To re-enable the protection domain on the promoted site... This step ensures that the writes are local to the site." This action realigns storage and compute.