JN0-650 Premium File
- 107 Questions & Answers
- Last Update: Nov 8, 2026
An EVPN multihoming pair wants active-active delivery for a dual-attached CE, but only one PE is eligible because the Ethernet segment identity differs. The proposed correction is: Align supported ESI and multihoming configuration on both PEs and validate the CE bundle mode. Which observation MOST directly confirms this fault is resolved?
Both PEs advertise the same intended Ethernet segment identity and load sharing follows design. This is the direct acceptance evidence for the observed failure: An EVPN multihoming pair wants active-active delivery for a dual-attached CE, but only one PE is eligible because the Ethernet segment identity differs. The mechanism being validated is: Active-active EVPN multihoming requires participating PEs to identify the same Ethernet segment.
Frames received from a multihomed segment are not forwarded back toward that same Ethernet segment. That would validate a different condition: An EVPN fabric uses two active PEs for one Ethernet segment, but return traffic loops back to the same segment through a remote peer. The decisive check for the current issue is: Both PEs advertise the same intended Ethernet segment identity and load sharing follows design.
The two PEs recognize the shared ESI and participate in the intended DF election. That would validate a different condition: Two provider edge switches attach the same customer Ethernet segment but do not discover each other for designated-forwarder coordination. The decisive check for the current issue is: Both PEs advertise the same intended Ethernet segment identity and load sharing follows design.
Encapsulated tenant test packets traverse the underlay without fragmentation or MTU drops. That would validate a different condition: An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. The decisive check for the current issue is: Both PEs advertise the same intended Ethernet segment identity and load sharing follows design.
A Junos engineer proposes this response: Align supported ESI and multihoming configuration on both PEs and validate the CE bundle mode. The situation is: An EVPN multihoming pair wants active-active delivery for a dual-attached CE, but only one PE is eligible because the Ethernet segment identity differs. Which technical principle BEST justifies the response?
Active-active EVPN multihoming requires participating PEs to identify the same Ethernet segment. This is the controlling mechanism in the specific case: An EVPN multihoming pair wants active-active delivery for a dual-attached CE, but only one PE is eligible because the Ethernet segment identity differs. It predicts the acceptance result: Both PEs advertise the same intended Ethernet segment identity and load sharing follows design.
EVPN DF election limits downstream BUM forwarding to avoid loops on multihomed segments. This principle explains a separate situation: A dual-homed customer edge receives duplicate broadcast frames when both active PEs forward remote BUM traffic toward the same segment. For this issue the relevant mechanism is: Active-active EVPN multihoming requires participating PEs to identify the same Ethernet segment.
EVPN Type 3 routes signal inclusive multicast membership for broadcast, unknown unicast, and multicast delivery. This principle explains a separate situation: Two EVPN fabric leaves share a broadcast domain, but unknown-unicast and broadcast packets do not reach remote VTEPs. For this issue the relevant mechanism is: Active-active EVPN multihoming requires participating PEs to identify the same Ethernet segment.
EVPN route targets constrain which tenant reachability a participating leaf imports. This principle explains a separate situation: A fabric leaf has a BGP EVPN session in Established but no MAC reachability for VNI 50100 while other VNIs work. For this issue the relevant mechanism is: Active-active EVPN multihoming requires participating PEs to identify the same Ethernet segment.
An EVPN multihoming pair wants active-active delivery for a dual-attached CE, but only one PE is eligible because the Ethernet segment identity differs. If the team bypasses or fails to implement the targeted correction (Align supported ESI and multihoming configuration on both PEs and validate the CE bundle mode.), which direct operational risk or residual exposure is MOST relevant?
Inconsistent ESI values can prevent multihoming recognition and resilient aliasing. This is the consequence linked to the observed situation: An EVPN multihoming pair wants active-active delivery for a dual-attached CE, but only one PE is eligible because the Ethernet segment identity differs. It is prevented by: Align supported ESI and multihoming configuration on both PEs and validate the CE bundle mode. The underlying reason is: Active-active EVPN multihoming requires participating PEs to identify the same Ethernet segment.
Ignoring ESI split-horizon state can create loops even when remote MAC learning works. This risk belongs to a different operational problem: An EVPN fabric uses two active PEs for one Ethernet segment, but return traffic loops back to the same segment through a remote peer. The stated condition instead exposes this direct risk: Inconsistent ESI values can prevent multihoming recognition and resilient aliasing. The appropriate mitigation is: Align supported ESI and multihoming configuration on both PEs and validate the CE bundle mode.
Missing segment discovery can create inconsistent designated-forwarder decisions for BUM delivery. This risk belongs to a different operational problem: Two provider edge switches attach the same customer Ethernet segment but do not discover each other for designated-forwarder coordination. The stated condition instead exposes this direct risk: Inconsistent ESI values can prevent multihoming recognition and resilient aliasing. The appropriate mitigation is: Align supported ESI and multihoming configuration on both PEs and validate the CE bundle mode.
An underlay sized only for bare tenant frames can drop oversized encapsulated traffic. This risk belongs to a different operational problem: An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. The stated condition instead exposes this direct risk: Inconsistent ESI values can prevent multihoming recognition and resilient aliasing. The appropriate mitigation is: Align supported ESI and multihoming configuration on both PEs and validate the CE bundle mode.
A remote VXLAN leaf receives an EVPN Type 3 route for a VNI but no tenant host routes and the engineer assumes Type 3 can replace MAC reachability. Which targeted engineering change is MOST directly justified by the observed evidence?
Confirm that host MAC/IP advertisements use Type 2 routes in addition to Type 3 BUM membership. This change specifically addresses the reported evidence: A remote VXLAN leaf receives an EVPN Type 3 route for a VNI but no tenant host routes and the engineer assumes Type 3 can replace MAC reachability. The relevant protocol mechanism is: EVPN Type 2 and Type 3 signal different reachability functions and are not interchangeable. A decisive acceptance test would be: Type 2 entries identify the host next hop while Type 3 supports BUM delivery.
Verify the VNI's route-target import/export and Type 2 route visibility across the EVPN peers. This is a valid solution to a different Junos situation: A fabric leaf has a BGP EVPN session in Established but no MAC reachability for VNI 50100 while other VNIs work. It does not directly correct the specific failure evidence here: A remote VXLAN leaf receives an EVPN Type 3 route for a VNI but no tenant host routes and the engineer assumes Type 3 can replace MAC reachability. The required targeted change is: Confirm that host MAC/IP advertisements use Type 2 routes in addition to Type 3 BUM membership.
Check Type 3 inclusive-multicast EVPN routes and the configured BUM delivery method for that VNI. This is a valid solution to a different Junos situation: Two EVPN fabric leaves share a broadcast domain, but unknown-unicast and broadcast packets do not reach remote VTEPs. It does not directly correct the specific failure evidence here: A remote VXLAN leaf receives an EVPN Type 3 route for a VNI but no tenant host routes and the engineer assumes Type 3 can replace MAC reachability. The required targeted change is: Confirm that host MAC/IP advertisements use Type 2 routes in addition to Type 3 BUM membership.
Verify their EVPN Type 4 Ethernet segment routes and consistent nonzero Ethernet segment identifier. This is a valid solution to a different Junos situation: Two provider edge switches attach the same customer Ethernet segment but do not discover each other for designated-forwarder coordination. It does not directly correct the specific failure evidence here: A remote VXLAN leaf receives an EVPN Type 3 route for a VNI but no tenant host routes and the engineer assumes Type 3 can replace MAC reachability. The required targeted change is: Confirm that host MAC/IP advertisements use Type 2 routes in addition to Type 3 BUM membership.
A remote VXLAN leaf receives an EVPN Type 3 route for a VNI but no tenant host routes and the engineer assumes Type 3 can replace MAC reachability. The proposed correction is: Confirm that host MAC/IP advertisements use Type 2 routes in addition to Type 3 BUM membership. Which observation MOST directly confirms this fault is resolved?
Type 2 entries identify the host next hop while Type 3 supports BUM delivery. This is the direct acceptance evidence for the observed failure: A remote VXLAN leaf receives an EVPN Type 3 route for a VNI but no tenant host routes and the engineer assumes Type 3 can replace MAC reachability. The mechanism being validated is: EVPN Type 2 and Type 3 signal different reachability functions and are not interchangeable.
The remote leaf receives the intended Type 2 route and resolves the tenant MAC through the correct VTEP. That would validate a different condition: An EVPN-VXLAN leaf learns a local tenant MAC but remote VTEPs never learn that endpoint's MAC/IP binding from the control plane. The decisive check for the current issue is: Type 2 entries identify the host next hop while Type 3 supports BUM delivery.
VXLAN packets traverse the underlay and remote tenant unicast frames reach the destination. That would validate a different condition: An EVPN-VXLAN service has correct BGP Type 2 MAC routes but VXLAN data packets fail between leaves because UDP overlay transport is blocked by a security device. The decisive check for the current issue is: Type 2 entries identify the host next hop while Type 3 supports BUM delivery.
Encapsulated tenant test packets traverse the underlay without fragmentation or MTU drops. That would validate a different condition: An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. The decisive check for the current issue is: Type 2 entries identify the host next hop while Type 3 supports BUM delivery.
A Junos engineer proposes this response: Confirm that host MAC/IP advertisements use Type 2 routes in addition to Type 3 BUM membership. The situation is: A remote VXLAN leaf receives an EVPN Type 3 route for a VNI but no tenant host routes and the engineer assumes Type 3 can replace MAC reachability. Which technical principle BEST justifies the response?
EVPN Type 2 and Type 3 signal different reachability functions and are not interchangeable. This is the controlling mechanism in the specific case: A remote VXLAN leaf receives an EVPN Type 3 route for a VNI but no tenant host routes and the engineer assumes Type 3 can replace MAC reachability. It predicts the acceptance result: Type 2 entries identify the host next hop while Type 3 supports BUM delivery.
EVPN Type 2 routes advertise MAC and optionally IP reachability information between participating leaves. This principle explains a separate situation: An EVPN-VXLAN leaf learns a local tenant MAC but remote VTEPs never learn that endpoint's MAC/IP binding from the control plane. For this issue the relevant mechanism is: EVPN Type 2 and Type 3 signal different reachability functions and are not interchangeable.
EVPN BGP advertises reachability while VXLAN encapsulation carries actual Ethernet frames over IP. This principle explains a separate situation: An EVPN-VXLAN service has correct BGP Type 2 MAC routes but VXLAN data packets fail between leaves because UDP overlay transport is blocked by a security device. For this issue the relevant mechanism is: EVPN Type 2 and Type 3 signal different reachability functions and are not interchangeable.
VXLAN adds transport encapsulation overhead beyond the original Ethernet payload. This principle explains a separate situation: An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. For this issue the relevant mechanism is: EVPN Type 2 and Type 3 signal different reachability functions and are not interchangeable.
A remote VXLAN leaf receives an EVPN Type 3 route for a VNI but no tenant host routes and the engineer assumes Type 3 can replace MAC reachability. If the team bypasses or fails to implement the targeted correction (Confirm that host MAC/IP advertisements use Type 2 routes in addition to Type 3 BUM membership.), which direct operational risk or residual exposure is MOST relevant?
Using only Type 3 membership cannot provide specific remote unicast MAC location information. This is the consequence linked to the observed situation: A remote VXLAN leaf receives an EVPN Type 3 route for a VNI but no tenant host routes and the engineer assumes Type 3 can replace MAC reachability. It is prevented by: Confirm that host MAC/IP advertisements use Type 2 routes in addition to Type 3 BUM membership. The underlying reason is: EVPN Type 2 and Type 3 signal different reachability functions and are not interchangeable.
Absent Type 2 reachability can force unnecessary flooding or prevent remote unicast delivery. This risk belongs to a different operational problem: An EVPN-VXLAN leaf learns a local tenant MAC but remote VTEPs never learn that endpoint's MAC/IP binding from the control plane. The stated condition instead exposes this direct risk: Using only Type 3 membership cannot provide specific remote unicast MAC location information. The appropriate mitigation is: Confirm that host MAC/IP advertisements use Type 2 routes in addition to Type 3 BUM membership.
An established control-plane session cannot compensate for a blocked VXLAN data path. This risk belongs to a different operational problem: An EVPN-VXLAN service has correct BGP Type 2 MAC routes but VXLAN data packets fail between leaves because UDP overlay transport is blocked by a security device. The stated condition instead exposes this direct risk: Using only Type 3 membership cannot provide specific remote unicast MAC location information. The appropriate mitigation is: Confirm that host MAC/IP advertisements use Type 2 routes in addition to Type 3 BUM membership.
An underlay sized only for bare tenant frames can drop oversized encapsulated traffic. This risk belongs to a different operational problem: An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. The stated condition instead exposes this direct risk: Using only Type 3 membership cannot provide specific remote unicast MAC location information. The appropriate mitigation is: Confirm that host MAC/IP advertisements use Type 2 routes in addition to Type 3 BUM membership.
A fabric control plane should recognize a subnet's tenant IP prefix for inter-subnet forwarding, but the team is examining only EVPN MAC route tables. Which targeted engineering change is MOST directly justified by the observed evidence?
Verify the supported EVPN IP-prefix route model, including Type 5 where required by the design. This change specifically addresses the reported evidence: A fabric control plane should recognize a subnet's tenant IP prefix for inter-subnet forwarding, but the team is examining only EVPN MAC route tables. The relevant protocol mechanism is: EVPN Type 5 can advertise IP prefixes for tenant inter-subnet routed overlay connectivity. A decisive acceptance test would be: The remote tenant VRF receives the appropriate IP prefix with valid overlay next-hop resolution.
Verify BGP EVPN Type 2 MAC/IP route origination and route-target import for the affected VNI. This is a valid solution to a different Junos situation: An EVPN-VXLAN leaf learns a local tenant MAC but remote VTEPs never learn that endpoint's MAC/IP binding from the control plane. It does not directly correct the specific failure evidence here: A fabric control plane should recognize a subnet's tenant IP prefix for inter-subnet forwarding, but the team is examining only EVPN MAC route tables. The required targeted change is: Verify the supported EVPN IP-prefix route model, including Type 5 where required by the design.
Confirm that host MAC/IP advertisements use Type 2 routes in addition to Type 3 BUM membership. This is a valid solution to a different Junos situation: A remote VXLAN leaf receives an EVPN Type 3 route for a VNI but no tenant host routes and the engineer assumes Type 3 can replace MAC reachability. It does not directly correct the specific failure evidence here: A fabric control plane should recognize a subnet's tenant IP prefix for inter-subnet forwarding, but the team is examining only EVPN MAC route tables. The required targeted change is: Verify the supported EVPN IP-prefix route model, including Type 5 where required by the design.
Restore authorized VXLAN UDP transport and IP reachability between the participating VTEP endpoints. This is a valid solution to a different Junos situation: An EVPN-VXLAN service has correct BGP Type 2 MAC routes but VXLAN data packets fail between leaves because UDP overlay transport is blocked by a security device. It does not directly correct the specific failure evidence here: A fabric control plane should recognize a subnet's tenant IP prefix for inter-subnet forwarding, but the team is examining only EVPN MAC route tables. The required targeted change is: Verify the supported EVPN IP-prefix route model, including Type 5 where required by the design.
A fabric control plane should recognize a subnet's tenant IP prefix for inter-subnet forwarding, but the team is examining only EVPN MAC route tables. The proposed correction is: Verify the supported EVPN IP-prefix route model, including Type 5 where required by the design. Which observation MOST directly confirms this fault is resolved?
The remote tenant VRF receives the appropriate IP prefix with valid overlay next-hop resolution. This is the direct acceptance evidence for the observed failure: A fabric control plane should recognize a subnet's tenant IP prefix for inter-subnet forwarding, but the team is examining only EVPN MAC route tables. The mechanism being validated is: EVPN Type 5 can advertise IP prefixes for tenant inter-subnet routed overlay connectivity.
The remote leaf receives the intended Type 2 route and resolves the tenant MAC through the correct VTEP. That would validate a different condition: An EVPN-VXLAN leaf learns a local tenant MAC but remote VTEPs never learn that endpoint's MAC/IP binding from the control plane. The decisive check for the current issue is: The remote tenant VRF receives the appropriate IP prefix with valid overlay next-hop resolution.
Type 2 entries identify the host next hop while Type 3 supports BUM delivery. That would validate a different condition: A remote VXLAN leaf receives an EVPN Type 3 route for a VNI but no tenant host routes and the engineer assumes Type 3 can replace MAC reachability. The decisive check for the current issue is: The remote tenant VRF receives the appropriate IP prefix with valid overlay next-hop resolution.
VXLAN packets traverse the underlay and remote tenant unicast frames reach the destination. That would validate a different condition: An EVPN-VXLAN service has correct BGP Type 2 MAC routes but VXLAN data packets fail between leaves because UDP overlay transport is blocked by a security device. The decisive check for the current issue is: The remote tenant VRF receives the appropriate IP prefix with valid overlay next-hop resolution.
A Junos engineer proposes this response: Verify the supported EVPN IP-prefix route model, including Type 5 where required by the design. The situation is: A fabric control plane should recognize a subnet's tenant IP prefix for inter-subnet forwarding, but the team is examining only EVPN MAC route tables. Which technical principle BEST justifies the response?
EVPN Type 5 can advertise IP prefixes for tenant inter-subnet routed overlay connectivity. This is the controlling mechanism in the specific case: A fabric control plane should recognize a subnet's tenant IP prefix for inter-subnet forwarding, but the team is examining only EVPN MAC route tables. It predicts the acceptance result: The remote tenant VRF receives the appropriate IP prefix with valid overlay next-hop resolution.
EVPN Type 2 routes advertise MAC and optionally IP reachability information between participating leaves. This principle explains a separate situation: An EVPN-VXLAN leaf learns a local tenant MAC but remote VTEPs never learn that endpoint's MAC/IP binding from the control plane. For this issue the relevant mechanism is: EVPN Type 5 can advertise IP prefixes for tenant inter-subnet routed overlay connectivity.
EVPN Type 2 and Type 3 signal different reachability functions and are not interchangeable. This principle explains a separate situation: A remote VXLAN leaf receives an EVPN Type 3 route for a VNI but no tenant host routes and the engineer assumes Type 3 can replace MAC reachability. For this issue the relevant mechanism is: EVPN Type 5 can advertise IP prefixes for tenant inter-subnet routed overlay connectivity.
EVPN BGP advertises reachability while VXLAN encapsulation carries actual Ethernet frames over IP. This principle explains a separate situation: An EVPN-VXLAN service has correct BGP Type 2 MAC routes but VXLAN data packets fail between leaves because UDP overlay transport is blocked by a security device. For this issue the relevant mechanism is: EVPN Type 5 can advertise IP prefixes for tenant inter-subnet routed overlay connectivity.
A fabric control plane should recognize a subnet's tenant IP prefix for inter-subnet forwarding, but the team is examining only EVPN MAC route tables. If the team bypasses or fails to implement the targeted correction (Verify the supported EVPN IP-prefix route model, including Type 5 where required by the design.), which direct operational risk or residual exposure is MOST relevant?
Expecting MAC-only routes to replace required tenant IP prefix exchange can break routed overlay traffic. This is the consequence linked to the observed situation: A fabric control plane should recognize a subnet's tenant IP prefix for inter-subnet forwarding, but the team is examining only EVPN MAC route tables. It is prevented by: Verify the supported EVPN IP-prefix route model, including Type 5 where required by the design. The underlying reason is: EVPN Type 5 can advertise IP prefixes for tenant inter-subnet routed overlay connectivity.
Absent Type 2 reachability can force unnecessary flooding or prevent remote unicast delivery. This risk belongs to a different operational problem: An EVPN-VXLAN leaf learns a local tenant MAC but remote VTEPs never learn that endpoint's MAC/IP binding from the control plane. The stated condition instead exposes this direct risk: Expecting MAC-only routes to replace required tenant IP prefix exchange can break routed overlay traffic. The appropriate mitigation is: Verify the supported EVPN IP-prefix route model, including Type 5 where required by the design.
Using only Type 3 membership cannot provide specific remote unicast MAC location information. This risk belongs to a different operational problem: A remote VXLAN leaf receives an EVPN Type 3 route for a VNI but no tenant host routes and the engineer assumes Type 3 can replace MAC reachability. The stated condition instead exposes this direct risk: Expecting MAC-only routes to replace required tenant IP prefix exchange can break routed overlay traffic. The appropriate mitigation is: Verify the supported EVPN IP-prefix route model, including Type 5 where required by the design.
An established control-plane session cannot compensate for a blocked VXLAN data path. This risk belongs to a different operational problem: An EVPN-VXLAN service has correct BGP Type 2 MAC routes but VXLAN data packets fail between leaves because UDP overlay transport is blocked by a security device. The stated condition instead exposes this direct risk: Expecting MAC-only routes to replace required tenant IP prefix exchange can break routed overlay traffic. The appropriate mitigation is: Verify the supported EVPN IP-prefix route model, including Type 5 where required by the design.
Please check your mailbox for a message from support@examlabs.com and follow the directions.