True Statements about Static Routes in Junos OS

BC

B. Static routes must have a next hop defined.

This statement is true. A static route is a manually configured route that specifies a fixed path to a destination network. Unlike dynamic routing protocols, which learn routes from other routers in the network, static routes are created by the network administrator and remain constant unless manually changed. In order for a static route to be functional, it must have a next hop defined, which specifies the next router or gateway to send the traffic to.

C. Static routes remain in the routing table until you remove them or until they become inactive.

This statement is also true. Static routes are manually configured routes and therefore remain in the routing table until they are removed or become inactive. Static routes are preferred over dynamic routes because they have a higher administrative distance, which means that they are considered more reliable and trustworthy than routes learned from other routers. However, if a better route becomes available, the static route may become inactive and be removed from the routing table.

A. Static routes are defined at the [edit routing-instances] hierarchy.

This statement is false. Static routes are defined at the [edit routing-options] hierarchy in the Junos OS, not the [edit routing-instances] hierarchy. The [edit routing-options] hierarchy is used to configure static routes and other routing options, such as routing policies and route filtering.

D. Static routes are learned by neighboring devices and added to their routing tables.

This statement is false. Static routes are manually configured and are not learned by neighboring devices. Unlike dynamic routing protocols, which exchange route information between routers, static routes are created and maintained by the network administrator. Neighboring devices may receive and use static routes that are advertised to them, but they do not learn static routes in the same way that they learn dynamic routes.