Hard — 200-301 Practice Quiz

Question 1

A user reports slow file transfers between their workstation and a server. On the access switch port connecting the workstation, you run 'show interfaces' and notice the port is administratively up and line protocol is up, but the counters show an increasing number of late collisions and runts. The port is configured for 'speed 100' and 'duplex full'. What is the MOST likely cause of this problem?

Accepted Answer

The workstation NIC has auto-negotiated to half duplex, creating a duplex mismatch with the switch port set to full duplex

Answer

The cable exceeds the 100-meter maximum length for copper Ethernet, causing signal attenuation

Answer

The switch port and workstation are both set to full duplex, so no collisions can occur on the link

Answer

The server is using UDP instead of TCP, so lost frames are not being retransmitted

Question 2

A network administrator must configure an extended ACL on router R1's Gigabit interface. The policy requires that hosts on the 192.168.20.0/24 network be blocked from sending ping (echo) traffic to the server at 10.1.1.50, but those same hosts must still be allowed to reach the server's web service on TCP port 80. Which ordered set of ACL statements accomplishes this requirement?

Accepted Answer

deny icmp 192.168.20.0 0.0.0.255 host 10.1.1.50 echo
permit tcp 192.168.20.0 0.0.0.255 host 10.1.1.50 eq 80

Answer

permit tcp 192.168.20.0 0.0.0.255 host 10.1.1.50 eq 80
deny icmp 192.168.20.0 0.0.0.255 host 10.1.1.50 echo

Answer

deny ip 192.168.20.0 0.0.0.255 host 10.1.1.50
permit tcp 192.168.20.0 0.0.0.255 host 10.1.1.50 eq 80

Answer

permit ip 192.168.20.0 0.0.0.255 host 10.1.1.50
deny icmp 192.168.20.0 0.0.0.255 host 10.1.1.50 echo

Question 3

Two directly connected routers, R1 and R2, are configured for single-area OSPFv2 on their point-to-point serial link. They form an adjacency but never reach FULL state. R1 shows the neighbor stuck in EXSTART/EXCHANGE, and the console logs repeated messages about DBD packets. The IP addressing, area IDs, and hello/dead timers all match. What is the MOST likely cause?

Accepted Answer

The two interfaces have mismatched MTU values

Answer

The router IDs are identical on both routers

Answer

One interface is configured as an OSPF passive interface

Answer

The interfaces are in different OSPF network types

Question 4

On a multi-access Ethernet segment, R1 forms OSPF adjacencies with the DR and BDR but shows R2 stuck in the 2WAY/DROTHER state in the output of 'show ip ospf neighbor'. Both routers are in the correct area, timers match, and they can ping each other. What is the most likely explanation for the 2WAY state between R1 and R2?

Accepted Answer

R1 and R2 are both DROTHER routers, so they intentionally remain in the 2WAY state and do not become fully adjacent

Answer

There is an OSPF area ID mismatch preventing the adjacency from advancing

Answer

The OSPF hello and dead timers between R1 and R2 do not match

Answer

R1 and R2 have duplicate OSPF router IDs, causing the neighbor process to halt

Question 5

Two routers, R1 and R2, are connected over a Frame Relay WAN link. OSPF is enabled on the multipoint interfaces of both routers, and Layer 3 connectivity has been verified with successful pings across the link. However, the OSPF adjacency never forms and no neighbor is listed with 'show ip ospf neighbor'. The interfaces default to the non-broadcast network type. What is the most likely reason the adjacency fails to establish?

Accepted Answer

The non-broadcast network type does not send multicast Hello packets, so neighbors must be defined manually with the 'neighbor' command

Answer

Non-broadcast interfaces elect a DR/BDR, which prevents multipoint adjacencies from forming

Answer

OSPF cannot operate over Frame Relay unless the interfaces are changed to point-to-point network type

Answer

The routers have mismatched process IDs, which stops the Hello exchange