Juniper Updated JN0-106 Exam Questions and Answers by essa

In the Junos OS architecture, the configuration environment is strictly bifurcated to ensure system stability and integrity. The candidate configuration is a specific database that serves as a staging area, storing all proposed changes made by an administrator during a configuration session before they are finalized. Unlike other network operating systems where changes might take effect immediately upon entry, Junos utilizes this " sandbox " approach where modifications reside only in the candidate database until a commit command is explicitly executed.

Once the commit process is initiated, the Junos OS kernel validates the candidate configuration for syntax errors and logical consistency. If the validation check is successful, the candidate configuration is promoted and becomes the active configuration—the operational state currently running on the device hardware. This separation allows multiple administrators to work on complex changes without impacting live transit traffic or device stability prematurely. If a mistake is identified during the editing process, the candidate configuration can be easily discarded or compared against the active state to identify discrepancies. This workflow is a cornerstone of Junos OS, facilitating a " check-before-apply " methodology that is essential for carrier-grade reliability and minimizing the risk of accidental outages during critical maintenance windows. Reference: Junos OS Fundamentals, Configuration Databases, Candidate vs. Active.

==========

The relationship between the routing table (Routing Information Base or RIB) and the forwarding table (Forwarding Information Base or FIB) is the cornerstone of the Junos OS architectural separation between the control and data planes. The routing table resides in the control plane on the Routing Engine (RE). Its primary role is to aggregate all reachability information from every configured protocol and select the best route for each destination prefix based on criteria like preference and metrics.

Once the Routing Engine has identified the single " active " best path for a destination, it distills this complex routing data into a simplified, streamlined version called the forwarding table . The forwarding table contains only the essential information needed to move a packet: the destination prefix, the egress interface, and the Layer 2 next-hop MAC address. The RE then " pushes " this forwarding table to the Packet Forwarding Engine (PFE) in the data plane. By having the PFE use a table built from the routing table , Junos ensures that transit traffic can be processed at wire speed without the overhead of complex routing logic. This one-way flow—from the comprehensive RIB on the RE to the optimized FIB on the PFE—allows the device to maintain high performance even while routing protocols are recalculating or the management plane is under heavy load.

In Junos OS, a routing policy is a powerful tool used to manage the flow of routing information between the Routing Information Base (RIB) and routing protocols. Unlike forwarding decisions, which are handled by the Packet Forwarding Engine, routing policies function within the control plane on the Routing Engine. Their primary purpose is to define specific criteria for importing routes into the routing table from neighbors or exporting routes from the routing table to neighbors.

Routing policies consist of terms containing from (match) and then (action) statements. They allow administrators to filter prefixes (e.g., denying specific BGP routes), modify route attributes (e.g., changing OSPF metrics or BGP communities), and manipulate path selection behavior. For example, an export policy might be used to ensure that only specific internal subnets are advertised to an ISP via BGP, preventing the accidental leakage of private infrastructure addresses. By default, Junos applies " default policies " for each protocol (such as OSPF accepting all OSPF routes), but custom policies allow for granular control over how the device interacts with the rest of the network. This ensures that the routing table contains only the desired paths for optimal traffic engineering.

Creating a new user account in Junos OS involves several specific steps within the [edit system login] configuration hierarchy. To establish a functional and secure user account, an administrator must first define the username and assign that user to a login class. Login classes are essential because they define the permissions and access levels for the user, such as super-user, read-only, or operator. Without a login class, a user would have no permissions to perform tasks within the CLI.

The second mandatory task is to configure an authentication method for the user, most commonly a password. This is typically done using the authentication plain-text-password command, which prompts the administrator to enter and confirm the secret string that the system then hashes and stores. While Junos also supports public-key authentication for SSH, a local password remains the standard for basic access control. It is important to note that SSH access is generally controlled at the system level under [edit system services] and does not need to be enabled on a per-user basis individually. Furthermore, allowing a user to bypass authentication is contrary to the Junos security model and is not a standard task in user account creation. Reference: User Interfaces, User Management, Login Classes.