A vSAN administrator wishes to implement HCI mesh between two clusters that are located in geographically separate data centers. Which two possible options must the vSAN administrator choose to…

Question

Options

• ANIC teaming implemented for the vSAN network VMkernel port
• BA leaf spine topology for core redundancy and reduced latency
• CSpan vSAN cluster communication across the same Layer 2 network
• DRoute vSAN cluster communication via different vSAN networks over Layer 3
• EvSAN encryption disabled prior to configuring HCI mesh

• A
  5% (2)
• B
  13% (5)
• C
  55% (21)
• E
  26% (10)

Explanation

vSAN HCI Mesh requires clusters to communicate over a reliable, low-latency network, and the supported configurations are: - Span vSAN cluster communication across the same Layer 2 network: This is the simplest and preferred setup, as it provides seamless connectivity between clusters for shared datastore - Route vSAN cluster communication via different vSAN networks over Layer 3: vSAN 7 Update 2 and later supports Layer 3 HCI Mesh, allowing clusters in different Layer 3 subnets or geographically separate data centers to connect as long as network requirements (bandwidth, latency, and MTU) are met.

No community discussion yet for this question.