By default, which MPLS operation is performed by the penultimate router in an LSP on the transport label?
Answer(s): D
In a Multiprotocol Label Switching (MPLS) environment, label operations are categorized into three primary actions: Push (adding a label), Swap (replacing a label), and Pop (removing a label). The specific behavior described in the question refers to a mechanism called Penultimate Hop Popping (PHP).According to Juniper Networks technical documentation, the goal of PHP is to improve forwarding efficiency at the egress point of a Label-Switched Path (LSP). The Egress Label Edge Router (LER), which is the final destination for the LSP, would normally have to perform two lookups if it received a labeled packet: first, it would look up the label in its MPLS table to see it is the destination, and second, it would look up the underlying IP payload in its IP routing table (inet.0) to forward the packet.To alleviate this burden, the Egress LER signals a special label value called Implicit Null (Label 3) to its upstream neighbor (the penultimate router) during the signaling process (RSVP or LDP). When the penultimate router receives a packet destined for that egress LER, it sees the instruction to pop the transport label. Consequently, the penultimate router performs a Pop operation, stripping away the outer MPLS label and sending the raw IP packet (or the remaining inner service label) to the Egress LER.This allows the Egress LER to perform only a single lookup. If the transport label was the only label, the Egress LER simply performs a standard IP lookup. If there is a VPN label remaining, it performs a single MPLS lookup for the VRF. This "default" behavior in Junos OS optimizes the performance of the egress router by offloading the final label removal to the penultimate hop. Note that if Ultimate HopPopping (UHP) were configured (via the explicit-null command), the penultimate router would perform a Swap to Label 0 instead of a Pop.
You are designing a high availability solution for a Juniper router with dual Routing Engines (RE). You want to ensure that the routing protocol state is preserved during an RE switchover. You have already enabled graceful Routing Engine switchover (GRES) and you want to avoid relying on helper routers to maintain the routing protocol state. In this scenario, which feature would accomplish this behavior?
When designing High Availability (HA) for Juniper Service Provider routers, understanding the interaction between the control plane and data plane is vital. The user has already enabled Graceful Routing Engine Switchover (GRES), which synchronizes the interface and kernel state between the primary and backup Routing Engines (REs). However, GRES by itself does not preserve the routing protocol state (like OSPF adjacencies or BGP sessions).To achieve the preservation of the routing protocol state without relying on external "helper" routers, you must implement Non-Stop Active Routing (NSR). According to Juniper Networks documentation, NSR uses the infrastructure provided by GRES to also synchronize the routing protocol process (rpd) information. Under NSR, the backup RE maintains a "hot" standby state of all routing protocols. If the primary RE fails, the backup RE takes over immediately. Because it already possesses the full routing table and peer session states, the peering neighbors are unaware that a switchover occurred. No protocol adjacency resets occur, and traffic continues to flow uninterrupted.It is crucial to differentiate NSR from Graceful Restart (Option C). While Graceful Restart also aims to maintain traffic flow during a switchover, it does require help from neighboring routers (known as "helper mode"). If the neighbors do not support or are not configured for Graceful Restart, the sessions will drop. Since the user explicitly stated they want to "avoid relying on helper routers," Graceful Restart is not the correct solution.Non-stop Active Bridging (Option A) provides a similar "hitless" failover but specifically for Layer 2 environments (STP/VLANs) rather than Layer 3 routing protocols. BFD (Option B) is a failure detection protocol used to speed up convergence but does not preserve state during an RE failover; in fact, without NSR, BFD would likely trigger a faster teardown of the session during a switchover. Therefore, NSR is the only feature that meets the requirement for independent control-plane preservation.
Which two statements regarding GRE and IP-IP tunnels are correct? (Choose two.)
Answer(s): A,D
In Juniper Networks Junos OS, Generic Routing Encapsulation (GRE) and IP-in-IP (IP-IP) are common tunneling mechanisms used to transport packets across a network by encapsulating them within another protocol. Understanding the header structure and the limitations of these protocols is essential for proper MTU (Maximum Transmission Unit) management and security design.Overhead (Option A):Both GRE and IP-IP tunnels operate by adding an additional IP header to the original packet. An IP-IP tunnel (Protocol 4) adds a 20-byte IPv4 header. A GRE tunnel (Protocol 47) adds the same 20-byte delivery IP header plus a minimum 4-byte GRE header (totaling 24 bytes, which can increase if keys or sequencing are used). Because these headers are added to the payload, the total size of the packet increases. This "overhead" means that if the original packet was already at the MTU limit (e.g., 1500 bytes), the encapsulated packet will exceed it, potentially leading to fragmentation or the need to adjust the TCP MSS (Maximum Segment Size).Encryption (Option D):Crucially, according to Juniper Service Provider documentation, neither GRE nor IP-IP provides native encryption or data confidentiality. They are encapsulation protocols, not security protocols. The payload remains in cleartext and is visible to any device along the path. If security and encryption are required for data traversing these tunnels, they must be combined with IPsec (IP Security). While GRE is often used as the "carrier" for IPsec (to allow multicast or dynamic routing protocols which IPsec alone does not support), the GRE protocol itself remains an unencrypted delivery mechanism. Therefore, statements A and D accurately describe the architectural behavior of these tunnel types.
What is the default export behavior of IS-IS in the Junos OS?
Answer(s): C
In the Junos OS, routing policy behavior is governed by default import and export rules that vary significantly between different protocols. For IS-IS (Intermediate System to Intermediate System), the default export policy is "reject all." This means that, by default, an IS-IS process will export nothing from the routing table into the IS-IS database.According to Juniper Networks technical documentation, IS-IS automatically advertises its own direct interfaces that are configured under the [edit protocols isis] hierarchy. However, it does not automatically redistribute routes learned from other sources—such as Static routes, OSPF, or BGP— into the IS-IS domain. This is a safety mechanism designed to prevent accidental routing loops or the flooding of unnecessary prefixes into the link-state database (LSDB), which could impact the stability of the SPF (Shortest Path First) algorithm.To move routes from the routing table (inet.0) into IS-IS, an administrator must explicitly create a routing policy and apply it as an export policy within the IS-IS configuration. For example:Code snippet set policy-options policy-statement REDIST-STATIC term 1 from protocol static set policy-options policy-statement REDIST-STATIC term 1 then accept set protocols isis export REDIST-STATICWithout such a policy, the IS-IS LSPs (Link-State PDUs) will only contain information about the IS-IS enabled interfaces and the reachability of other IS-IS neighbors. This behavior contrasts with protocols like BGP, which has different default rules for exporting active BGP routes to EBGP peers. In the context of IS-IS in a Juniper environment, "export nothing" is the standard operational baseline.
Which two statements are correct about TLVs in IS-IS? (Choose two.)
Answer(s): C,D
In the IS-IS protocol, TLVs (Type, Length, Value) are the fundamental building blocks used to carry information within Link-State PDUs (LSPs). Unlike some other protocols that have a fixed, rigid packet format, IS-IS was designed from the ground up to be modular and extensible. This extensibility is achieved through the use of TLVs, which allow the protocol to carry different types of data without requiring changes to the core protocol state machine.According to Juniper Networks technical documentation, TLVs allow flexible encoding of routing information (Option C). Each TLV specifies the "Type" of information it carries (such as neighbor information or IP reachability), the "Length" of that information, and the "Value" (the actual data). This architecture is what allowed IS-IS to easily support IPv6 by simply adding new TLVs (like TLV 236 for IPv6 reachability) without redesigning the protocol. It also supports Traffic Engineering (TE) extensions used in MPLS environments by adding TLVs that describe link bandwidth and administrative groups.Furthermore, a single LSP can contain multiple TLVs (Option D). When a Juniper router generates an LSP, it packs all the necessary information—such as the router's area addresses, its neighbors, and its local interface prefixes—into various TLVs and places them into a single PDU. If the amount of information exceeds the Maximum Transmission Unit (MTU) of the interface, the router will generate additional LSPs (fragmented LSPs) to carry the remaining TLVs.Options A and B are incorrect because restricting an LSP to a single TLV would make the protocol incredibly inefficient, and the very nature of IS-IS is its ability to support multiple network layer protocols (not just IPv4) through its agnostic TLV-based transport.
Post your Comments and Discuss Juniper JN0-364 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the JN0-364 content, but please register or login to continue.