JN0-650 Premium File
- 107 Questions & Answers
- Last Update: Nov 8, 2026
Two provider edge switches attach the same customer Ethernet segment but do not discover each other for designated-forwarder coordination. If the team bypasses or fails to implement the targeted correction (Verify their EVPN Type 4 Ethernet segment routes and consistent nonzero Ethernet segment identifier.), which direct operational risk or residual exposure is MOST relevant?
Missing segment discovery can create inconsistent designated-forwarder decisions for BUM delivery. This is the consequence linked to the observed situation: Two provider edge switches attach the same customer Ethernet segment but do not discover each other for designated-forwarder coordination. It is prevented by: Verify their EVPN Type 4 Ethernet segment routes and consistent nonzero Ethernet segment identifier. The underlying reason is: EVPN Type 4 Ethernet segment routes support discovery among PEs attached to one multihomed segment.
Ignoring Type 1 withdrawal can prolong traffic blackholing after a multihomed attachment fails. This risk belongs to a different operational problem: A multihomed customer edge loses a PE uplink, yet remote ingress PEs keep forwarding toward withdrawn Ethernet segment reachability. The stated condition instead exposes this direct risk: Missing segment discovery can create inconsistent designated-forwarder decisions for BUM delivery. The appropriate mitigation is: Verify their EVPN Type 4 Ethernet segment routes and consistent nonzero Ethernet segment identifier.
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: Missing segment discovery can create inconsistent designated-forwarder decisions for BUM delivery. The appropriate mitigation is: Verify their EVPN Type 4 Ethernet segment routes and consistent nonzero Ethernet segment identifier.
Missing Type 3 membership can blackhole broadcast and discovery traffic across the VXLAN overlay. This risk belongs to a different operational problem: Two EVPN fabric leaves share a broadcast domain, but unknown-unicast and broadcast packets do not reach remote VTEPs. The stated condition instead exposes this direct risk: Missing segment discovery can create inconsistent designated-forwarder decisions for BUM delivery. The appropriate mitigation is: Verify their EVPN Type 4 Ethernet segment routes and consistent nonzero Ethernet segment identifier.
A dual-homed customer edge receives duplicate broadcast frames when both active PEs forward remote BUM traffic toward the same segment. Which targeted engineering change is MOST directly justified by the observed evidence?
Correct designated-forwarder election and non-DF egress suppression for that Ethernet segment and VLAN. This change specifically addresses the reported evidence: A dual-homed customer edge receives duplicate broadcast frames when both active PEs forward remote BUM traffic toward the same segment. The relevant protocol mechanism is: EVPN DF election limits downstream BUM forwarding to avoid loops on multihomed segments. A decisive acceptance test would be: Only the elected DF delivers remote BUM frames to the customer segment for the affected VLAN.
Inspect EVPN ESI split-horizon filtering and associated multihoming route attributes. This is a valid solution to a different Junos situation: An EVPN fabric uses two active PEs for one Ethernet segment, but return traffic loops back to the same segment through a remote peer. It does not directly correct the specific failure evidence here: A dual-homed customer edge receives duplicate broadcast frames when both active PEs forward remote BUM traffic toward the same segment. The required targeted change is: Correct designated-forwarder election and non-DF egress suppression for that Ethernet segment and VLAN.
Align supported ESI and multihoming configuration on both PEs and validate the CE bundle mode. This is a valid solution to a different Junos 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 does not directly correct the specific failure evidence here: A dual-homed customer edge receives duplicate broadcast frames when both active PEs forward remote BUM traffic toward the same segment. The required targeted change is: Correct designated-forwarder election and non-DF egress suppression for that Ethernet segment and VLAN.
Engineer end-to-end underlay MTU headroom for the supported VXLAN packet size. This is a valid solution to a different Junos situation: An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. It does not directly correct the specific failure evidence here: A dual-homed customer edge receives duplicate broadcast frames when both active PEs forward remote BUM traffic toward the same segment. The required targeted change is: Correct designated-forwarder election and non-DF egress suppression for that Ethernet segment and VLAN.
A dual-homed customer edge receives duplicate broadcast frames when both active PEs forward remote BUM traffic toward the same segment. The proposed correction is: Correct designated-forwarder election and non-DF egress suppression for that Ethernet segment and VLAN. Which observation MOST directly confirms this fault is resolved?
Only the elected DF delivers remote BUM frames to the customer segment for the affected VLAN. This is the direct acceptance evidence for the observed failure: A dual-homed customer edge receives duplicate broadcast frames when both active PEs forward remote BUM traffic toward the same segment. The mechanism being validated is: EVPN DF election limits downstream BUM forwarding to avoid loops on multihomed segments.
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: Only the elected DF delivers remote BUM frames to the customer segment for the affected VLAN.
Remote PEs withdraw or reroute dependent MAC reachability promptly after the segment fails. That would validate a different condition: A multihomed customer edge loses a PE uplink, yet remote ingress PEs keep forwarding toward withdrawn Ethernet segment reachability. The decisive check for the current issue is: Only the elected DF delivers remote BUM frames to the customer segment for the affected VLAN.
Traffic reaches only VTEPs participating in the appropriate tenant VNI. That would validate a different condition: Two tenants share the same physical VXLAN underlay but their Layer 2 broadcasts must remain separate despite overlapping inner VLAN numbers. The decisive check for the current issue is: Only the elected DF delivers remote BUM frames to the customer segment for the affected VLAN.
A Junos engineer proposes this response: Correct designated-forwarder election and non-DF egress suppression for that Ethernet segment and VLAN. The situation is: A dual-homed customer edge receives duplicate broadcast frames when both active PEs forward remote BUM traffic toward the same segment. Which technical principle BEST justifies the response?
EVPN DF election limits downstream BUM forwarding to avoid loops on multihomed segments. This is the controlling mechanism in the specific case: A dual-homed customer edge receives duplicate broadcast frames when both active PEs forward remote BUM traffic toward the same segment. It predicts the acceptance result: Only the elected DF delivers remote BUM frames to the customer segment for the affected VLAN.
EVPN Type 4 Ethernet segment routes support discovery among PEs attached to one multihomed segment. This principle explains a separate situation: Two provider edge switches attach the same customer Ethernet segment but do not discover each other for designated-forwarder coordination. For this issue the relevant mechanism is: EVPN DF election limits downstream BUM forwarding to avoid loops on multihomed segments.
EVPN Type 1 Ethernet autodiscovery supports multihoming convergence and Ethernet segment reachability withdrawal. This principle explains a separate situation: A multihomed customer edge loses a PE uplink, yet remote ingress PEs keep forwarding toward withdrawn Ethernet segment reachability. For this issue the relevant mechanism is: EVPN DF election limits downstream BUM forwarding to avoid loops on multihomed segments.
VXLAN VNIs identify isolated logical overlay segments over a shared routed underlay. This principle explains a separate situation: Two tenants share the same physical VXLAN underlay but their Layer 2 broadcasts must remain separate despite overlapping inner VLAN numbers. For this issue the relevant mechanism is: EVPN DF election limits downstream BUM forwarding to avoid loops on multihomed segments.
A dual-homed customer edge receives duplicate broadcast frames when both active PEs forward remote BUM traffic toward the same segment. If the team bypasses or fails to implement the targeted correction (Correct designated-forwarder election and non-DF egress suppression for that Ethernet segment and VLAN.), which direct operational risk or residual exposure is MOST relevant?
If both multihomed PEs forward the same remote BUM packets, customer-side loops or duplicates can occur. This is the consequence linked to the observed situation: A dual-homed customer edge receives duplicate broadcast frames when both active PEs forward remote BUM traffic toward the same segment. It is prevented by: Correct designated-forwarder election and non-DF egress suppression for that Ethernet segment and VLAN. The underlying reason is: EVPN DF election limits downstream BUM forwarding to avoid loops on multihomed segments.
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: If both multihomed PEs forward the same remote BUM packets, customer-side loops or duplicates can occur. The appropriate mitigation is: Correct designated-forwarder election and non-DF egress suppression for that Ethernet segment and VLAN.
Ignoring Type 1 withdrawal can prolong traffic blackholing after a multihomed attachment fails. This risk belongs to a different operational problem: A multihomed customer edge loses a PE uplink, yet remote ingress PEs keep forwarding toward withdrawn Ethernet segment reachability. The stated condition instead exposes this direct risk: If both multihomed PEs forward the same remote BUM packets, customer-side loops or duplicates can occur. The appropriate mitigation is: Correct designated-forwarder election and non-DF egress suppression for that Ethernet segment and VLAN.
Reusing a tenant VNI inadvertently can merge unrelated broadcast domains. This risk belongs to a different operational problem: Two tenants share the same physical VXLAN underlay but their Layer 2 broadcasts must remain separate despite overlapping inner VLAN numbers. The stated condition instead exposes this direct risk: If both multihomed PEs forward the same remote BUM packets, customer-side loops or duplicates can occur. The appropriate mitigation is: Correct designated-forwarder election and non-DF egress suppression for that Ethernet segment and VLAN.
An EVPN fabric uses two active PEs for one Ethernet segment, but return traffic loops back to the same segment through a remote peer. Which targeted engineering change is MOST directly justified by the observed evidence?
Inspect EVPN ESI split-horizon filtering and associated multihoming route attributes. This change specifically addresses the reported evidence: 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 relevant protocol mechanism is: EVPN split horizon prevents duplicate forwarding back to the originating Ethernet segment. A decisive acceptance test would be: Frames received from a multihomed segment are not forwarded back toward that same Ethernet segment.
Align supported ESI and multihoming configuration on both PEs and validate the CE bundle mode. This is a valid solution to a different Junos 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 does not directly correct the specific failure evidence here: 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 required targeted change is: Inspect EVPN ESI split-horizon filtering and associated multihoming route attributes.
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: 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 required targeted change is: Inspect EVPN ESI split-horizon filtering and associated multihoming route attributes.
Inspect new Type 2 MAC advertisement and MAC mobility sequence handling after the move. This is a valid solution to a different Junos situation: A virtual machine moves to a different EVPN leaf, yet remote leaves continue using the stale previous VTEP for its MAC. It does not directly correct the specific failure evidence here: 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 required targeted change is: Inspect EVPN ESI split-horizon filtering and associated multihoming route attributes.
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 proposed correction is: Inspect EVPN ESI split-horizon filtering and associated multihoming route attributes. Which observation MOST directly confirms this fault is resolved?
Frames received from a multihomed segment are not forwarded back toward that same Ethernet segment. This is the direct acceptance evidence for the observed failure: 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 mechanism being validated is: EVPN split horizon prevents duplicate forwarding back to the originating Ethernet segment.
Both PEs advertise the same intended Ethernet segment identity and load sharing follows design. That would validate a different condition: 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 decisive check for the current issue is: Frames received from a multihomed segment are not forwarded back toward that same Ethernet segment.
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: Frames received from a multihomed segment are not forwarded back toward that same Ethernet segment.
The remote tenant VRF receives the appropriate IP prefix with valid overlay next-hop resolution. That would validate a different condition: 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 decisive check for the current issue is: Frames received from a multihomed segment are not forwarded back toward that same Ethernet segment.
A Junos engineer proposes this response: Inspect EVPN ESI split-horizon filtering and associated multihoming route attributes. The situation is: An EVPN fabric uses two active PEs for one Ethernet segment, but return traffic loops back to the same segment through a remote peer. Which technical principle BEST justifies the response?
EVPN split horizon prevents duplicate forwarding back to the originating Ethernet segment. This is the controlling mechanism in the specific case: An EVPN fabric uses two active PEs for one Ethernet segment, but return traffic loops back to the same segment through a remote peer. It predicts the acceptance result: Frames received from a multihomed segment are not forwarded back toward that same Ethernet segment.
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: EVPN split horizon prevents duplicate forwarding back to the originating Ethernet segment.
EVPN Type 1 Ethernet autodiscovery supports multihoming convergence and Ethernet segment reachability withdrawal. This principle explains a separate situation: A multihomed customer edge loses a PE uplink, yet remote ingress PEs keep forwarding toward withdrawn Ethernet segment reachability. For this issue the relevant mechanism is: EVPN split horizon prevents duplicate forwarding back to the originating Ethernet segment.
EVPN MAC mobility mechanisms coordinate changed endpoint attachment locations. This principle explains a separate situation: A virtual machine moves to a different EVPN leaf, yet remote leaves continue using the stale previous VTEP for its MAC. For this issue the relevant mechanism is: EVPN split horizon prevents duplicate forwarding back to the originating Ethernet segment.
An EVPN fabric uses two active PEs for one Ethernet segment, but return traffic loops back to the same segment through a remote peer. If the team bypasses or fails to implement the targeted correction (Inspect EVPN ESI split-horizon filtering and associated multihoming route attributes.), which direct operational risk or residual exposure is MOST relevant?
Ignoring ESI split-horizon state can create loops even when remote MAC learning works. This is the consequence linked to the observed situation: An EVPN fabric uses two active PEs for one Ethernet segment, but return traffic loops back to the same segment through a remote peer. It is prevented by: Inspect EVPN ESI split-horizon filtering and associated multihoming route attributes. The underlying reason is: EVPN split horizon prevents duplicate forwarding back to the originating Ethernet segment.
Inconsistent ESI values can prevent multihoming recognition and resilient aliasing. This risk belongs to a different operational problem: 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 stated condition instead exposes this direct risk: Ignoring ESI split-horizon state can create loops even when remote MAC learning works. The appropriate mitigation is: Inspect EVPN ESI split-horizon filtering and associated multihoming route attributes.
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: Ignoring ESI split-horizon state can create loops even when remote MAC learning works. The appropriate mitigation is: Inspect EVPN ESI split-horizon filtering and associated multihoming route attributes.
Expecting MAC-only routes to replace required tenant IP prefix exchange can break routed overlay traffic. This risk belongs to a different operational problem: 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 stated condition instead exposes this direct risk: Ignoring ESI split-horizon state can create loops even when remote MAC learning works. The appropriate mitigation is: Inspect EVPN ESI split-horizon filtering and associated multihoming route attributes.
A fabric leaf has a BGP EVPN session in Established but no MAC reachability for VNI 50100 while other VNIs work. Which targeted engineering change is MOST directly justified by the observed evidence?
Verify the VNI's route-target import/export and Type 2 route visibility across the EVPN peers. This change specifically addresses the reported evidence: A fabric leaf has a BGP EVPN session in Established but no MAC reachability for VNI 50100 while other VNIs work. The relevant protocol mechanism is: EVPN route targets constrain which tenant reachability a participating leaf imports. A decisive acceptance test would be: Type 2 MAC routes for VNI 50100 are received and installed only by intended tenant members.
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 leaf has a BGP EVPN session in Established but no MAC reachability for VNI 50100 while other VNIs work. The required targeted change is: Verify the VNI's route-target import/export and Type 2 route visibility across the EVPN peers.
Verify the supported EVPN IP-prefix route model, including Type 5 where required by the design. This is a valid solution to a different Junos 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 does not directly correct the specific failure evidence here: A fabric leaf has a BGP EVPN session in Established but no MAC reachability for VNI 50100 while other VNIs work. The required targeted change is: Verify the VNI's route-target import/export and Type 2 route visibility across the EVPN peers.
Inspect new Type 2 MAC advertisement and MAC mobility sequence handling after the move. This is a valid solution to a different Junos situation: A virtual machine moves to a different EVPN leaf, yet remote leaves continue using the stale previous VTEP for its MAC. It does not directly correct the specific failure evidence here: A fabric leaf has a BGP EVPN session in Established but no MAC reachability for VNI 50100 while other VNIs work. The required targeted change is: Verify the VNI's route-target import/export and Type 2 route visibility across the EVPN peers.
A fabric leaf has a BGP EVPN session in Established but no MAC reachability for VNI 50100 while other VNIs work. The proposed correction is: Verify the VNI's route-target import/export and Type 2 route visibility across the EVPN peers. Which observation MOST directly confirms this fault is resolved?
Type 2 MAC routes for VNI 50100 are received and installed only by intended tenant members. This is the direct acceptance evidence for the observed failure: A fabric leaf has a BGP EVPN session in Established but no MAC reachability for VNI 50100 while other VNIs work. The mechanism being validated is: EVPN route targets constrain which tenant reachability a participating leaf imports.
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: Type 2 MAC routes for VNI 50100 are received and installed only by intended tenant members.
The remote tenant VRF receives the appropriate IP prefix with valid overlay next-hop resolution. That would validate a different condition: 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 decisive check for the current issue is: Type 2 MAC routes for VNI 50100 are received and installed only by intended tenant members.
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: Type 2 MAC routes for VNI 50100 are received and installed only by intended tenant members.
Please check your mailbox for a message from support@examlabs.com and follow the directions.