You save $69.98
200-301 Premium Bundle
- Premium File 760 Questions & Answers
- Last Update: Nov 4, 2026
- Training Course 271 Lectures
- Study Guide 1969 Pages
You save $69.98
A router shows `O 10.80.0.0/16 [110/65] via 192.0.2.9`. Which interpretation of the bracketed values is correct?
IOS routing-table syntax presents `[administrative distance/metric]`. AD compares eligible route sources for the same destination; metric ranks paths within a protocol.
Neither TTL nor number of traversed areas occupies the AD/metric position in this route entry.
These bracketed values are routing preference information, not Layer 2 VLAN or interface IDs.
The destination network has a separate prefix; the next-hop address appears after the via field.
A router is configured with address 192.0.2.1/30 on GigabitEthernet0/1. Besides the connected /30, which local host route will an IOS routing table normally show?
The connected route represents the /30 network; a separate L entry identifies the router’s exact /32 IPv4 address as a local destination.
S denotes a configured static route, not the automatically installed local interface host route.
The L route identifies the router’s specific interface IP as /32, not the whole connected prefix.
OSPF routes use O only if learned through OSPF; a directly assigned interface address does not become OSPF merely by existing.
At a biotech lab, the security and networking lead sees route entry R 172.24.177.0/24 [120/56] via 10.159.0.1. What do the bracketed values represent in this IOS route entry?
In IOS bracket notation [120/56], the first value 120 is administrative distance and the second 56 is the route metric. AD compares different route sources; metric compares paths within the route source.
Values in brackets after the route code are not an IPv4 mask and generic hop count. The network prefix specifies the mask separately.
This reverses the documented bracket order. Administrative distance is 120, not 56, in [120/56].
Syslog facility/severity metadata belongs to logging configuration, not route installation bracket values.
At a telecom operations room, the branch support lead interprets static route S 172.20.158.0/24 [1/0] via 10.52.0.1. What does the via field mean?
The via 10.52.0.1 field identifies the Layer 3 next-hop router for traffic matching 172.20.158.0/24. The outgoing interface and adjacency resolution determine actual Layer 2 forwarding.
The route destination is the listed prefix 172.20.158.0/24, not the value in the via field. A next-hop can serve many destinations.
10.52.0.1 is an IPv4 address, whereas MAC addresses identify Ethernet destinations; ARP can resolve the next hop to a MAC.
A route next-hop is not a DHCP server parameter. DHCP lease processing is independent from RIB next hops.
At a distribution center, a network administrator reviews the IPv4 routing table containing 172.30.41.0/24. Which statement correctly describes the prefix field?
An IPv4 prefix such as 172.30.41.0/24 defines the masked destination address space considered in route lookup. More specific matching routes may override it for subsets.
The routing-table prefix describes a set of possible destination IP addresses for forwarding. Source matches are an ACL concept and are not implied by this RIB entry.
A hostname is a device identity label, not an IPv4 network and mask in the RIB.
Ordinary unicast routing table lookups match destination IPv4 addresses, not source addresses.
At a clinic, the site engineer forwards a packet to 10.178.197.124. Four installed IPv4 routes are listed; all next hops are usable. Which entry wins the longest-prefix match?
10.178.197.0/25 has a prefix length /25 and is the longest matching installed route for 10.178.197.124; destination lookups prefer specificity before an unrelated metric.
10.178.197.0/24 has a prefix length /24 and matches 10.178.197.124 but /25 is more specific than /24.
0.0.0.0/0 has a prefix length /0 and matches 10.178.197.124 but /25 is more specific than /0.
10.178.0.0/16 has a prefix length /16 and matches 10.178.197.124 but /25 is more specific than /16.
R1 has installed routes `S 10.20.30.5/32 [200/0] via 192.0.2.2` and `O 10.20.30.0/24 [110/20] via 192.0.2.3`. A packet arrives for 10.20.30.5; both next hops are usable. Which path is selected?
A forwarding lookup selects the longest matching prefix first. Only after competing paths to the same prefix is administrative distance relevant; /32 wins over /24.
AD resolves preference between otherwise competing route sources to an identical prefix, not between a host route and a broader network route.
Equal-cost forwarding requires eligible equal-cost paths to the same destination prefix, not a /24 and /32 overlap.
A /32 route is the most specific possible IPv4 host route and correctly matches the one destination address.
At a biotech lab, the infrastructure lead forwards a packet to 10.46.161.124. Four installed IPv4 routes are listed; all next hops are usable. Which entry wins the longest-prefix match?
10.46.0.0/16 has a prefix length /16 and is the longest matching installed route for 10.46.161.124; destination lookups prefer specificity before an unrelated metric.
10.46.162.0/24 has a prefix length /24 and does not contain 10.46.161.124, so this route cannot forward the destination.
10.46.161.128/25 has a prefix length /25 and does not contain 10.46.161.124, so this route cannot forward the destination.
0.0.0.0/0 has a prefix length /0 and matches 10.46.161.124 but /16 is more specific than /0.
At a distribution center, the migration lead learns identical destination 192.0.2.192/26 from two eligible route sources with administrative distances 90 and 110. Which default IOS route-selection statement is correct?
For the identical prefix 192.0.2.192/26, administrative distance ranks competing route sources; lower AD 90 is preferred to 110. The RIB installs the best eligible source for that destination.
For identical eligible destination prefixes, administrative distance compares route-source preference in the opposite direction: AD 90 is preferred to AD 110, not vice versa.
There is no threshold based on the numerical AD difference that creates multipath. Different source-preference values select the lower-AD candidate for this exact prefix.
Administrative distance is a preference cost with lower values preferred, not a higher-is-better score.
At a nonprofit organization, the migration lead evaluates four OSPF candidate paths to the identical destination 198.51.100.64/26 and the same area. Which path is preferred under the listed route costs?
Within the same routing protocol and prefix 198.51.100.64/26, lower OSPF accumulated cost is preferred. Path B cost 10 is the lowest among the presented alternatives.
Within the same routing protocol and prefix 198.51.100.64/26, lower OSPF accumulated cost is preferred. Path A cost 35 exceeds path B cost 10.
Within the same routing protocol and prefix 198.51.100.64/26, lower OSPF accumulated cost is preferred. Path D cost 80 exceeds path B cost 10.
Within the same routing protocol and prefix 198.51.100.64/26, lower OSPF accumulated cost is preferred. Path C cost 20 exceeds path B cost 10.
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.
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.