Static routes are manually configured by an administrator and remain in the routing table until manually changed or removed, unless a route validation mechanism causes the route to be withdrawn.

To recover the root password on a Junos router without losing the configuration, you should (A) enter and commit the new root password once you have gained access to the system, (D) hit the space bar to interrupt the boot process and enter recovery mode when prompted during the boot process, and (E) use a console connection to reboot the device and access the bootloader prompt. These steps allow you to reset the root password while preserving the existing configuration.

Transit traffic that traverses the forwarding plane of a Layer 3 router includes both unicast and multicast traffic types. Unicast traffic is directed from a single source to a single destination, while multicast traffic is sent from one source to multiple destinations that are part of a multicast group.
These types of traffic are efficiently routed through the network by leveraging the router's forwarding plane capabilities. Exception traffic, which requires special handling by the control plane, and broadcast traffic, which is typically limited to a single broadcast domain and not usually forwarded by Layer 3 routers, are not considered standard types of transit traffic for the forwarding plane of a router.

The Routing Engine (RE) in a Junos device serves as the centralized intelligence and management hub, primarily responsible for the control and management planes of the system. In this capacity, the RE is tasked with processing routing updates, such as OSPF Link State Advertisements (LSAs) or BGP Update messages. These updates are vital for the RE to maintain the Routing Information Base (RIB), calculate the shortest paths, and subsequently populate the Forwarding Information Base (FIB) which is then pushed to the Packet Forwarding Engine (PFE).
Furthermore, the Routing Engine handles all local management traffic. This category encompasses administrative access through the Command Line Interface (CLI) via SSH or Telnet, SNMP queries from network management systems, and system logging processes.
Because the RE runs the Junos OS kernel, it must directly interpret and respond to these management-level requests to ensure the device remains configurable and observable.
Conversely, transit traffic--the data passing through the device from one ingress port to an egress port--is offloaded to the PFE to be handled at wire speed. While the PFE manages the heavy lifting of data forwarding and Class of Service (CoS) application, the RE remains focused on high- level protocol maintenance and system administration, ensuring that control plane stability is maintained even under heavy traffic loads.

In the Junos OS, the Command Line Interface (CLI) uses distinct prompt symbols to provide the administrator with immediate contextual awareness of their current operating environment. When the prompt ends with a hash symbol (#) , it indicates that the user is in configuration mode .
This mode is the " engine room " of the device, where you modify the candidate configuration. Here, you can add, delete, or modify statements across the various hierarchies like [edit system], [edit interfaces] , or [edit protocols]. It is important to remember that changes made while the # prompt is visible are not active until a commit command is successfully executed.
Contrast this with the operational mode , which is indicated by a greater-than symbol ( > ) . Operational mode is used for monitoring, troubleshooting, and viewing the system status (e.g., show commands). Moving between these modes is a fundamental part of the Junos workflow: you enter configuration mode by typing configure and return to operational mode by typing exit or quit. If you see a percent sign (%), you ' ve wandered into the FreeBSD shell mode , which is a lower-level Unix environment typically reserved for advanced system maintenance. Recognizing that # means you have the power to change the system ' s " brain
" is a key safety check for any network architect.
Reference: User Interfaces, CLI Modes and Navigation.