Switch(config)# ip route 172.16.2.0/30 192.168.1.100 metric 1 distance 1
Why does this route fail to appear in the IP routing table?
Its prefix length is invalid.
Its next hop is unreachable.
Its administrative distance is the same as an existing static route.
Its metric is the same as an existing static route.
Correct answer: B
Question 2
Refer to the exhibit.
Exhibit 1.
Exhibit 2.
Which devices can communicate with each other at Layer 2?
Devices 1 and 2 can communicate at Layer 2; Devices 3 and 4 can communicate at Layer 2.
Devices 2 and 3 can communicate at Layer 2.
Devices 1 and 4 can communicate at Layer 2.
Devices 1 and 4 can communicate at Layer 2; Devices 2 and 3 can communicate at Layer 2.
Correct answer: C
Question 3
Refer to the exhibit.
Exhibit 1.
Exhibit 2.
The routing configuration must support this behavior:
Server 1 and Server 2 communicate over Link 1 when Link 1 is up.
If Link 1 fails, Server 1 and Server 2 can continue to communicate over the path through Switch-3.
What must the network administrator change to meet these criteria?
On Switch 3, add a route to 192.168.2.0/24 through 192.168.1.9 and a route to 192.168.3.0/24 through 192.168.1.5.
On Switch-1, Switch-2, and Switch-3, change the next hop in each static route to specify an IP address that exists on that switch.
On Switch-1, raise the administrative distance for the second route to 192.168.3.0/24; on Switch-2, raise the administrative distance for the second route to 192.168.2.0/24
On Switch-1, add a route to 192.168.1.8/30 through 192.169.0.03; on Switch-2, add a route to 192.168.1.4/30 through 192.168.1.1; on Switch-3, add a route to 192.168.1.0/30 through 192.169.1.4.
On Switch-1, add a route to 192.168.1.8/30 through 192.168.1.2; on Switch-2, add a route to 192.168.1.4/30 through 192.168.1.1; on Switch-3, add a route to 192.168.1.0/30 through 192.168.1.4.