Your network 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.
You implement an additional DHCP server named Server2 that runs Windows Server 2012
R2.
You need 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:
http://blogs.technet.com/b/canitpro/archive/2013/07/10/step-by-step-dhcp-high-availabilitywith-windowsserver-2012-r2.aspx
http://technet.microsoft.com/en-us/library/hh831385.aspx
Configure DHCP failover on the server that created the scope. In this case Server1 created
Scope1 therefore DHCP Failover should be configured on Server1
C is correct
http://technet.microsoft.com/en-us/library/hh831385.aspx
Configure DHCP failover on the server that created the scope. In this case Server1 created Scope1 therefore DHCP Failover should be configured on Server1
Since the scope is DHCPv6, why wouldn’t the answer be “B”?
From http://technet.microsoft.com/en-us/library/dn338983.aspx
“DHCP failover supports DHCPv4 scopes only. DHCPv6 scopes cannot be failover-enabled.”
I agree with Jon,
B is the correct answer.
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.
The answer is B. Good research Jon!!
premium file is C.
it’s B. dhcp failover not supported ipv6.
i dont understand
I’ve got the latest premium file and it says B.
please send me premium file
[email protected]
Please send me a premium file.
You need to do more than commit your answers to rote memory.
Premium file says wrongly that it’s B (failover),but technet clearly says that failover is NOT SUPPORTED in ipv6.
So, what’s the part that you don’t understand ?
Also, if your read technet, it tells you that a scope will do the trick.
Premium files LIE!
I dont understand all this infatuation with premium files. All a premium file is, is some cunt finds the most popular 200-300 reoccurring questions, pastes them (probably off this site) and slaps it into a shitty PDF with some lame ass watermark.
Nowhere anywhere do Premium files mention that the answers are 100% correct.
In fact, I combined 360+ of my own questions from different 70-412 dumps and researched the fuck out of all 360+ questions and made sure I had the right answer.
Ive read so many technet articles and these forums and experimented in my own lab.
I honestly have the ultimate 70-412 PDF with 99% accuracy of answers that i created on my own.
please send me premium file damemalov dude As soon As possible my exam is on mon 🙁 !!!
[email protected]
I hope everyone spams your email with penis enlargement ads
Please send me this premium file!
Thank you for attention
[email protected]
plz send me also the premium file. my exam is on Friday.
[email protected]
The answer is B. DHCP failover is not supported with IPv6.
http://technet.microsoft.com/en-us/library/dn338983.aspx
DHCP failover and IPv6
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.
Please send me this premium file. Thanks so much!!!
please update exam 70-486 exam after 2 day
could please send it to me also the premium file.
i really need to pass the exam after i failed last week.
thanks a lot in advance.
[email protected]
🙂
please send one premium file… thanks a lot in advance
please send one premium file… thanks a lot in advance
[email protected]
NO, no one can!
you guys are corrupting this forum, start studding instead… or leave it if you can’t.
Thanks a lot in advance!!!
Please send me the premium file. Thanks in advance.
[email protected]
Please sen me the premiun file, thanks
Please send me the premion file thanks
[email protected]
please send me the premium [email protected]
Pease send me the premiun file . thanks
[email protected]
Below content i took from sam’s link. since failover doesn’t applicable for IPV6 the answer is B.
DHCP failover in Windows Server 2012 provides support for a maximum of two DHCP servers, and the failover relationship is limited to IPv4 scopes and subnets. Network nodes using Internet Protocol version 6 (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:
DHCP failover and IPv6
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.
https://technet.microsoft.com/nl-nl/library/dn338983.aspx#ipv6
http://blogs.technet.com/b/canitpro/archive/2013/07/10/step-by-step-dhcp-high-availability-with-windows-server-2012-r2.aspx
please send ne premium file:[email protected]. thx
please send one premium file… thanks a lot in advance
[email protected]
To get the premium file working you have to have an active account guys i do believe so just getting it sent wont work
What do you mean Bob ? Please explain.
has to be B…
A – NLB is not minimal effort
B – 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.
C – Not supported by IPV6
D – not exactly highly available
This settles it. good explanation.
the answer is B confirmed by exam 100%
Kindly send me the premium file pls. Thanks in advance.
send here pls… [email protected]
DHCP Failover in Windows Server 2012 supports IPv4 DHCP Scopes only. When using IPv6, most organizations use stateless IP autoconfiguration, where the DHCP servers don’t maintain individual IPv6 Address leases. In this case, setting up two standalone DHCP servers with identical DHCP options defined for each scope is sufficient for providing DHCP HA, and DHCP Failover is unnecessary.
Please can anyone send me the 70-412 updated dumps
email [email protected]
Please send me the premium file. Thanks in advance
[email protected]
B is the correct answer.
The key to the correct answer is IPV6
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.
https://technet.microsoft.com/en-us/library/dn338983(v=ws.11).aspx#ipv6
You need to provide high availability for Scope1, thats the request.
Following technet:
“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.”
So to have high available IPv6 Scope, we should create the Scope with identical option configuration on Server2 🙂
Answer is B.
I get that it’s not DHCP failover but shouldn’t it be ‘D’ – setup failover clustering (and then add a DHCP role in)?
On the wording, it doesn’t just say that DHCP as a service should be HA but that SCOPE1 SPECIFICALLY should be HA.
Surely the only way to do that is D, right? Otherwise the scope isn’t highly available – there are just TWO scopes which are cleverly configured.
Sure, DHCP as a resource is cool and the effect is as desired but SCOPE1 itself wouldn’t be HA with B.