Master JN0-364: Juniper Service Provider Routing and Switching Specialist Certification Made Simple

Correct : C

In the world of BGP, controlling inbound traffic (traffic entering your network) is significantly more challenging than controlling outbound traffic because it requires influencing a decision made by an external Autonomous System (AS). According to Juniper Networks documentation, when you have multiple links to the same AS or even different ASes, the BGP path selection process is used by the upstream neighbor to decide which path to take to reach your prefixes.

AS-Path Prepending is the standard technique used to make a path appear less attractive to external peers. By artificially lengthening the AS_PATH attribute on the BGP advertisements sent over a specific link, you exploit the BGP best-path algorithm rule that prefers a shorter AS path. When you prepend your own AS number multiple times to the update sent to the 'less preferred' peer, that peer's BGP routers will see a longer path compared to the alternative link and will naturally prefer the shorter, unprepended route.

It is important to distinguish why other options are incorrect for this specific goal:

Local Preference (Option D): This is a well-known discretionary attribute used to influence outbound traffic. It is not advertised to EBGP peers; therefore, your upstream neighbor cannot see your local preference settings.

Origin Code (Option B): While the origin code (IGP, EGP, or Incomplete) is a tie-breaker in the selection process, it is rarely used for traffic engineering and lacks the granular control provided by prepending.

Route Reflector (Option A): This is an Internal BGP (IBGP) scaling mechanism used to reduce the need for a full mesh of peers within an AS; it does not directly influence external path selection by an upstream provider.

Junos OS allows you to easily implement prepending via routing policies applied as an 'export' policy to the EBGP neighbor. By using the as-path-prepend action within a policy term, you can selectively degrade a path's attractiveness to manage your inbound bandwidth.

Correct : D

In Virtual Router Redundancy Protocol (VRRP), the primary goal is to provide a highly available default gateway for end hosts. However, there is a specific operational behavior in the VRRP standard (RFC 3768/RFC 5798) regarding how the 'Virtual Router' responds to traffic destined for its own Virtual IP (VIP).

According to Juniper Networks documentation, by default, a VRRP router that is in the Master state will only respond to packets destined for the VIP if that router is the IP Address Owner (meaning its physical interface IP matches the VIP). If the router is a 'non-owner' (a common configuration in many networks), it will forward traffic on behalf of the VIP but will not respond to management traffic, such as ICMP Echo Requests (Pings), directed at the VIP itself.

To satisfy the requirement that 'servers connected to the network must be able to ping their gateway,' the accept-data (Option D) parameter must be configured. In Junos OS, the accept-data statement allows the VRRP Master to respond to traffic destined for the virtual IP address even if it is not the address owner. This includes responding to Pings and allowing other management connections like SSH or Telnet to the VIP.

Regarding the other options:

Preempt (Option B): While preempt is often used to ensure the primary router regains control, in Junos, a router with the highest priority (255) defaults to preemptive behavior, and accept-data is specifically what solves the 'pinging the gateway' requirement.

Track (Option A): Tracking is used for failover logic but doesn't affect the ability to ping the VIP.

Static ARP (Option C): This is unnecessary as VRRP uses a virtual MAC address to ensure hosts can resolve the VIP via standard NDP (for IPv6) or ARP (for IPv4).

Correct : B, C

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.

Correct : C, D

In a Juniper Networks MPLS environment, the process by which a router determines how to forward traffic involves both the control plane and the data plane. When R1 (acting as an Ingress Label Edge Router, or LER) receives an IP packet from Site A destined for Site B, it must perform a lookup to decide whether to forward the packet via standard IP routing or via an MPLS Label Switched Path (LSP).

The first criterion R1 uses is the destination address of the traffic (Option C). Upon receiving the native IP packet, R1 looks up the destination IP in its routing table (typically inet.0). If the destination matches a prefix that is associated with an LSP---such as the loopback address of R5 or a prefix reachable via R5---the router identifies the appropriate Forwarding Equivalence Class (FEC). The FEC essentially groups packets that should be forwarded in the same manner over the same path. Without identifying the destination, the router cannot map the traffic to the correct MPLS tunnel.

The second criterion is the label number advertisement received from R2 (Option D). MPLS relies on downstream label allocation. In this topology, R2 is the immediate downstream 'next hop' for R1 on the path to Site B. For the LSP to be established, R2 must signal a label to R1 using a protocol like LDP (Label Distribution Protocol) or RSVP (Resource Reservation Protocol). This label (in this case, 7166) tells R1: 'If you want to send traffic to the destination associated with this LSP, wrap it in this specific label so I know how to process it.'

R1 does not use the source address (Option A) for standard label mapping, nor does it receive the label directly from R5 (Option B) in a hop-by-hop signaling model; it must use the label provided by its direct neighbor, R2. Therefore, by combining the destination IP (to find the path) and the label provided by the next hop (to encapsulate the packet), R1 successfully directs the traffic through the MPLS core.

Correct : C

In the context of the Label Distribution Protocol (LDP), the method by which a router advertises labels to its neighbors is defined by its Label Advertisement Mode. According to Juniper Networks documentation and industry standards (RFC 5036), there are two primary modes: Downstream Unsolicited (DU) and Downstream on Demand (DoD).

In Downstream Unsolicited (DU) mode, which is the default behavior for Junos OS and most service provider implementations, an LSR (Label Switching Router) does not wait for a specific request from its neighbors. Instead, as soon as the LSR learns a prefix through its Interior Gateway Protocol (IGP) and establishes an LDP session, it automatically generates a label for that prefix and advertises it to all of its LDP peers. This explains the scenario where labels appear for every loopback address in the IGP as soon as LDP is enabled. DU mode is highly efficient for fast convergence because the labels are already present in the neighbors' databases before they are even needed for traffic forwarding.

By contrast, Downstream on Demand (DoD) requires a router to explicitly request a label for a specific prefix from its next-hop neighbor. Ordered Control (Option B) and Independent Control refer to the timing of label creation (whether a router waits for the next-hop to provide a label before creating its own), while Conservative Retention (Option A) refers to how a router stores labels it receives but doesn't currently use for forwarding. In the Junos default environment, LDP utilizes Downstream Unsolicited advertisement combined with Ordered Control and Liberal Retention to ensure a robust and rapidly converging MPLS control plane.