You manage a server infrastructure for a software development company. There are 30 physical servers distributed across 4 subnets, and one Microsoft Hyper-V
cluster that can run up to 100 virtual machines (VMs). You configure the servers to receive the IP address from a DHCP server named SERVER1 that runs
Microsoft Windows Server 2012 R2. You assign a 30-day duration to all DHCP leases.
Developers create VMs in the environment to test new software. They may create VMs several times each week.
Developers report that some new VMs cannot acquire IP address. You observe that the DHCP scope is full and delete non-existent devices manually. All physical
servers must keep their current DHCP lease configuration.
You need to ensure that the DHCP lease duration for VMs is 8 hours.
What should you configure?
A.
4 server-level Allow filters
B.
1 server-level DHCP policy
C.
1 scope-level DHCP policy
D.
4 scope-level exclusion ranges
Correct:
“Polices are configured at the scope level to control IP address range and at the server level to specify lease duration”
https://technet.microsoft.com/en-us/library/dn425039(v=ws.11).aspx
0
0
The answer is correct, but the reply of eraser isn’t complete.
You CAN set lease time at scope level, but if you want to change lease time based on a specific class you have to configure it at the server level.
0
0
Le Go, you can specify a vendor class at scope level too.
0
0
eraser has taken a quote out of context. The quote is not true in general, it only applies to the example to which the quote belongs on the mentioned web page.
0
0
The correct answer is C; 1 scope-level DHCP policy.
There are 4 subnets. Only the developers report that some new VMs cannot acquire an IP address. In other words, other devices still get IP addresses, so the other devices belong to other DHCP scopes. The DHCP scope is full, the story reads, so the VMs have their own DHCP scope.
If we want to change the lease configuration for the VMs, but we must make sure that the physical servers in other DHCP scopes keep their current DHCP lease configuration, we need to create 1 scope-level DHCP policy for the DHCP scope of the VMs.
If you would create 1 server-level DHCP policy, it would apply to all DHCP scopes, so also to the DHCP scope of the physical servers and that was something that we must prevent, according to the question.
1
1
C should be the right answer. We need to create a scope policy and not the server side policy
1
1
B – Server Level
You create one server level policy and use the MAC Address as the criteria. Microsoft Hyper-V uses 00-15-5D as the prefix for all MAC addresses that it assigns. This way you can assign the DHCP lease time to Hyper-V clients.
3
1
Answer is C. I tested this in lab and confirmed. Here is a link that accomplishes the above scenario
https://blogs.technet.microsoft.com/teamdhcp/2012/09/22/using-dhcp-policies-to-set-different-lease-durations-for-different-device-types/
2
1
In addition we must consider this:
1) “You observe that the DHCP scope is full and delete non-existent devices manually” – one scope is full, not scopes
2) “All physical servers must keep their current DHCP lease configuration.” – we do not have information that they have static IP configuration, so we cannot apply IPv4 lease changing policies to Hyper-V hosts
3) “You need to ensure that the DHCP lease duration for VMs is 8 hours” – again, for VMs, not for all servers.
So, answer must be C. 1 scope-level DHCP policy
0
0
OK. Technically we could create policy with MAC address filter for Hyper-V VMs and then apply this at DHCP server level, but again, we have information one scope is full, not scopes.
0
0