Pass the Juniper JNCIS-SP JN0-363 Questions and answers with ValidTests

Referring to the configuration in the exhibit, R1 is set to export the 3rd_Policy to the neighbor at 192.168.1.5. Since 3rd_Policy permits the 10.200.3.0/24 prefix, only that prefix will be advertised to the neighbor.

The "ultimate-hop-popping" term refers to the action taken by the penultimate router in an LSP to remove the MPLS label before delivering the packet to the ultimate router, which is not desired here. Configuring the "explicit-null" statement causes the penultimate router to replace the top label with a label that has a value of 0, which instructs the ultimate router to perform a label lookup and preserve the label switching for the entire LSP.

In the OSPF routing table output, prefixes are marked with different route types. An external prefix injected into OSPF is marked as 'Ext' (External) followed by a number that indicates whether it's an E1 or E2 route. The prefix 172.18.1.0/24 is marked as Ext2, which indicates that it is an external route that has been redistributed into OSPF from another routing protocol or static configuration.

References

Juniper Networks Technical Documentation on OSPF

https://supportportal.juniper.net/s/article/EX-Identify-the-Root-Bridge-in-a-Spanning-Tree-STP-network?language=en_US The root bridge in a spanning-tree network is the bridge with the smallest or the lowest bridge ID.

In the absence of a manually configured priority, the Spanning Tree Protocol (STP) elects the root bridge based on the lowest bridge ID, which is a combination of the priority and the MAC address. The device with the lowest MAC address will have the lowest bridge ID and thus be elected as the root bridge.

References

Juniper Networks Technical Documentation on STP

https://www.juniper.net/documentation/us/en/software/junos/high-availability/topics/task/nsr-configuring.html

Nonstop routing (NSR) requires both Graceful Routing Engine Switchover (GRES) and commit synchronization to be configured to maintain routing protocol and forwarding state during a Routing Engine switchover. NSR allows the secondary Routing Engine to take over the control plane without the protocols needing to restart, and GRES ensures that the forwarding plane continues operating with the current forwarding table. Commit synchronization ensures that configuration changes are synchronized between the primary and backup Routing Engines.

In the exhibit, the interface is configured with the native-vlan-id 20 parameter. This means that any untagged frames arriving on this interface will be associated with VLAN 20. The native VLAN serves as the default VLAN for untagged frames on a trunk port.

To ensure that MPLS traffic-engineered routes are used without affecting IGP routes in the route tables, the mpls-forwarding traffic engineering setting should be used. This setting allows MPLS to influence forwarding without changing the IGP route selection.

The exhibit shows an aggregate route configuration for the network 172.21.0.0/22, which would summarize the specific networks 172.21.0.0/24, 172.21.1.0/24, and 172.21.2.0/24. For an aggregate route to be active, it must have contributing routes in the routing table. If the route is hidden, it usually means there are no contributing routes that are active or the policy applied to the aggregate does not match any of the specific routes. Therefore, the first step in troubleshooting would be to verify that there are indeed active contributing routes for the aggregate to be valid.

The exhibit shows the show vrrp summary output from two routers, with both routers listing the state of their VRRP group as master. VRRP allows for multiple routers to share a virtual IP address and a virtual MAC address, but usually, only one router is the master at any given time while others are in backup state. However, in some configurations, VRRP can operate in an active/active mode where multiple routers handle traffic simultaneously for load sharing. Since both routers show the state as master and there is no evidence of misconfiguration in the virtual IP addresses or priority, it indicates that VRRP is likely functioning in an active/active setup.

The exhibit shows that the BGP session state is "Active," which generally indicates that the router is trying to establish a BGP session but has not received a response. One common cause for this issue is that there is no route to the BGP neighbor's address. Since the routers are using internal BGP (iBGP) and they are in the same AS, the AS number does not need to be unique, and a next-hop self policy is not strictly required for iBGP. The router-id is usually automatically determined and does not need to be explicitly set.