Cisco 200-301 Exam Dumps, Practice Test Questions

OSPF entries use O-related codes, and local interface host routes use L; neither is represented by S*.

Connected prefixes use C and local host addresses use L, not a static candidate-default code.

RIP routes use R and the asterisk does not imply a dynamic protocol failover policy.

The ordinary route table includes `C` connected routes when installed; `static` is a different source filter and would not make a shut port operational.

A functioning addressed interface automatically installs its connected prefix; a separate static route is neither required nor a substitute for enabling the interface.

OSPF is a dynamic route-exchange protocol. Locally connected networks can be installed without any OSPF adjacency.

The time field is not a per-packet latency measurement. Forwarding delay depends on queuing, link conditions, and traffic paths, not the route age.

DHCP lease state is not encoded as this route-table age field, and the route was learned with an OSPF source code.

The first bracket number is administrative distance 110; `00:00:42` is in a later field and represents elapsed update time.

Metrics from different routing protocols are not generally comparable; the route source with better administrative distance wins for the identical prefix.

Two candidates with different administrative distances do not automatically become equal-cost multipath entries in the same routing table.

RIP is not part of this scenario and is never an automatic conversion mechanism for OSPF/EIGRP entries.

OSPF compares path type before cost here; the lower interarea cost does not override the intra-area path-type preference inside the same process.

Equal-cost multipath does not combine different preferred OSPF route types merely because two candidates exist.

A router may know both intra-area and interarea candidates for a prefix, but path-type selection chooses the preferred one.

RIP supports reachable hop counts only up to 15. At 16 the route is treated as unreachable rather than as the longest permitted path.

A RIP hop metric does not convert a learned route into a static route or become its administrative distance.

An OSPF external advertisement is unrelated to this RIPv2 route metric; route types are not automatically converted.

A /24 is broader and includes many destinations; a /32 matches precisely one IPv4 address.

A default route is the broadest possible prefix, opposite the specified single-host exception.

A /16 aggregates a much larger block and cannot represent only 203.0.113.9.

A /32 matches one IP address; the destination 0.0.0.0/0 instead matches any destination as fallback.

The all-zero /0 prefix does not identify a normal directly connected network.

S* denotes a static candidate default route, not an OSPF inter-area advertisement.

The router derived 10.20.30.0/24 from the active interface, so this is connected-source state.

No routing-protocol advertisement is needed to install a connected prefix from its own interface.

IOS may also install a separate local /32, but the situation calls for the complete /24 subnet route.

A connected route is attached to a local interface rather than explicitly naming a separate adjacent router.

The local host route identifies the router’s address, not a neighboring forwarding router.

An exit-only route does not explicitly identify an adjacent forwarding router by IP.

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.