Configuration Parameter for Static Route Next-Hop Resolution

B

The correct answer is B. resolve.

In Junos, static routes are typically used to specify a route to a destination network that is not directly connected to the device. By default, when a packet is forwarded to a destination network via a static route, the device performs next-hop resolution to determine the next-hop IP address to forward the packet to.

Next-hop resolution involves looking up the next-hop IP address in the routing table and determining the interface through which the packet should be forwarded. If the next-hop IP address is directly connected to the device, the device can use the connected interface to forward the packet. Otherwise, the device needs to determine the next-hop interface and ARP for the next-hop IP address.

The configuration parameter that alters the default next-hop resolution behavior of a static route is the 'resolve' parameter. This parameter is used to specify whether or not the device should perform next-hop resolution for a particular static route.

If the 'resolve' parameter is configured as 'no-resolve', the device will not perform next-hop resolution for the static route. Instead, the device will forward packets to the specified next-hop IP address without looking up the next-hop interface or ARP. This can be useful in scenarios where the next-hop IP address is not directly connected to the device and the necessary next-hop information is already known.

The other configuration parameters listed in the question are not related to next-hop resolution for static routes:

• The 'no-readvertise' parameter is used in BGP route advertisements to prevent a device from advertising a received route to other peers.
• The 'preference' parameter is used to set the administrative distance for a static route. Administrative distance is a measure of the trustworthiness of a routing protocol or static route.
• The 'passive' parameter is used in OSPF and RIP to configure a device interface as a passive interface, which means that the interface will not participate in OSPF or RIP updates.