Important Juniper JN0-664 JNCIP-SP Exam Questions

Answer: A, C

Explanation:

https://www.juniper.net/documentation/us/en/software/junos/ospf/topics/topic-map/configuring-ospfv2-sham-links.html

Answer: D

Explanation:

BGP Layer 2 VPNs use BGP to distribute endpoint provisioning information and set up pseudowires between PE devices. BGP uses the Layer 2 VPN (L2VPN) Routing Information Base (RIB) to store endpoint provisioning information, which is updated each time any Layer 2 virtual forwarding instance (VFI) is configured. The prefix and path information is stored in the L2VPN database, which allows BGP to make decisions about the best path.

In BGP Layer 2 VPNs, each site has a unique site ID that identifies it within a VFI. The site ID can be manually configured or automatically assigned by the PE device. By default, the site ID is automatically assigned based on the order that you add the interfaces to the site configuration. The first interface added to a site configuration has a site ID of 1, the second interface added has a site ID of 2, and so on.

Option D is correct because by default on PE-2, the remote site IDs are automatically assigned based on the order that you add the interfaces to the site configuration. Option A is not correct because by default on PE-2, the site's local ID is automatically assigned a value of 0 and does not need to be configured to match the total number of attached sites. Option B is not correct because you do not need to create a unique Layer 2 VPN routing instance for each site on the PE-2 device. You can create one routing instance for all sites within a VFI. Option C is not correct because you do not need to use separate physical interfaces to connect PE-2 to each site. You can use subinterfaces or service instances on a single physical interface.

Answer: B, C

Explanation:

Intermediate System to Intermediate System (IS-IS) is a link-state routing protocol that supports Level 1 (L1), Level 2 (L2), or both (L1/L2) operations. The way IS-IS sends Hello (IIH) packets depends on whether the interface is point-to-point (P2P) or broadcast (LAN).

Evaluating the Answer Choices

Option A: 'If a point-to-point interface is in both L1 and L2, separate hello messages are sent for each level.'

Incorrect!

On point-to-point (P2P) interfaces, only one combined Hello message is sent for both L1 and L2.

IS-IS P2P Hellos include both Level 1 and Level 2 TLVs in the same message.

This statement is incorrect.

Option B: 'If a point-to-point interface is in both L1 and L2, one combined hello message is sent for both levels.'

Correct!

On point-to-point (P2P) links, IS-IS sends a single Hello message that includes TLVs for both L1 and L2.

This reduces overhead and simplifies adjacency formation.

This statement is correct.

Option C: 'If a broadcast interface is in both L1 and L2, separate hello messages are sent for each level.'

Correct!

On broadcast (LAN) interfaces, IS-IS sends separate Hello messages for L1 and L2.

This is because L1 and L2 use separate Designated IS (DIS) elections and different multicast addresses:

L1 Hellos: Sent to AllL1IS (01:80:C2:00:00:14)

L2 Hellos: Sent to AllL2IS (01:80:C2:00:00:15)

This statement is correct.

Option D: 'If a broadcast interface is in both L1 and L2, one combined hello message is sent for both levels.'

Incorrect!

As stated above, IS-IS sends separate Hello messages for L1 and L2 on broadcast interfaces because they have independent DIS elections.

This statement is incorrect.

Final Answer:

B. If a point-to-point interface is in both L1 and L2, one combined hello message is sent for both levels. C. If a broadcast interface is in both L1 and L2, separate hello messages are sent for each level.

Verification from Juniper Documentation

Juniper IS-IS Configuration Guide confirms:

Point-to-Point (P2P) interfaces send one combined Hello for both levels.

Broadcast interfaces send separate L1 and L2 Hellos due to separate DIS elections.

RFC 1195 (IS-IS Extensions for IPv4) specifies that broadcast networks require distinct Hellos per level.

Answer: D

Explanation:

The auto-export parameter is a routing option that allows a routing instance to share routes with other routing instances or the master routing table. The auto-export parameter automatically exports routes from one routing instance to another based on the route target communities attached to the routes. In this scenario, the 10.101.1.0/24 route will be shared if the auto-export parameter is configured under [edit routing-options] hierarchy level.

Answer: A

Explanation:

https://www.juniper.net/documentation/us/en/software/junos/sampling-forwarding-monitoring/bgp/topics/concept/bgp-multipath-unequal-understanding.html