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

In Junos OS, a static route is a manually configured entry in the routing table. Unlike dynamic routes, which have built-in timers and aging mechanisms, static routes are generally 'permanent' as long as their conditions for validity are met.

1. Manual Removal (Option A):

Since static routes are explicitly defined by the administrator, the most direct way to remove one is through a configuration change. Using the delete routing-options static route command followed by a commit will immediately remove the route from the Routing Information Base (RIB).

2. Next-Hop Reachability (Option B):

For a static route to be 'active' and installed in the forwarding table, its next-hop must be reachable. If a static route points to a specific physical interface or an IP address on a local segment, and that outbound interface becomes unavailable (e.g., the link goes 'Down'), the Junos kernel detects that the next-hop is no longer viable. Consequently, the route is marked as 'hidden' or 'inactive' and is removed from the active forwarding table to prevent traffic from being black-holed.

Why other options are incorrect:

Aging (Option C): Static routes do not have an expiration timer based on traffic. Even if no packet is sent for years, the route remains as long as the interface is up.

Remote Reachability (Option D): Standard static routes only track the status of the local interface or the immediate next-hop. They do not possess 'end-to-end' visibility. If a host two hops away fails, the local router has no way of knowing this via the static route itself. To achieve this level of tracking, features like RPM (Real-time Performance Monitoring) or BFD (Bidirectional Forwarding Detection) must be linked to the static route.

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.

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.

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.

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).

In the Junos OS architecture, route preference (often referred to as administrative distance in other vendor platforms) is the primary metric used by the Routing Engine to select the 'best' path when multiple protocols provide a route to the same destination. Each routing protocol and route type is assigned a default numeric value; the lower the value, the more preferred the route.

According to Juniper Networks technical documentation, an aggregate route is assigned a default preference of 130. Aggregate routes are a form of static-like route used to group specific routes into a single, broader prefix to reduce the size of routing tables and limit the scope of routing updates. They are 'protocol-independent' because they are not learned from a dynamic neighbor but are manually defined by the administrator.

To understand where 130 fits in the hierarchy, it is helpful to compare it with other common Junos preferences:

Directly connected interfaces: 0

Static routes: 5

OSPF Internal: 10

IS-IS Level 1/2: 15/18

Aggregate routes: 130

OSPF AS External: 150

BGP (Internal and External): 170

Generated routes: 150

By setting the aggregate route preference to 130, Junos ensures that specific routes learned via IGPs (like OSPF or IS-IS) are preferred over the aggregate. This is essential because an aggregate route is often used as a 'catch-all' or a discard route when more specific path information is missing. If the aggregate had a lower preference (like 5), it might override dynamic routing information, leading to suboptimal routing or black-holed traffic.

For Juniper platforms equipped with dual Routing Engines (REs), the fundamental technology required to provide high availability during a hardware or software failure of the primary RE is Graceful Routing Engine Switchover (GRES).

According to Juniper Networks technical documentation, GRES allows the backup RE to stay in a 'hot' standby state. When GRES is enabled, the primary RE synchronizes critical state information with the backup RE, specifically the chassis state and the interface state. This synchronization includes the Packet Forwarding Engine (PFE) configuration.

When the primary RE fails, the backup RE takes over immediately. Because the PFE (which resides on the line cards) was already synchronized and is not restarted during the switchover, the router continues to forward packets that are already in flight or part of established flows. This prevents a complete network outage during an RE failover.

Comparison with other options:

NSB (Non-Stop Bridging - Option A): Focuses specifically on maintaining Layer 2 protocol states (like STP) during a switchover.

LAG (Link Aggregation - Option B): Provides redundancy for physical links, not the control plane or the RE.

BFD (Bidirectional Forwarding Detection - Option C): Is a protocol used for rapid detection of link or neighbor failures; it does not protect the RE or maintain forwarding during an internal switchover.

It is important to note that while GRES maintains the forwarding state, it does not by itself maintain the routing protocol state (adjacencies). To keep OSPF or BGP sessions from dropping during the switchover, GRES must be paired with Non-Stop Active Routing (NSR). However, as the question focuses on the core requirement of continuing to forward packets, GRES is the foundational technology.

In the IPv6 architecture, the base header is kept at a fixed size of 40 bytes to streamline processing. Any additional features or options are handled by Extension Headers, which are inserted between the IPv6 header and the upper-layer protocol. According to Juniper Networks technical documentation and RFC 8200, when a source node needs to list one or more intermediate nodes to be 'visited' on the way to the final destination, it utilizes the Routing extension header (Option B).

The Routing header is functionally similar to the 'Source Route' option in IPv4. When a packet contains a Routing header, it is addressed to the first intermediate node listed in the header. That node examines the header, swaps its own address with the next address in the list, and forwards the packet. This process continues until the packet reaches the final destination. This is a foundational component for technologies like Segment Routing over IPv6 (SRv6), where the Routing header (specifically the Segment Routing Header or SRH) is used to steer traffic through a specific set of service instructions or nodes.

To distinguish this from the other options:

Hop-by-hop options (Option A): These carry information that must be examined by every node along the path (such as Router Alert), not just specific intermediate nodes.

Fragment (Option C): This is used only when the source node needs to fragment a packet that exceeds the path MTU.

Destination options (Option D): These carry optional information intended specifically for the destination node (or nodes listed in a Routing header), but they do not dictate the path themselves.

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.

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.