Cisco 200-301 Exam Dumps, Practice Test Questions

The first bracket value is administrative distance, indicating route-source preference, not the second-position OSPF cost.

The prefix length is the /16 in the destination network, not the numeric metric inside [110/30].

The next-hop address appears in the via field of the route entry; it is a forwarding IP address, not an OSPF cost number.

Intra-area OSPF routes use `O` without the E2 suffix; that code does not designate external type 2 origination.

Connected routes are denoted `C` and normally use administrative distance zero; `O E2` is not a connected prefix.

A static candidate default appears with an `S*` prefix, not `O E2`, and the displayed network is not the default prefix.

The IA modifier explicitly indicates an inter-area route rather than an intra-area O-only route.

The bracket is [administrative distance/metric], not the learned route classification.

The via IPv4 address names the next hop; the prefix’s O IA code identifies the source/type.

Internal EIGRP routes ordinarily appear under `D` with default AD 90; `D EX` and AD 170 signify the external category.

OSPF external type 2 routes carry `O E2` rather than `D EX` and use separate OSPF route semantics.

RIP is coded `R` and has a usable hop-count range below 16; 28160 is not a plausible RIP hop count.

C marks the attached /24 network; L marks the router’s own exact assigned /32 interface address.

O identifies OSPF-learned routing information, not the local host prefix created by interface addressing.

S denotes a configured static route, not IOS’s automatically generated local /32 host route.

Type 2 external routes normally retain the external cost separately; this is explicitly an E1 route.

Administrative distance affects route-source selection and is not summed into OSPF path metrics.

O E1 denotes an OSPF external type 1 route, not the local C connected-route code.

Zero-distance connected routes have the most preferred source trust; a value of 255 is not a superior priority.

Different AD values do not create equal-cost paths; ECMP eligibility requires valid routes meeting the routing process's multipath criteria.

Numerically lower AD is preferred for the same prefix; 255 is not more preferred than OSPF's 110.

Destination address bits identify the network; the stated 20 versus 60 metric values rank eligible same-type paths.

Both are OSPF paths with the same AD, so OSPF cost is what differs for this comparison.

Interface labels do not substitute for the protocol’s computed total path cost.

Administrative distance chooses a route source when installing the same prefix; packet forwarding chooses the most specific installed match across different lengths.

Metric comparison among same-protocol candidates is not the first rule for choosing between different installed prefixes that match the destination.

Route age is not the longest-prefix forwarding selection rule and cannot make a shorter prefix win over a valid longer match.

The router already owns the SVI subnet; IOS installs its connected prefix without a manually added ip route.

The local /24 network does not require OSPF neighbor advertisements to appear as connected.

A default is a fallback and does not replace the attached subnet’s connected route.

OSPF process configuration lists intended protocol settings but is not proof that the default route is installed in the active RIB.

An interface description helps identify a circuit but does not prove an IP default route is usable in the RIB.

Resolver settings affect name lookup but not the installed default route used to forward unmatched destination IP packets.