Your network has a router named Router1 that provides access to the Internet. You have a server named
Server1 that runs Windows Server 2012 R2. Server1 to use Router1 as the default gateway.
A new router named Router2 is added to the network. Router2 provides access to the Internet. The IP address
of the internal interface on Router2 is 10.1.14.2S4.
You need to configure Server1 to use Router2 to connect to the Internet if Router1 fails.
What should you do on Server1?
A.
Add a route for 10.1.14.0/24 that uses 10.1.14.254 as the gateway and set the metric to 1.
B.
Add 10.1.14.254 as a gateway and set the metric to 1.
C.
Add a route for 10.1.14.0/24 that uses 10.1.14.254 as the gateway and set the metric to 500.
D.
Add 10.1.14.254 as a gateway and set the metric to 500.
Explanation:
To configure the Automatic Metric feature:
1. In Control Panel, double-click Network Connections.
2. Right-click a network interface, and then click Properties.
3. Click Internet Protocol (TCP/IP), and then click Properties.
4. On the General tab, click Advanced.
5. To specify a metric, on the IP Settings tab, click to clear the Automatic metric check box, and then enter the
metric that you want in the Interface Metric field.
To manually add routes for IPv4
Open the Command Prompt window by clicking the Start button Picture of the Start button. In the search box,
type Command Prompt, and then, in the list of results, click Command Prompt.
At the command prompt, type route -p add [destination] [mask <netmask>] [gateway] [metric <metric>] [if
<interface>].
I’d pick D
If someone got an explanation why it should be C please let me know.
Agreed, adding a route to the 10.1.14.0/24 network [route add 10.1.14.0 mask 255.255.255.0 10.1.14.254 metric 500 -p] does nothing because it is the directly connected network.
Adding a default gateway of 10.1.14.254 with a metric of 500 is the same as adding the following route [route add 0.0.0.0 mask 0.0.0.0 10.1.14.254 metric 500 -p]. This route states that any destination not in the local network will use the 10.1.14.254 as its default gateway if it has the lowest metric of available gateways.
Agree with D
Agree with D.
I think that the key to the reading of the question is that Router2 provides access to the internet. Therefore, its use should be restricted to that (i.e. confined to that subnet). D is setting a generic gateway for all routing.
So I believe the correct answer to another ambiguous question is most likely C.
I am changing my answer to D. Upon further review C doesn’t make sense, since it only specifics a route to a specific subnet. Answer D provides a simple gateway (a way to get out) with a metric higher than that for Router1 (assumed based on the answers provided, but it cannot be “1” which would have the highest priority)
Also you can look at the responses here:
http://www.aiotestking.com/microsoft/you-need-to-configure-server1-to-use-router2-to-connect-to-the-internet-if-router1-fails/
It’s D.
In this scenario they aren’t asking about any command line stuff. Just get NIC adapter properties, select IPV4, advanced and add another gateway with a higher metric.
If this was from the command line you would still need an undefined route statement:
0.0.0.0 for both the subnet and the mask and the metric option would be set to 500:
route add 0.0.0.0 MASK 0.0.0.0 10.1.14.254 METRIC 500 IF 1
Route add is obvious
0.0.0.0 is undefined traffic (internet)
Mask is 0.0.0.0
10.1.14.254 is the the additional gateway
Metric is 500
The answer here is obviously D without further delving into the reason why it is D look at the question, it didn’t specify a subnet mask for the Router 2, are we to assume that the 10.1.14.254 is a 32 bit subnet mask?
Has anyone thought of it this way? If you configure another default gateway on the server, even if you set the metric 500 the system will see two default gateway. But if you configure a route and router one goes down, an auto failover
will occur using router two.
Two default gateway will result in a conflict