An administrator created a new Tier-1 Gateway and is attempting to change the connected gateway for a deployed segment to use the new gateway. In the UI, when the administrator clicks the Connected…

Question

Options

• AThe Tier-1 Gateway is not connected to an NSX Edge Cluster.
• BThe Tier-1 Gateway connectivity policy is set to "None".
• CThe Tier-1 Gateway and NSX Segment are in different transport zones.
• DThe Tier-1 Gateway and NSX Segment are connected to different Tier-0 Gateways.

• A
  7% (2)
• B
  3% (1)
• C
  73% (22)
• D
  17% (5)

Explanation

In VMware Cloud Foundation networking, the relationship between segments and gateways is governed by the underlying Transport Zone (TZ) configuration. A Transport Zone defines the potential span of a virtual network--specifically, which hosts and edges can participate in that When an administrator creates an NSX Segment, they must associate it with a specific Transport Zone (either Overlay or VLAN). Similarly, when a Tier-1 Gateway is created, its reach is determined by the Transport Zones available on the Transport Nodes (Edges and ESXi hosts) where it is instantiated. For a Segment to be attached to a Tier-1 Gateway, both objects must reside within the same Transport Zone. If the Segment was created in "Overlay-TZ-01" but the new Tier-1 Gateway is only associated with "Overlay-TZ-02" (or if one is in a VLAN TZ and the other in an Overlay TZ), the NSX Manager UI will filter out the incompatible gateway to prevent an invalid configuration. The logical switch (Segment) cannot bind to a gateway if they do not share a common broadcast or encapsulation domain defined by the Transport Zone. Option A is incorrect because a Tier-1 Gateway does not strictly require an Edge Cluster unless it is providing stateful services (like NAT, LB, or Firewall). It can exist purely as a distributed component on the hypervisors. Option B (Connectivity Policy) determines if the T1 advertises routes to the T0, but it doesn't prevent a segment from connecting to it. Option D is also incorrect, as a Tier-1 Gateway can be moved between Tier-0s, or even exist without a Tier-0 connection initially. Therefore, the Transport Zone mismatch is the fundamental architectural barrier preventing the gateway from appearing in the selection list.

No community discussion yet for this question.