What will occur when Server1 attempts to connect to a host that has an IP address of 172.20.10.50?

You have a server named Server1 that runs Windows Server 2016.

Server1 has the following routing table.

What will occur when Server1 attempts to connect to a host that has an IP address of 172.20.10.50?
A . Server1 will attempt to connect directly to 172.20.10.50.
B . Server1 will route the connection to 10.10.0.2.
C . Server1 will silently drop the connection attempt.
D . Server1 will route the connection to 192.168.2.1.

Answer: D

Explanation:

http://www.techrepublic.com/article/understanding-routing-tables/

Latest 70-741 Dumps Valid Version with 259 Q&As

Latest And Valid Q&A | Instant Download | Once Fail, Full Refund

Subscribe
Notify of
guest
4 Comments
Inline Feedbacks
View all comments
Eric
Eric
3 years ago

Not true. They are on the same subnet via the 172.16.0.0 network. That mask is a /12, which takes us from 172.16.0.1 to 172.16.31.254 as usable host addresses. This places them on the same network, and will result in not needing to go through the default route to reach the destination.

SWJW Pokhen
SWJW Pokhen
4 years ago

I would say the answer is A!

IP: 172.20.10.50 applies to route: 172.16.0.0 / 255.240.0.0

IP: 172.16.0.1
= 1010 1100.0001 0000.0000 0000.0000 0001
NM: 255.240.0.0
= 1111 1111.1111 0000.0000 0000.0000 0000

Here you see the first 12 bits determine the Network ID
NID: 172.16.0.0

IP: 172.20.10.50
= 1010 1100.0001 0100.0000 1010.0011 0010
It has the same first 12 bits as IP: 172.16.0.1

So IP: 172.16.0.1/12 is in the same Network as IP: 172.20.10.50/12
Now I hope to have proven to you that 172.20.10.50 applies to the route 172.16.0.0 / 255.240.0.0

(The last IP in NID:172.16.0.0 with 12 bits: 172.31.255.255/12

IP: 172.31.255.255
= 1010 1100.0001 1111.1111 1111.1111 1111
It has the same first 12 bits as IP: 172.16.0.1
)

Csaba Németh
Csaba Németh
4 years ago
Reply to  SWJW Pokhen

I totally agree with you. I don’t understand the “correct” answer.

Easy
Easy
4 years ago

It will connect to 172.20.10.50 but not directly. Since they are on different networks the request has to get forwarded to the default gateway to get routed to another network.