The hardware firewall sits several racks from the GIS hosts, so east-west inspection trombones and adds latency. Which virtual-networking design addresses that inspection-path problem?
Select an answer to reveal the explanation.
Short Explanation
Hairpinning GIS traffic to a far-away firewall is like sending every hallway conversation out to the parking-lot booth. A distributed firewall reads those packets on the host, so the trip is local. A fatter WAN or Horizon Cloud does not shorten that trombone.
Full Explanation
Physical firewalls racked far from compute force east-west flows to leave the host, traverse the fabric, and return—adding latency for civic GIS workloads. NSX-T distributed firewall inspects at the vNIC on the host, so inspection does not depend on a distant hardware appliance. Relocating the hardware pair but still hairpinning, upsizing WAN circuits, or steering traffic through Horizon Cloud leaves the trombone path in place.