You save $69.98
Two eligible IPv4 routes describe exactly 172.16.50.0/24: static `[1/0] via 192.0.2.1` and OSPF `[110/2] via 192.0.2.2`. Both next hops are reachable. What is the normal route-source preference?
When routes to an identical prefix are eligible, IOS compares administrative distance across routing sources. Static AD 1 takes precedence over OSPF AD 110.
Metrics are meaningful within a routing protocol and are not generally compared across separate protocols before AD; larger metric is not preferred in OSPF.
Interface numbering does not override the installed route-selection decision for equal prefixes.
Equal prefix length alone does not create equal-cost paths between sources with different AD values.
At an enterprise data center, the campus network lead forwards a packet to 10.119.15.104. Four installed IPv4 routes are listed; all next hops are usable. Which entry wins the longest-prefix match?
10.119.15.0/24 has a prefix length /24 and is the longest matching installed route for 10.119.15.104; destination lookups prefer specificity before an unrelated metric.
10.119.0.0/16 has a prefix length /16 and matches 10.119.15.104 but /24 is more specific than /16.
0.0.0.0/0 has a prefix length /0 and matches 10.119.15.104 but /24 is more specific than /0.
10.119.15.128/25 has a prefix length /25 and does not contain 10.119.15.104, so this route cannot forward the destination.
At a stadium, a network operations engineer forwards a packet to 10.56.236.129. Four installed IPv4 routes are listed; all next hops are usable. Which entry wins the longest-prefix match?
10.56.0.0/16 has a prefix length /16 and is the longest matching installed route for 10.56.236.129; destination lookups prefer specificity before an unrelated metric.
0.0.0.0/0 has a prefix length /0 and matches 10.56.236.129 but /16 is more specific than /0.
10.56.237.0/24 has a prefix length /24 and does not contain 10.56.236.129, so this route cannot forward the destination.
10.56.237.0/25 has a prefix length /25 and does not contain 10.56.236.129, so this route cannot forward the destination.
R1 has a configured static route to 10.40.0.0/16 through 192.0.2.2 with administrative distance 255. A valid OSPF route to the same /16 appears with AD 110. Which route will normally be installed?
In Cisco administrative distance semantics, a value of 255 is not accepted as a usable installed route. The reachable OSPF path can be installed at AD 110.
Lower AD means higher preference for otherwise eligible sources; 255 is an exclusion value rather than maximum trust.
Identical prefixes do not imply equal-cost sharing when one source is intentionally ineligible.
A configured but ineligible static route does not suppress a valid OSPF route for the same destination.
A router has OSPF route 10.50.0.0/16 with AD 110 and a static route 10.50.20.0/24 with AD 200. A packet is destined for 10.50.20.8. Which forwarding decision is correct?
The /24 covers the host more specifically than the /16. AD compares routes that compete for the same prefix, not routes of different prefix lengths.
A lower AD for a less-specific route does not override the longest-prefix match for this packet.
A router may have different protocols contributing entries; forwarding uses the active matching table entries.
These entries have different prefix lengths, so equal-cost forwarding is not inferred.
At a logistics provider, an implementation partner forwards a packet to 10.151.230.83. Four installed IPv4 routes are listed; all next hops are usable. Which entry wins the longest-prefix match?
10.151.230.0/25 has a prefix length /25 and is the longest matching installed route for 10.151.230.83; destination lookups prefer specificity before an unrelated metric.
10.151.0.0/16 has a prefix length /16 and matches 10.151.230.83 but /25 is more specific than /16.
10.151.230.0/24 has a prefix length /24 and matches 10.151.230.83 but /25 is more specific than /24.
0.0.0.0/0 has a prefix length /0 and matches 10.151.230.83 but /25 is more specific than /0.
At a regional hospital, a network administrator forwards a packet to 10.13.185.108. Four installed IPv4 routes are listed; all next hops are usable. Which entry wins the longest-prefix match?
10.13.185.0/24 has a prefix length /24 and is the longest matching installed route for 10.13.185.108; destination lookups prefer specificity before an unrelated metric.
0.0.0.0/0 has a prefix length /0 and matches 10.13.185.108 but /24 is more specific than /0.
10.13.0.0/16 has a prefix length /16 and matches 10.13.185.108 but /24 is more specific than /16.
10.13.185.128/25 has a prefix length /25 and does not contain 10.13.185.108, so this route cannot forward the destination.
At a regional hospital, an implementation partner forwards a packet to 10.184.33.114. Four installed IPv4 routes are listed; all next hops are usable. Which entry wins the longest-prefix match?
10.184.0.0/16 has a prefix length /16 and is the longest matching installed route for 10.184.33.114; destination lookups prefer specificity before an unrelated metric.
0.0.0.0/0 has a prefix length /0 and matches 10.184.33.114 but /16 is more specific than /0.
10.184.34.0/24 has a prefix length /24 and does not contain 10.184.33.114, so this route cannot forward the destination.
10.184.33.128/25 has a prefix length /25 and does not contain 10.184.33.114, so this route cannot forward the destination.
R1 has RIP route 172.16.90.0/24 with `[120/1]` and an OSPF candidate for the same /24 with `[110/65]`. Both next hops are valid. What determines which source supplies the installed path?
Administrative distance compares preference between different route sources for the exact same prefix. Their protocol-specific metrics are not a common measurement scale.
RIP hop count and OSPF cost measure different things and should not be directly compared before AD.
IOS does not average incompatible routing metrics to manufacture a common-cost route across protocols.
The routing table can receive overlapping offers for the same prefix; one is chosen according to eligible route-source preference.
A router has two OSPF next hops to 10.66.0.0/16, both with total OSPF metric 30, and supports equal-cost multipath. What forwarding behavior is expected?
OSPF ECMP can install multiple equally preferred paths to the same prefix. Actual per-flow or per-packet selection depends on the forwarding implementation.
OSPF can install multiple equal-cost next hops when ECMP is supported and permitted.
Paths from the same OSPF source normally have the same AD; the equal cost is the relevant condition.
OSPF next-hop selection does not require VLAN identifiers to differ for equal-cost paths.
R1 is directly connected to 10.80.0.0/24 and also has an installed static route to 10.80.0.128/25 via 192.0.2.6. For a destination 10.80.0.200, which installed prefix is chosen?
A /25 covers addresses 10.80.0.128–255 and is longer than /24; the installed /25 is the forwarding match. This assumes the next hop is already resolved as stated.
Connected AD applies when choosing between routes to the same prefix, not when a longer matching route exists.
Overlapping routes with different prefix lengths are not equivalent paths for ECMP selection.
A legitimate specific route can override a broader connected route if installed and valid; this is a routing-table specificity decision.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (760 Questions, Last Updated on Nov 4, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.
