During a data-center refresh, your team is replacing hard-coded static IPv4 addresses with DHCP-assigned addresses for every Windows and Linux server. One three-node application cluster must still be reachable on its existing IP addresses so that firewall rules and reverse-lookup (PTR) records stay valid-even after the nodes are re-imaged from a template. Operations wants the solution managed entirely on the DHCP server so administrators never have to touch the network settings inside the guest OSs. Which DHCP configuration best meets these requirements?
Enable DHCP failover in load-balancing mode so the lease database is synchronized between two servers.
Define an exclusion range that contains the cluster IPs, then manually configure those addresses inside the virtual machines.
Create a reservation that maps each node's MAC address to its current IP and set the NICs to request an address via DHCP.
Configure network switches to insert DHCP Option 82 information so the server returns the same IP on every renewal.
A DHCP reservation permanently binds a client identifier-typically the network adapter's MAC address-to a specific IP address inside the scope. When the cluster nodes are set to obtain an address automatically, the DHCP server always leases the reserved address to the correct node, satisfying the need for a consistent IP while keeping central management.
An exclusion range only prevents the DHCP server from handing out the address; it still requires the administrator to configure a static IP on each node, which the scenario seeks to avoid. DHCP failover provides redundancy for the lease database, not deterministic addressing for an individual client. Option 82 merely adds relay-agent information so the server can apply network-based policies; it has no role in forcing the same address to be issued to a specific host.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.