Your network contains an Active Directory domain named adatum.com. The domain contains a member server
named LON-DC1. LON-DC1 runs Windows Server 2012 andhas the DHCP Server server role installed.
The network contains 100 client computers and 50 IPphones. The computers and the phones are from the
same vendor.
You create an IPv4 scope that contains addresses from 172.16.0.1 to 172.16.1.254.
You need to ensure that the IP phones receive IP addresses in the range of 172.16.1.100 to 172.16.1.200. The
solution must minimize administrative effort.
What should you create?
A.
Server level policies
B.
Filters
C.
Reservations
D.
Scope level policies
Answer D. Scope level policies.
The option to divide up a single scope is done on the scope level policy wizard.
The same range division option is not available when you configure a server level policy.
try it.
I did.
0
0
“A server level policy cannot have a setting for an IP address range.”
– http://technet.microsoft.com/en-us/library/hh831538.aspx
0
0
C
0
0
You don’t want to reserve IP addresses for 50 IP phones. you create a scope policy (as omaw3d says, scope policy has ip range at later step to give to the defined condition). Before you create the policy, you define ‘Vendor class’ in right-click dhcp server/IPv4 or IPv6 node. Then you add a condition for the vendor class and assign ip address.
ANSWER: D
0
0
D
1
0
Answer is D – you need to create SCOPE level policy.
0
0
Yes, answer is D.
http://blogs.technet.com/b/teamdhcp/archive/2012/09/22/using-dhcp-policies-to-set-different-lease-durations-for-different-device-types.aspx
1
0
But no one is thinking of the “same vendor” aspect. It stands pretty clear here: https://technet.microsoft.com/en-us/library/dn425039.aspx
“This is possible using DHCP policies if the devices have different vendors”
So is it really the D? Or maybe it has to be the ambitious C?
0
0
If you read further down the article you are referring to you will see that you can use conditions and combine those with Or and AND.
Still less effort to use conditions that to make reservations for all the ip-phones.
In real life you will have a separate VLAN anyway and not even bother with this 😉
0
0
looking at the question i believe the answer is D, because the range for the IP phone policy would be 172.16.1.100 to 172.16.1.200, this falls inside the scope mentioned earlier in the scenario (172.16.0.1 to 172.16.1.254) so the policy would need to be applied to the scope (D).
0
0
Answer is D for sure!
0
0