When using a DHCP Relay on a segment, which design restriction must be considered?

Question

Options

• ADHCP settings, DHCP options, and static bindings cannot be configured on the segment.
• BDHCP client requests cannot be relayed to the external DHCP servers.
• CDHCP settings, DHCP options, and static bindings can be configured on the segment.
• DDHCP Relay service is available to all the other segments in the network.

• A
  72% (44)
• B
  8% (5)
• C
  3% (2)
• D
  16% (10)

Explanation

In VMware Cloud Foundation (VCF) networking, IP address management within an NSX segment can be handled by either the native NSX DHCP server or by an external DHCP server. When an administrator chooses to use an existing external corporate DHCP infrastructure, they must configure a DHCP Relay on the logical segment. The DHCP Relay works by intercepting the initial DHCP Discover broadcast from a workload VM and forwarding it (as a unicast packet) to the specified IP address of the external DHCP server. However, NSX enforces a strict mutual exclusivity in its configuration logic to prevent conflicts and unpredictable address assignments. According to the "NSX-T Data Center Administration Guide," once a segment is configured to use a DHCP Relay profile, the native NSX DHCP capabilities for that specific segment are disabled. This means that DHCP settings, DHCP options, and static bindings cannot be configured on that segment (Option A). All such configurations, including IP reservations and scope options (like DNS or NTP), must be managed centrally on the external DHCP server.

No community discussion yet for this question.