NSX Federation uses a Global Manager to centrally define and synchronize global networking and security objects across the Local Managers at participating sites, making F fundamental to the architecture. Broadcom confirms that configuration is performed through the active Global Manager and synchronized to the applicable locations. ( Broadcom TechDocs )

A is required for stretched North/South routing: a Global Tier-0 can span locations, with site-local service routers and BGP connectivity to the physical network. Federation also uses RTEPs on Edge Nodes for cross-site Geneve transport.

B reflects the important 150-ms cross-location Edge-to-Edge RTT limit for stretched networking. Newer NSX releases permit higher latency between some manager components, but the inter-site Edge data path remains subject to the tighter latency consideration.

C is correct because NSX overlay networking requires additional MTU for Geneve encapsulation. Broadcom specifies 1600 bytes as the minimum and 1700 bytes as the recommended value , making 1700 the appropriate design target.

E separates site-local routing from stretched workloads: local Tier-1 gateways serve site-specific segments, while a Global/spanning Tier-1 provides cross-site connectivity. Broadcom confirms that local Tier-1 gateways can connect to a Global Tier-0 in Federation.

D is too absolute, particularly with distributed VPC connectivity models. G is incorrect because Edge TEP addressing is normally based on NSX IP pools/static allocation rather than requiring DHCP. H provides insufficient MTU for Geneve overlays.

Study Guide References/Topics: NSX Federation Architecture; Global and Local Managers; Stretched Tier-0/Tier-1 Gateways; RTEPs; Multi-Site BGP Routing; Geneve MTU; Local versus Global Networking Objects; Multi-Site Availability.