You work as an administrator at ABC.com. The ABC.com network consists of a single domain
named ABC.com. All servers in the ABC.com domain, including domain controllers, have Windows
Server 2012 R2 installed.
You add the DHCP Server Role on a server named ABC_SR04. You configure DHCP to support
two subnets named Subnet A and Subnet B. Subnet A has a network ID of 172.16.0.0/16 and
Subnet B has a network ID of 172.16.1.0/24.
All client computers are reconfigured to receive IP addresses from DHCP. However, clients on
Subnet B cannot access clients on Subnet A.
What is the most likely cause of this problem?
A.
The Server Options are not configured correctly.
B.
The IP address for the Router is not correctly specified in the Scope Options.
C.
The IP address for the DNS Sever is not correctly specified in the Scope Options.
D.
The IPv6 has not been disabled on ABC_SR04.
Explanation:
Reference:
http://technet.microsoft.com/en-us/library/ee941211(v=ws.10).aspx
So clients are getting IP addresses but only one segment clients are unable to reach to the other segment clients. If router address wasn’t correct then how did clients got the IP address? Could be DNS issue which is in Option C.
0
0
This is a false question because both IP-ranges are overlapping.
All addresses 72.16.1.0/24 (.0 to .255) are part of 172.16.0.0/16 (.0.0 to .255.255 wich includes .1.0 to .1.255) So you will be unable to route without NAT in between.
0
0
agree with the overlapping subnets, B can’t reach A, bc clients in A assume “subnet B” is directly connected.
so actually A can’t reach B, but that also means traffic from B never gets routed back.
Even if the network ranges were correct then it’s still ambigious. C would be the only option for A can reach B, but B can’t reach A when using a name (it will succeeed on IP). B. will mean that A can’t reach B either or at least not setup a connection as the route back isn’t correct.
crap question. i’d probably go for C.
0
0