Free Juniper JN0-363 Practice Exam with Questions & Answers | Set: 2

The IPv6 header includes a new field that is not found in the IPv4 header, called the flow label. The flow label in IPv6 is used to identify packets that require special handling by routers for quality of service (QoS) or other reasons, allowing these packets to be handled efficiently as they move through the network.

References

• Juniper Networks Technical Documentation on IPv6
• IPv6 Header Fields - Juniper Networks

Theno-readvertisepolicy statement is used to prevent a static route from being redistributed into a dynamic routing protocol. This setting ensures that routes that are configured statically are not advertised out via dynamic routing protocols such as OSPF or BGP.

References

• Juniper Networks Technical Documentation on Routing Policy

IPv6 link-local addresses are automatically generated for each interface and have a prefix of fe80::/10. The interface's MAC address is typically used as part of the process to create the Interface Identifier (IID) in the link-local address, following the EUI-64 format.

References

• Juniper Networks Technical Documentation on IPv6
• IPv6 Interface Addresses - Juniper Networks

The Segment Routing Global Block (SRGB) defines a range of MPLS labels reserved for segment routing. With an SRGB starting label of 10,000 and an index range of 500, the first usable label is indeed 10,001 because label 10,000 is typically reserved and not usedfor forwarding. The last usable label would be 10,499 because the range includes 500 labels starting from 10,001.

References:

• Juniper Networks documentation on Segment Routing: Segment Routing Overview

https://www.cisco.com/c/en/us/support/docs/ip/open-shortest-path-first-ospf/13684-12.html#anc13

Neighbors Stuck in Exstart/Exchange State The problem occurs most frequently when you attempt to run OSPF between a Cisco router and another vendor router. The problem occurs when the maximum transmission unit (MTU) settings for neighboring router interfaces do not match. If the router with the higher MTU sends a packet larger that the MTU set on the neighboring router, the neighbor router ignores the packet. When this problem occurs, the output of the show ip ospf neighbor command displays output similar to what is shown in this figure.

A mismatched Maximum Transmission Unit (MTU) setting on OSPF interfaces can cause routers to get stuck in the ExStart state. OSPF requires that both sides of a link have the same MTU to form a full adjacency.References:

• OSPF Troubleshooting, Juniper Networks Documentation
• MTU and OSPF, Juniper Networks Documentation

To influence the path taken through an autonomous system, the Multi-Exit Discriminator (MED) attribute can be used. By setting a lower MED on R2 for routes advertised toR1 and R3, it will make the path through R2 to the 203.0.113.0/24 network more preferable.References:

• Understanding BGP Path Selection, Juniper TechLibrary
• BGP Attributes and Path Selection, Juniper TechLibrary

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

• BGP Policies, Juniper Networks Documentation
• Policy Framework, Juniper Networks Documentation

only 10.200.3.0/24 will be advertised. The neighbor export overrides anything at the group level and protocol level. Policies aren't additive, you can't apply all three at the same time. What if one of them rejected a prefix while the other accepted the same one? You need one to override the other

Local preference is a BGP attribute that dictates which path is preferred when multiple paths to the same destination are available. A higher local preference is preferred over a lower one. Since ISP A (AS 65501) is advertising a local preference of 100 and ISP B (AS 65502) is advertising a local preference of 200 to AS 65512, traffic from devices in AS 65512 will prefer the path via ISP B for all networks that ISP B advertises. However, since ISP A advertises the 172.20.21.0/24 network and ISP B does not, traffic for 172.20.21.0/24 will go through ISP A. For the 172.20.0.0/24 network, which both ISPs advertise, devices in AS 65512 will prefer the path via ISP B due to the higher local preference.

References:

• Juniper Networks documentation on BGP attributes: BGP Attributes and Policy

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

With Label Distribution Protocol (LDP), a full mesh of label-switched paths (LSPs) is automatically created between all LDP-enabled routers, and these paths are reflected in the inet.3 table. LDP LSPs are set up when LDP is enabled on interfaces connecting routers in an MPLS network.

References:

• Juniper Networks documentation on LDP: Understanding LDP