Yournetwork contains an Active Directory domain named contoso.com. The domain contains a
server named Server1 that runs Windows Server 2012 R2 and has the DHCP Server server role
installed. Server1 has an IPv6 scope named Scope1.
Youimplement an additional DHCP server named Server2 that runs Windows Server 2012 R2.
Youneed to provide high availability for Scope1. The solution must minimize administrative effort.
What should you do?
A.
Install and configure Network Load Balancing (NLB) on Server1 and Server2.
B.
Create a scope on Server2.
C.
Configure DHCP failover on Server1.
D.
Install and configure Failover Clustering on Server1 and Server2.
Explanation:
Overview: Configure DHCP failover using the DHCP console
Toconfigure DHCP failover using the DHCP console, right-click a DHCP scope or right-click IPv4 and
then click Configure Failover.
The Configure Failover wizard guides you through configuring DHCP failover on the selected scope.
Note: The DHCP server failover feature, available in Windows Server 2012 and later, provides the
ability to have two DHCP servers provide IP addresses and option configuration to the same subnet
or scope, providing for continuous availability of DHCP service to clients.
Incorrect:
Not A. NLB is not related to DHCP scope availability.
Not B. DHCP failover requirements include:
DHCP Scopes requirement:
At least one IPv4 DHCP scope must be configured on the primary DHCP server.
The same DHCP scope ID, or an overlapping scope, must not be configured on the failover partner.
Not D. Failover clustering is possibly, but would not minimize administration.
Deploy DHCP Failover
DHCP failover is not supported for Internet Protocol version 6 (IPv6) scopes. Network adapters using IPv6 typically determine their own IPv6 address using stateless IP auto-configuration. In this mode, the DHCP server delivers only the DHCP option configuration, and the server does not maintain any lease state information. A high availability deployment for stateless DHCPv6 is possible by simply setting up two servers with identical option configuration. Even in a stateful DHCPv6 deployment, the scopes do not run under high address utilization, which makes split scope a viable solution for high availability.
B.
6
0
I Agree with @Jakub, IPv6 is not supported.
https://technet.microsoft.com/en-us/library/dn338983(v=ws.11).aspx#ipv6
B is the correct answer.
3
0
B
3
0
Yep, looks good
– Answer C if it’s IPV4
– Answer B if it’s IPV6
Thanks guys for the explantation (& link)!
2
0
Answer: B
A could result in duplicate IP addresses being assigned.
C IPv6 Failover is not supported by DHCP in 2012.
D Failover Cluster DHCP Role does not support IPv6 High Availability as each node is configured in a failover DHCP relationship meaning it won’t work for IPv6.
The question is worded poorly since it states make Scope1 highly available….which technically can’t be done. The scope must be split and a portion of it assigned to each server.
https://technet.microsoft.com/en-us/library/dn338983%28v=ws.11%29.aspx?f=255&MSPPError=-2147217396#ipv6
2
0