Juniper Service Provider Routing and Switching, Specialist JN0-364 JNCIS-SP Exam Questions

Answer : A

The prevention of routing loops within an Autonomous System (AS) is handled differently than loop prevention between ASes. While External BGP (EBGP) uses the AS_PATH attribute to detect loops, Internal BGP (IBGP) does not modify the AS_PATH. Therefore, a different mechanism is required to ensure that a route does not circulate infinitely inside the network.

This mechanism is known as the IBGP Split Horizon rule. According to Juniper Networks documentation and the BGP standard (RFC 4271), a BGP speaker must not advertise a route learned via an IBGP peer to any other IBGP peer. In simpler terms, 'what is learned internally, stays local.' This rule ensures that a route only travels one 'hop' inside the AS---from the router that learned it from an external source to all other internal routers.

Because of this rule, IBGP routers do not naturally propagate routes through each other. This creates a requirement for a full mesh of IBGP sessions, where every BGP-speaking router in the AS must have a direct peering session with every other BGP-speaking router. To mitigate the scaling issues of a full mesh in large service provider networks, architects use Route Reflectors or Confederations, which are authorized exceptions to the Split Horizon rule.

Option B is incorrect because EBGP peers do advertise EBGP routes to other EBGP peers (this is how the internet works). Option C is incorrect because EBGP-learned routes must be sent to IBGP peers so the internal network knows how to reach the outside world. Option D is incorrect because internal routes must be sent to external peers to advertise your network to the internet.

Answer : B

In Junos OS, the flow of routing information is managed by policies that sit between the protocol's database (the RIB-In/LSDB) and the main routing table (inet.0). Understanding the direction of these policies is critical for correct configuration.

An import policy (Option B) is used to control the movement of routes from a routing protocol into the routing table. According to Juniper Service Provider documentation, even though IS-IS is a link-state protocol that requires all routers in an area to have an identical Link-State Database (LSDB), an import policy can be used to filter which of those validated routes are actually placed into inet.0 for forwarding. For external routes (routes leaked into IS-IS from other areas or protocols), an import policy allows an administrator to selectively accept or reject prefixes based on specific criteria like prefix-lists or community tags.

It is important to distinguish this from an export policy (Option A). In Junos, an export policy is used to take routes already in the routing table and push them out to a protocol to be advertised to neighbors. For example, you would use an export policy to redistribute static routes into IS-IS. Route preference (Option C) is a global value used to select between different protocols for the same prefix, and the interface metric (Option D) is used by the SPF algorithm to calculate the shortest path within the IS-IS database itself. Therefore, to specifically control which learned external routes are 'installed' into the forwarding table, the import policy is the correct tool.

Answer : B

In an MPLS network, routers are categorized by their role along a Label Switched Path (LSP). In this scenario, the LSP originates on R1 (Ingress LER) and terminates on R5 (Egress LER). Between these two endpoints are the Provider (P) routers, also known as Transit Label Switching Routers (LSRs), which include R2, R3, and R4.

To identify which router performs only label swap operations, we must look at the standard Junos data plane behavior:

R1 (Ingress LER): Performs a Push operation. It receives native IP traffic from Networks 1 or 2, looks up the destination, and imposes (pushes) an MPLS label onto the packet before sending it to R2.

R2 and R3 (Transit LSRs): These routers perform a Swap operation. They receive a labeled packet, look up the incoming label in their Label Forwarding Information Base (LFIB), replace it with an outgoing label provided by the downstream neighbor, and forward it.

R4 (Penultimate Hop): By default, Junos uses Penultimate Hop Popping (PHP). Because R4 is the second-to-last router before the egress (R5), the egress router R5 advertises an 'implicit-null' label (Label 3) to R4. This instructs R4 to perform a Pop operation---removing the MPLS label entirely---and sending the native IP packet to R5.

R5 (Egress LER): Receives the packet (which is already unlabeled due to PHP) and performs a standard IP route lookup to reach the final destination in Network 3 or 4.

Among the options provided, R3 is the only router that is a transit LSR but not the penultimate hop. While R2 also performs a swap, it is not an option. R4 performs a Pop (due to PHP), R1 performs a Push, and R5 performs an IP lookup. Therefore, R3 is the correct answer as it solely performs the label swap operation.

Answer : A, B, D

The Border Gateway Protocol (BGP) operates based on a strict set of advertisement rules designed to prevent routing loops while ensuring global reachability. These rules differ significantly depending on whether the relationship is External BGP (EBGP) or Internal BGP (IBGP).

1. EBGP Advertisement (Option A): In a standard EBGP scenario, a router acts as an exit/entry point for an Autonomous System. When an EBGP speaker receives a valid route from any peer (Internal or External), it will, by default, advertise that route to all of its other EBGP peers. This is the primary mechanism that allows prefixes to propagate across the global internet from one AS to another.

2. IBGP Split Horizon (Option D):

The most critical rule within an AS is the IBGP Split Horizon rule. To prevent loops within an AS, BGP dictates that a route learned from an IBGP peer must not be advertised to any other IBGP peer. This is why BGP requires a 'full mesh' of IBGP sessions or the use of Route Reflectors to ensure all internal routers learn all routes. Without this rule, a route could circulate infinitely within the AS because IBGP does not update the AS_PATH attribute.

3. EBGP to IBGP Propagation (Option B):

When a router learns a route from an EBGP peer, it is permitted to advertise that route to all of its IBGP peers. This ensures that everyone inside the network knows how to reach external destinations. However, it is important to remember that in Junos OS, the BGP Next Hop is not modified by default when sending routes to IBGP peers, often requiring a 'next-hop-self' policy to ensure internal reachability.

Options C and E are incorrect because they directly contradict these fundamental BGP loop-prevention and propagation mechanisms.

Answer : 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 Hop Popping (UHP) were configured (via the explicit-null command), the penultimate router would perform a Swap to Label 0 instead of a Pop.

Answer : B

In the IS-IS (Intermediate System to Intermediate System) protocol as implemented in Junos OS, routers can operate at two hierarchical levels: Level 1 (L1) for intra-area routing and Level 2 (L2) for inter-area backbone routing. By default, a Juniper router and its interfaces are configured to act as Level 1/2, meaning they will attempt to form adjacencies at both levels simultaneously.

According to Juniper Networks technical documentation, the show isis interface command provides a granular view of how the protocol is interacting with specific local links. In the provided exhibit, we must examine the L (Level) column and the DR (Designated Router) status columns to understand R1's operational state.

Level Configuration: Under the L column for both the physical interface ge-0/0/0.0 and the loopback lo0.0, the value is strictly 2. This indicates that these interfaces have been explicitly configured to operate only at Level 2.

Adjacency Capabilities: For the interface ge-0/0/0.0, the Level 1 DR field is marked as Disabled. This confirms that R1 is not participating in Level 1 operations on this link; it will not transmit Level 1 Hello PDUs, nor will it listen for them. Consequently, R1 is incapable of forming a Level 1 adjacency with R2 on this segment.

Metric Implications: The exhibit shows an L1/L2 Metric of 100/100. In Junos, 'narrow' metrics (the default) are limited to a maximum value of 63 per interface. A metric of 100 indicates that wide metrics (wide-metrics-only) have been enabled. Therefore, option A is incorrect because the router is using wide metrics.

Since the prompt states the adjacency is 'up,' and the interface is restricted to Level 2, we can conclude that R1 only forms a Level 2 adjacency with R2 (Option B). Even though an L1 metric of 100 is displayed in the table as a configured value, it is not actually 'advertised' in a Link-State PDU because the Level 1 protocol is disabled on that interface.

Answer : 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.