Comprehensive and Detailed 250 to 350 words of Explanation From VMware Cloud Foundation (VCF) documents:
InVMware 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 aDHCP Relayon 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 aDHCP Relay profile, the native NSX DHCP capabilities for that specific segment are disabled. This means thatDHCP 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.
Option C is incorrect because the UI will physically grey out or prevent the entry of native DHCP parameters once the Relay is selected. Option B is incorrect as the primary purpose of a Relay is precisely to forward requests to external servers. Option D is incorrect because a DHCP Relay is configured on a per-segment or per-gateway basis; it is not a "global" service that automatically covers all other segments in the network. Therefore, the architectural trade-off when choosing a Relay is the shift of all management and binding logic to the external physical or virtual DHCP appliance.
===========
