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.