Juniper JN0-106 Practice Test Questions Answers

Junos OS firewall filters operate on a sequential, " first-match " logic, but their behavior is significantly influenced by the use of terminating versus non-terminating actions. In this exhibit, a packet with a source address of 10.0.0.0/8 is evaluated against the filter named test.

Evaluation begins with term 1 . The packet matches the source-address criteria, triggering the actions defined in the then statement. The first action is log, which sends the packet header information to the firewall task buffer for logging. The second action is next term . This is a critical non-terminating action ; it instructs the Packet Forwarding Engine (PFE) to continue the evaluation process using the subsequent term in the filter rather than stopping after the match.

Evaluation then moves to term 2 . Because term 2 contains no from match conditions, it acts as a " catch-all " for any traffic that reaches it. The action in this term is reject . This is a terminating action that discards the packet and sends an ICMP " destination unreachable " message back to the source. Therefore, the packet is first recorded by the logging process and is subsequently dropped by the rejection mechanism. If next term had not been present in term 1 , the packet would have been implicitly accepted (as any matched term without a terminating action like discard, reject, or accept defaults to an implicit accept in that specific term). However, the explicit instruction to move forward ensures the packet hits the reject statement.

The Junos OS operates using a candidate configuration model, where changes are made in a temporary buffer before being applied to the running system. To ensure accuracy and prevent unintended network disruptions, it is a critical best practice to review the differences between the candidate buffer and the currently active configuration. The command show | compare executed from the [edit] hierarchy level is the primary tool for this task.

When this command is issued, the CLI performs a line-by-line comparison. The output uses a " diff " format: lines prefixed with a plus sign (+) represent new statements added to the candidate configuration, while lines prefixed with a minus sign (-) indicate statements that have been removed. This visualization allows the architect to verify exactly what will change upon execution of the commit command. Unlike operational mode commands that only show the final state, show | compare highlights the delta, making it indispensable for auditing complex policy changes or interface reconfigurations. This step acts as a final manual validation gate, reducing the risk of syntax errors or logical misconfigurations entering the production environment. Using this command is a fundamental skill for passing the JNCIA-Junos exam and for professional day-to-day operations.

User access control in Junos OS is managed through the application of permission flags within login classes. When an architect needs to define a role that allows for robust monitoring and troubleshooting without granting authority to alter the device ' s operational state, the view permission flag is the appropriate selection. This flag grants the user the ability to execute the majority of show commands in operational mode, which includes viewing the routing table, inspecting interface statistics, and checking hardware status.

The view permission is specifically designed for " read-only " access. It ensures that the user can observe all necessary telemetry data to validate network health—satisfying the requirement to check routing and interface stats—while strictly prohibiting access to configuration mode or any set commands. This contrasts with the configure flag, which allows modification of the candidate configuration, or the network flag, which provides specific permissions related to network-level operational tasks. By assigning a user to a class restricted with the view flag, an administrator maintains a secure environment where support personnel can diagnose issues without the risk of accidental or unauthorized configuration changes. This principle of least privilege is a cornerstone of Junos security management. Reference: User Interfaces, User Management and Access Control.

==========

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.

In large-scale Junos deployments, efficiency and flexibility are achieved through the use of configuration groups . When faced with a requirement like moving all 1-gigabit interfaces to jumbo frames—with the caveat that the exact MTU value (e.g., 4000 bytes) might change after testing—manually editing every interface is both tedious and prone to error.

By creating a configuration group under the [edit groups] hierarchy, you can define the MTU parameter once. You then use the apply-groups statement at the [edit interfaces] level or on specific interface ranges. This creates a " template " effect. The flexibility comes into play during the testing phase: if results indicate that a 9000-byte MTU is preferable to 4000 bytes, the architect only needs to modify the value in the group definition. The Junos OS inheritance mechanism automatically propagates this update to every interface associated with that group.

Applying MTU at the family level (Option B) is less efficient and doesn ' t handle the physical Layer 2 MTU requirements of jumbo frames as effectively. Path-MTU discovery (Option D) is a protocol-level function for avoiding fragmentation but does not configure the local interface ' s hardware capability to accept larger frames. Thus, groups represent the best practice for centralized, scalable management.