Free JN0-106 Practice Test Questions and Answers (2026)

The operational command clear log ospf-trace truncates the file—erasing all existing contents—then immediately reopens it so that OSPF trace messages keep being written; only the stored data is removed.

A. Command does not remove the file itself; it only empties it.

B. Runtime command never changes configuration traceoptions statements.

C. Logging continues after the file is cleared; it is not halted.

1. Juniper Networks, Junos OS CLI Reference 23.4R1, “clear log” command, Description ¶1-2.

2. Junos OS System Log Messages Guide 22.3, “Clearing System Log Files,” p.19.

The Junos CLI help syslog command provides detailed textual explanations for individual system log (syslog) error messages, allowing an administrator to understand the cause and possible remediation of each message. No other help sub-command supplies the MOTD, hyperlinks, or URL-only output; therefore, option D is the only correct choice.

A. help reference shows the syntax and brief description of a command, not just a URL.

B. The message of the day is displayed automatically at login, not obtained with any help command.

C. Junos help commands display text; they do not output interactive hyperlinks for remediation actions.

1. Junos OS CLI User Guide, “Requesting Explanations of System Log Messages,” Section 5.5, p. 120–121 (Juniper Networks, 2023-06-30).

2. Junos OS Documentation, KB21103 “Using ‘help syslog’ to interpret messages,” ¶2–3 (Juniper, 2022).

The Routing Engine (RE) is Junos’s management and control component. It runs routing protocols (RPD, OSPF, BGP, etc.) to build the Routing Information Base and handles all device management tasks, including storing and modifying the configuration database. Packet forwarding and firewall-filter processing occur in the Packet Forwarding Engine, not in the RE.

B. Firewall filter evaluation for transit packets is executed on the Packet Forwarding Engine, not the Routing Engine.

D. Transit packet forwarding is off-loaded to the Packet Forwarding Engine; the Routing Engine does not forward data traffic.

1. Juniper Networks, Junos OS Architecture Guide, “Routing Engine Processes”, Section 1.3, p. 12–14.

2. Juniper Networks, Day One: Junos Basics, Chapter 2 “Control and Forwarding Planes”, p. 8–10.

3. Juniper Networks, MX Series Architecture White Paper, “Packet Forwarding Engine Functions”, p. 5.

The Routing Engine (RE) is the control-plane component of a Juniper device. It handles all management and protocol processing, maintains the routing and forwarding tables, and exchanges route information with the Packet Forwarding Engine (PFE); it does not forward transit or CoS-handled traffic itself.

B. CoS classification/queuing is performed in the PFE, not the RE.

C. Transit packet forwarding occurs in the PFE; the RE is not in the data path.

1. Juniper Networks, “Junos Platform Layered Architecture,” TechLibrary article, Table 1 (Routing Engine Functions).

2. Juniper Networks, “Junos OS Architecture Fundamentals,” Courseware AJER v21, Module 2, p. 2-6.

Entering “?” triggers context-sensitive help. The CLI prints every command or keyword valid in the current hierarchy level and, beside each, a short descriptive phrase—effectively a summary of commands and options.

B. No separate “tips” list is provided; only command completions appear.

C. String-search help is invoked with “help apropos”, not with “?”.

1. Juniper Networks, “Using CLI Help”, Junos OS CLI User Guide, § Context-Sensitive Help (?), paras 1-2 (2023-07).

2. Juniper Networks, Junos OS CLI Reference, “help apropos” vs. “?” Comparison Table, p. 14 (2022-11).

TCP establishes a session with a three-way SYN, SYN-ACK, ACK handshake and assigns sequence numbers to bytes, enabling reliable, in-order delivery with retransmission and flow control. It does not guarantee latency and never uses Ethernet broadcast.

A. TCP offers reliability, not deterministic latency; delays vary with congestion.

B. TCP segments are unicast IP packets, never Ethernet broadcasts by default.

1. RFC 793 – Transmission Control Protocol, §3.3 (Connection Establishment), §2.1 (Ordered Delivery).

2. Juniper TechLibrary – “Understanding TCP in Junos OS”, ¶Overview (2022-10-12).

The static route to 10.0.0.0/24 uses a qualified-next-hop (10.12.0.2 via ge-0/0/1, preference 5) and a secondary next-hop (10.23.0.3). When ge-0/0/1 fails, the qualified next-hop becomes inactive and the router installs the parent route whose next-hop is 10.23.0.3.

B. 10.12.0.2 is tied to the failed interface and is removed from the RIB.

C. 10.12.0.1 is not referenced in the static route statement.

D. 10.25.11.1 is not associated with the 10.0.0.0/24 route in the exhibit.

1. Juniper Networks, “Junos OS Routing Protocols Configuration Guide”, 21.4R1, sec. ‘Configuring a Qualified Next Hop for a Static Route’, Example 1, pp. 180-182.

2. Juniper Networks Day One Book “Exploring IPv4 Static Routing”, Example ‘Primary Qualified Next Hop with Backup Next Hop’.

Junos first performs longest-prefix match to find all candidate routes. If multiple routes remain, the one with the lowest route preference (administrative distance) is chosen; lower numeric values mean higher priority.

A. Higher preference values are less preferred; lower numbers win.

D. Route preference affects route selection only; it does not change forwarding table size.

1. Junos OS Fundamentals Guide 23.4R1, “Route Preference (Administrative Distance),” para. 1-2.

2. Junos OS Routing Protocols Concepts Guide 23.4R1, §Route Selection Process, steps 2-3.

