Juniper JN0-364 Exam Dumps

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.

In a Juniper Networks environment, Resource Reservation Protocol (RSVP) is a signaling protocol used to establish Label-Switched Paths (LSPs). While RSVP handles the actual signaling (requesting labels and reserving bandwidth along a path), it does not inherently know which path to take. This is where Constrained Shortest Path First (CSPF) comes into play.

CSPF is an advanced version of the Dijkstra algorithm used specifically for traffic engineering. Unlike the standard SPF used by IGPs, which only considers the shortest metric, CSPF takes into account multiple constraints such as available bandwidth, link coloring (administrative groups), and explicit hop requirements. According to Juniper technical documentation, when an LSP is configured, the Ingress router uses CSPF to calculate a loop-free path that satisfies all these constraints before RSVP begins signaling. This is why statement B is the correct description of the operational flow.

Statement D is a common distractor. While CSPF uses the Traffic Engineering Database (TED) to perform its calculations, the path is not 'calculated by the TED' itself; the TED is merely the repository of link-state information (provided by OSPF or IS-IS extensions). Statement C refers to Segment Routing Global Block (SRGB), which is relevant to Segment Routing (SR-TE), not standard RSVP-signaled LSPs. Finally, statement A is incorrect because admin-groups (link coloring) are actually one of the primary constraints that require CSPF to determine a valid path.

In the Border Gateway Protocol (BGP) finite state machine (FSM), the Established state is the final and functional stage of a BGP peering session. According to Juniper Networks technical documentation, once a session reaches this state, the two peers have successfully exchanged Open messages and agreed upon session parameters (such as AS numbers, hold timers, and BGP identifiers). Only after the session is 'Established' can the routers begin the actual exchange of network layer reachability information (NLRI).

The most frequent message type exchanged in the Established state is the UPDATE message. These messages are the heart of BGP operations; they are used to advertise new feasible routes to a peer or to withdraw routes that are no longer reachable. An UPDATE message contains path attributes (like AS-Path, Next-Hop, and Local Preference) and the associated prefixes. In a stable network, UPDATE messages are only sent when there is a change in the topology, adhering to BGP's incremental update philosophy.

The second message type that can be exchanged in this state is the NOTIFICATION message. While ideally, a session stays established, any detected error---such as a hold timer expiration, a malformed update, or a manual 'clear' command---will trigger the transmission of a NOTIFICATION message. This message informs the peer of the specific error code and immediately causes the BGP session to transition back to the Idle state, tearing down the TCP connection.

It is important to note that OPEN messages (Option A) are only used during the session initialization phase to transition from the OpenConfirm state to Established. REQUEST (Option B) is not a valid BGP message type defined in the standard (RFC 4271); the closest equivalent in functionality would be a Route-Refresh message, which is a separate extension. Therefore, in the context of standard BGP operations within the Established state, Updates and Notifications are the correct answers.

The AS_PATH attribute is a 'well-known mandatory' attribute in BGP, meaning it must be present in every BGP Update message exchanged between External BGP (eBGP) peers. It records the sequence of Autonomous System numbers that a route has traversed. Per Juniper Networks Service Provider documentation, this attribute serves two fundamental purposes:

1. Loop Prevention (Option B):

This is the most critical function of the AS_PATH. When a BGP router receives an update from an eBGP peer, it scans the AS_PATH attribute for its own AS number. If the router finds its local AS number already listed in the path, it concludes that the route has already passed through its network and has 'looped' back. To prevent an infinite routing loop, the router will immediately discard the update. This mechanism is the cornerstone of BGP's stability as a path-vector protocol.

2. Path Selection / Shortest Path Determination (Option C):

BGP uses a complex 'tie-breaking' algorithm to select the best path among multiple candidates. One of the highest-ranking criteria in this algorithm (after Weight, Local Preference, and AS_PATH length) is the length of the AS_PATH. A shorter AS_PATH (fewer AS numbers listed) is generally preferred over a longer one, as it typically represents a more direct path through the internet hierarchy.

Why other options are incorrect:

Option A: The 'origin' of a route (IGP, EGP, or Incomplete) is determined by the ORIGIN attribute, which is a separate well-known mandatory attribute.

Option D: BGP does not count individual 'next-hop devices' (which would be an IGP metric like hop count in RIP); it only tracks Autonomous Systems. A single AS in the path might contain hundreds of internal routers (next-hops), but BGP only sees it as one 'hop' in the AS_PATH.

When implementing Multiprotocol BGP (MP-BGP) for IPv6, several architectural constants remain consistent with the original BGP design, while others have evolved to accommodate larger network scales.

Router ID (Option C):

A critical point in Juniper's Service Provider documentation is that the BGP Router ID remains a 32-bit value, even when the protocol is carrying 128-bit IPv6 prefixes. The Router ID is typically represented in dotted-quad notation (e.g., 192.168.1.1). In an IPv6-only environment, a Juniper router cannot automatically derive this ID from an interface address, so it must be manually defined under [edit routing-options]. This 32-bit ID is essential for BGP tie-breaking and loop prevention within the AS.

Autonomous System Number (Option D):

The Autonomous System Number (ASN) was originally a 16-bit value (0 to 65535). However, to address the exhaustion of available ASNs, the standard was extended to 32-bit ASNs (documented in RFC 6793). In Junos OS, you can configure BGP using either the older 16-bit format or the newer 32-bit format (often represented in 'asplain' or 'asdot' notation). While the question mentions a 64-bit value, there is currently no standard for a 64-bit ASN in BGP; the transition from 16-bit to 32-bit satisfies current global scalability needs. Therefore, Option D is the most accurate within the context of current networking standards, as it acknowledges the coexistence of different ASN lengths.