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

Junos devices learn about MAC addresses by examining the source MAC address of frames received on an interface and then storing these MAC addresses in the MAC address table (also known as the forwarding database) along with the interface on which the traffic was received.

Graceful Routing Engine Switchover (GRES) and Nonstop Active Routing (NSR) are two features used in Junos OS to provide high availability. GRES allows for the stateful failover of the Routing Engine, and NSR allows for the continuation of packet forwarding and protocol states during a Routing Engine switchover. These technologies ensure that peer nodes are not alerted during a switchover. VRRP and ISSU serve different purposes and do not apply to this specific requirement.

The FE80::/10 prefix is reserved for IPv6 link-local addresses. These addresses are auto-configured on all IPv6-enabled interfaces and can be used for communication within the local link (subnet) only.

References

Juniper Networks Technical Documentation on IPv6 Addressing

The show bgp neighbor command in Junos OS provides a detailed description of each BGP session, including session state, options configured, and counters for messages sent and received. This is the command you would use to see a detailed list of all established BGP sessions.

Wide metrics in IS-IS allow for a larger metric value than what is available with narrow metrics, which supports a maximum of 63. Wide metrics also enable an interface to advertise different metrics for Level 1 and Level 2, allowing for more flexible routing policies and greater scalability in large networks.

https://www.juniper.net/documentation/us/en/software/junos/static-routing/topics/ref/statement/qualified-next-hop-edit-routing-options.html

https://www.juniper.net/documentation/us/en/software/junos/static-routing/topics/topic-map/static-route-prefer-qualified-next-hop.html: Qualified next hops allow you to associate one or more properties with a particular next-hop address. You can set an overall preference for a particular static route and then specify a different preference for the qualified next hop. For example, suppose two next-hop addresses (10.10.10.10 and 10.10.10.7) are associated with the static route 192.168.47.5/32. A general preference is assigned to the entire static route, and then a different preference is assigned to only the qualified next-hop address 10.10.10.7. For example:

The qualified-next-hop statement with a static route is used to specify multiple next hops for a static route with different preferences (priorities). This allows for more granular control over the path selection process in the event that the primary next hop becomes unreachable.

The adjacency SID in segment routing is advertised by one router to inform another about the label that should be used to forward traffic to it over a particular link. In this scenario, Router B would advertise an adjacency SID to Router A, which would be used by Router A to forward traffic to Router B. Based on the exhibit, the adjacency SID that Router B advertises to Router A would be 12.

The exhibit shows the output of the command show spanning-tree bridge, which provides information about the spanning tree status of the switch. From the output, we can see that the switch has a bridge ID different from the root ID, which implies that this switch is not the root bridge. The "Topology change initiator" field shows ge-0/0/14, which indicates that the last topology change occurred on this interface, and this is also the interface used to reach the root bridge.

https://www.omnisecu.com/tcpip/ipv6/comparison-between-ipv4-header-and-ipv6-header.php#:~:text=IPv6%20header%20is%20much%20simpler%20than%20IPv4%20header. &text=The%20size%20of%20IPv6%20header,are%20128%20bit%20binary%20numbers.&text=In%20IPv4%20header%2C%20the%20source,are%2032%20bit%20binary%20numbers.

The flow label is a new field added to IPv6 headers that was not present in IPv4 headers. It is used to identify packets that require special handling by routers, particularly for quality-of-service (QoS) purposes.

By default, the router that originally sourced the route into BGP places its peer address into the attribute field. The next-hop value is then typically changed when the route is transmitted across external gGP (EBGP) links. Internal BGP (IBGP) peers do not alter the next-hop value between themselves.

B. By default, the next-hop value is changed when a route is passed from an EBGP peer to another EBGP peer.

C. By default, the next-hop value is retained when a route is advertised across IBGP links.