Your network contains a server named Server1 that runs Windows Server 2012. Server1
has the DHCP Server server role installed.
All of the client computers that are in a subnet named Subnet1 receive their IP address
configurations from Server1.
You plan to add another DHCP server named Server2 to Subnet1.
You need to recommend changes to the DHCP infrastructure to ensure that the client
computers continue to receive IP addressing information if a single DHCP server fails.
What should you do?
More than one answer choice may achieve the goal. Select the BEST answer.
A.
Create a Network Load Balancing (NLB) cluster.
B.
Configure Failover for the scope.
C.
Create a DHCP failover cluster.
D.
Create a split scope.
Explanation:
http://blogs.technet.com/b/keithmayer/archive/2012/10/28/step-by-step-scoping-out-the-newdhcpfailover-inwindows-server-2012-31 -days-of-favorite-features-part-28-of-
31.aspx#.UQhW-b-jbK0
The answer is C, Create a DHCP Failover cluster (new feature)
To be able to configure Failover fot the scope as shown in your printscreen, yo have to have first a DHCP Failover Cluster, then, you can configure a failover relationship for a specific scope.
Frousse, I disagree. DHCP Failover for scopes is a the new feature in Server 2012. DHCP Failover Clusters was around in 2008.
This article details the feature and how it can integrate with a DHCP failover cluster if needed.
https://technet.microsoft.com/en-us/library/dn338983.aspx
The answer is always the new feature for the product. And it makes sense. Implementing a failover scope is REALLY easy (I’ve done it in the real world). Implementing a failover cluster is a pain in the … So, MS made a better feature to remove that headache.
Given answer is correct. Failover for the Scope.
Grammar correction: “DHCP Failover Clusters ‘were’ around in 2008”.
Agree with jimilives 😉