User PCs, R1, and R2 share subnet 10.1.99.0/24. Each router is configured with a default route that points at the other router. When a PC sends traffic to 10.1.99.1 (R1’s address), R2 believes R1 is the next hop and forwards the frame to R1; R1’s default route points back to R2. Because 10.1.99.1 belongs to the local subnet, neither router will ARP for it and both will repeatedly forward to the other, creating a Layer-3 routing loop.

B – All users are affected; the problem is not limited to User A.

C – R2 does not drop the traffic; it keeps forwarding it to R1.

D – R1 forwards (then receives again) the traffic; it does not silently discard all packets.

1. Juniper Networks TechLibrary, “Understanding and Preventing Static-Route Loops”, Section ‘Mutual Default Routes’, Example 2 (2022-12).

2. University of Colorado (Coursera) “Computer Communications”, Week 4 notes, p. 5-6, “Loops created by reciprocal static routes”.

A Junos local user account must belong to a login class, which defines its permissions, and it must have an authentication method such as a local password (or SSH key). Creating the account with set system login user class and set system login user authentication plain-text-password (or encrypted-password) satisfies these mandatory requirements. SSH access is controlled globally under system services ssh, not per user, and bypass-authentication is optional and rarely used.

B. SSH is enabled globally under system services; no per-user SSH switch exists.

D. bypass-authentication disables all authentication; not required for normal account creation.

1. Juniper Networks, “Junos OS System Basics Configuration Guide”, Section “Configuring Regular Users to Access the System”, release 22.3R1 (steps 2–3).

2. Juniper Networks, “Junos OS Security Configuration Guide”, Section “Configuring User Authentication”, para. 1–2 (describes mandatory class and password).

IPv6 hosts use the Neighbor Discovery Protocol (NDP) to map a destination’s IPv6 address to the corresponding Layer-2 MAC address on the local link, replacing ARP which is specific to IPv4.

A. DHCP provides configuration parameters, not link-layer address resolution.

B. ARP operates only for IPv4, not IPv6.

D. DNS resolves hostnames to IP addresses, not IP-to-MAC mapping.

1. RFC 4861: Neighbor Discovery for IP version 6 (IPv6), § 2.2 “Address Resolution” (2007).

2. Juniper Networks TechLibrary, “Understanding IPv6 Neighbor Discovery”, Junos OS Protocols Library, para 1 (2023-04).

3. MIT OCW 6.829, “IPv6 ND vs. ARP” lecture notes, slide 5 (2021).

To keep management traffic separate from inet.0, assign an IP address to the dedicated management port (fxp0.0 or em0.0) and activate the management routing instance with set system management-instance. That places fxp0 traffic in the mgmt.junos routing table, isolating it from the default forwarding table.

A. ge-0/0/0 belongs to the default routing instance; ethernet-switching does not isolate management.

B. lo0.0 is always in inet.0 and cannot provide physical OOB separation.

C. me0 uses the main forwarding plane; virtual-router affects only that interface’s routes, not full OOB isolation.

1. Juniper Networks TechLibrary, “Using a Dedicated Management Interface”, Junos OS Administration Guide, Section: Enabling the Management Routing Instance (set system management-instance), 2022-12.

2. Day One: Deploying Out-of-Band Management, Chapter 2 “fxp0 and mgmt-instance”, pp. 13-14, Juniper Networks, 2021.

Junos installs a static route only when the next-hop address can be resolved to an active, directly-connected route. Because 10.10.1.1 is not reachable through any interface or existing route, the 10.10.10.0/24 static route remains hidden and never becomes active.

B. Junos needs only a resolvable next-hop IP; specifying the outgoing interface is optional, not mandatory.

C. Static routes inherit the default preference (5); no explicit preference is required for installation.

D. retain merely prevents an inactive route from being removed; it does not make an unresolved route active.

1. Juniper Networks, Junos OS Routing Concepts, “Route Resolution for Static Routes,” §2.2, pages 41-43 (21.3R1).

2. Juniper Networks TechLibrary, Junos OS Routing Configuration Guide, “Static Route Overview,” last para before Example 1 (21.3R1).

Transit traffic is any packet that merely traverses the device without being destined for—or generated by—the local Routing Engine. Such traffic is switched in hardware by the PFE and therefore bypasses control-plane processing. Consequently, it needs no Routing Engine intervention (statement C) and is physically forwarded by the PFE to the next hop (statement D).

A. Routing-protocol packets terminate on the local device; they are handled by the control plane, so they are exception, not transit, traffic.

B. Packets destined for the Routing Engine are by definition not in transit; they are exception or local traffic.

1. Juniper Networks, “Transit Traffic Versus Exception Traffic,” Junos Platform Fundamentals Guide, Chapter 5, p. 104.

2. Juniper Networks, “Understanding Packet Forwarding,” Junos OS Documentation, section “Control-Plane and Data-Plane Separation,” para. 3-4.

In Junos routing policy evaluation, terms are processed sequentially. When a route matches a term whose action is accept, evaluation of the current policy stops immediately; no further terms in that policy are examined, and the route is treated as accepted before the system proceeds to any subsequent policy chains.

A. Route is not rejected; it is accepted.

B. Evaluation halts; second term is never reached.

C. Next policy chain is consulted only after policy completes; accept already finalizes decision.

1. Juniper Networks, Junos OS Routing Policy Configuration Guide 22.3R1, “How Routing Policies Are Evaluated,” p. 32–33.

2. Juniper Networks TechLibrary, “Understanding the Policy Framework,” Section “Term Processing Rules,” para. 2.