Free VMware 2V0-13.25 Actual Exam Questions - Question 7 Discussion

C/D, SDDC Manager and NSX are core for multi-AZ sync and networking continuity.

B imo, vCenter is crucial across AZs since it manages the ESXi hosts and workloads directly. Without replicating vCenter, you can’t really coordinate VM operations smoothly during failover. SDDC Manager (C) is important but more for higher-level orchestration, and NSX (D) handles networking, but if you don’t have vCenter replicated, you risk losing management control. So I’d go with B and D for replication here, focusing on both management plane and networking continuity.

It’s definitely C and D here. SDDC Manager must be replicated because it coordinates the entire fleet across AZs, and NSX needs to be duplicated to ensure seamless networking and security policies stay intact. vCenter (B) usually doesn’t get fully replicated; it’s more about managing individual clusters rather than being a replicated component across zones. VCF Automation and Operations are important but don’t require replication in this model. So, sticking with SDDC Manager and NSX makes the most sense for a disaster recovery setup spanning two AZs.

C. Along with D, these two make the most sense to me. SDDC Manager is the central piece for managing and orchestrating everything across the zones, and NSX is essential to keep networking consistent between sites. B and E seem less likely since vCenter usually manages local clusters, and Operations is more about monitoring, not replication. A doesn't fit because automation tools don’t typically get replicated like core infrastructure components. So, it’s probably C and D based on their roles in the architecture.

C (SDDC Manager) and D (NSX) for lifecycle and network replication across zones.

Maybe B and D, since vCenter needs to manage hosts in each zone and NSX handles cross-AZ networking.

C/E? SDDC Manager must sync, and Operations likely stays consistent for monitoring.

Probably C and D, both need to stay consistent across zones for management and networking.

C, D makes sense since SDDC Manager coordinates the overall lifecycle and NSX handles the network layer, both need to stay in sync across AZs for DR. vCenter might just be managed separately per zone.

D imo, NSX replication is key for network, and SDDC Manager keeps configs synced.

B/D? I’m thinking vCenter (B) and NSX (D) get replicated since vCenter handles the management of the clusters, and NSX is critical for network continuity across AZs. SDDC Manager (C) seems more tied to lifecycle and might not need full replication, just backup or standby. Also, VCF Automation (A) and Operations (E) are more about orchestration or monitoring, so less likely to be actively replicated across AZs. The key is which components need seamless failover vs. which can be restored later.

C, D — SDDC Manager and NSX definitely need replication for consistent management and networking.

B imo, since vCenter is critical for managing resources across zones.

Option C makes sense too because SDDC Manager handles overall lifecycle management, so replicating it helps keep both zones in sync beyond just vCenter and NSX.

B and D seem right since vCenter and NSX usually get replicated for multi-AZ setups.