Juniper Updated JN0-106 Exam Questions and Answers by harper-rose

Junos OS is built upon a highly stable and secure architecture that distinguishes it from many legacy network operating systems. Two of its most defining characteristics are software modularization and the separation of the control and forwarding planes .

Modularization means that Junos OS runs each major function—such as the routing protocol process (rpd), the management process (mgd), and the interface process (dcd)—as an independent software daemon in its own protected memory space. This ensures that if a single process crashes or needs to be restarted, it does not bring down the entire system or interrupt traffic forwarding.

Furthermore, the physical and logical separation of the Control Plane (Routing Engine) and the Forwarding Plane (Packet Forwarding Engine) is a cornerstone of Junos design. The Routing Engine handles complex intelligence, protocol calculations, and management, while the Packet Forwarding Engine performs high-speed packet switching in hardware. This ensures that a heavy management load or a complex routing recalculation won ' t cause " jitter " or packet loss for transit traffic. Conversely, Junos strictly prohibits unsigned third-party binaries to maintain system integrity, and it maintains a clear functional distinction between routing policies (path selection) and security policies (traffic permit/deny).

The Packet Forwarding Engine (PFE) represents the data plane of a Junos device, responsible for the high-speed processing and movement of packets through the system. Its primary role is to forward transit traffic—data that enters one interface and exits another—at wire speed using specialized hardware such as Application-Specific Integrated Circuits (ASICs). To accomplish this, the PFE utilizes a local copy of the Forwarding Information Base (FIB) provided by the Routing Engine, ensuring that forwarding decisions are made locally without requiring the main CPU ' s intervention for every packet.

In addition to pure forwarding, the PFE is the functional component that implements and executes firewall filters and policing. Because firewall filters must be applied to transit traffic at line rate to prevent bottlenecks, the PFE evaluates incoming and outgoing packets against configured filter terms in hardware. This ensures that security policies and traffic shaping are applied with minimal latency. It is critical to note that the PFE does not maintain the master routing table (RIB) or perform route selection; those " intelligent " control plane functions are strictly the domain of the Routing Engine. By offloading the repetitive tasks of packet inspection and hardware forwarding to the PFE, Junos OS maintains consistent performance even under heavy traffic loads or complex security configurations. Reference: Junos OS Fundamentals, Packet Forwarding Engine Architecture.

==========

In Junos OS, configuring the time-zone (such as America/LosAngeles) within the [edit system] hierarchy establishes the offset from Coordinated Universal Time (UTC) and governs how the device displays timestamps for logs and system events. However, simply setting the timezone does not adjust the underlying system hardware clock; it only dictates how that clock ' s data is interpreted and presented. To ensure the device reflects the correct local time, the administrator must either synchronize the system with an external reference or manually input the current date and time.

Configuring a Network Time Protocol (NTP) server is the preferred professional method, as it allows the device to automatically synchronize its clock with a reliable stratum source, ensuring long-term accuracy and consistency across the network. Alternatively, the set date operational mode command can be used to manually define the current year, month, day, hour, and minute. While a DNS server is necessary for resolving the hostnames of NTP servers, it does not provide time data itself. Furthermore, rebooting the device will not correct a fundamentally unset or drifting clock. Therefore, combining the correct timezone with either NTP synchronization or a manual date setting is the standard procedure for establishing temporal accuracy on a Junos platform. Reference: Operational Monitoring and Maintenance, System Time and NTP.

==========

Prefix lists in Junos OS are named collections of IP addresses or network prefixes defined under the [edit policy-options] hierarchy. One of their most powerful features is their versatility and reusability. Because they are defined as independent objects, a single prefix list can be referenced in multiple different routing policies across the device. This modularity ensures consistency; for instance, if a set of " internal " prefixes changes, an administrator only needs to update the list in one location for those changes to propagate to every policy that utilizes it.

Furthermore, prefix lists are designed to be used across different functional areas of the Junos architecture. They are equally valid for use in routing policies (to control the import or export of routes between protocols like BGP or OSPF) and in firewall filters (to match source or destination addresses for transit or management traffic). When used in a routing policy, the prefix list typically performs an exact match on the prefix length unless modified by a match type like orlonger. In a firewall filter, it acts as a high-speed lookup table for the Packet Forwarding Engine. This dual-purpose capability makes prefix lists a foundational tool for architects seeking to implement scalable, automated security and routing logic within a unified configuration framework.