Your network contains two subnets. The subnets are configured as shown in the following table.
You have a server named Server1 that runs Windows Server 2012. Server1 is connected to LAN1.
You run the route print command as shown in the exhibit. (Refer to the Exhibit.) 
You need to ensure that Server1 can communicate with the client computers on LAN2.
What should you do?
A.
Change the default gateway address.
B.
Set the state of the Teredo interface to disable.
C.
Change the metric of the 10.10.1.0 route.
D.
Set the state of the Microsoft ISATAP Adapter #2 interface to disable.
Explanation:
In general, the first and last addresses in a subnet are used as the network identifier and broadcast address,
respectively. All other addresses in the subnet canbe assigned to hosts on that subnet.
For example, IP addresses of networks with subnet masks of at least 24 bits ending in .0 or
.255 can never beassigned to hosts. Such “last” addresses of a subnet are considered “broadcast” addresses
and all hosts onthe corresponding subnet will respond to it.
Theoretically, there could be situations where you can assign an address ending in .0: for example, ifyou havea
subnet like 192.168.0.0/255.255.0.0, you are allowed to assign a host the address 192.168.1.0. It couldcreate
confusion though, so it’s not a very common practice.
Example10.6.43.0 with subnet 255.255.252.0 (22 bit subnet mask) means subnet ID 10.6.40.0, a host address
range from 10.6.40.1 to 10.6.43.254 and a broadcastaddress10.6.43.255. So in theory, your example 10.6.43.0
would be allowed as a valid host address.
The default gateway address should not end in .0 with the /24 address
http://tools.ietf.org/html/rfc4632
http://en.wikipedia.org/wiki/IPv4#Addresses_ending_in_0_or_255
None of the answers offered are correct, given the information presented in the graphic.
DougEFresh, A is the least bad answer 🙂 otherwise not only changing of gateway is required rather the ip address as well as the server network cable should also be connected to 10.11.1.0 segment as well.
10.10.1.0/24 is a Network ID, not viable for a gateway address.
Agreed, 10.10.1.0 is not a correct gateway address and should be changed to something in the range of 10.10.1.1-254.
I agree the question makes no sense.
I think the 192.168.2.0 address in this question is the problem
– a possible answer should have been to change it to the 10.11.1.0 address
A is the correct answer
although there is no entry for the 10.11.1.0 network there is a gateway of last resort set (0.0.0.0) which means any traffic destined for a network that is not listed in the routing table will be sent to the quad zero route.
the address listed for the Gateway however as already mentioned is a Network address not a valid address that can be assigned to a device, change the address to a valid one in the range and it will route the traffic to the 10.11.1.0 network correctly