JN0-650 Premium File
- 107 Questions & Answers
- Last Update: Nov 8, 2026
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. If the team bypasses or fails to implement the targeted correction (Restore authorized VXLAN UDP transport and IP reachability between the participating VTEP endpoints.), which direct operational risk or residual exposure is MOST relevant?
An established control-plane session cannot compensate for a blocked VXLAN data path. This is the consequence linked to the observed 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 is prevented by: Restore authorized VXLAN UDP transport and IP reachability between the participating VTEP endpoints. The underlying reason is: EVPN BGP advertises reachability while VXLAN encapsulation carries actual Ethernet frames over IP.
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: An established control-plane session cannot compensate for a blocked VXLAN data path. The appropriate mitigation is: Restore authorized VXLAN UDP transport and IP reachability between the participating VTEP endpoints.
Stale endpoint location information can blackhole traffic after a server migration. This risk belongs to a different operational problem: A virtual machine moves to a different EVPN leaf, yet remote leaves continue using the stale previous VTEP for its MAC. The stated condition instead exposes this direct risk: An established control-plane session cannot compensate for a blocked VXLAN data path. The appropriate mitigation is: Restore authorized VXLAN UDP transport and IP reachability between the participating VTEP endpoints.
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: An established control-plane session cannot compensate for a blocked VXLAN data path. The appropriate mitigation is: Restore authorized VXLAN UDP transport and IP reachability between the participating VTEP endpoints.
An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. Which targeted engineering change is MOST directly justified by the observed evidence?
Engineer end-to-end underlay MTU headroom for the supported VXLAN packet size. This change specifically addresses the reported evidence: An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. The relevant protocol mechanism is: VXLAN adds transport encapsulation overhead beyond the original Ethernet payload. A decisive acceptance test would be: Encapsulated tenant test packets traverse the underlay without fragmentation or MTU drops.
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: An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. The required targeted change is: Engineer end-to-end underlay MTU headroom for the supported VXLAN packet size.
Map each tenant broadcast domain to distinct VNIs and matching EVPN route-target membership. This is a valid solution to a different Junos situation: Two tenants share the same physical VXLAN underlay but their Layer 2 broadcasts must remain separate despite overlapping inner VLAN numbers. It does not directly correct the specific failure evidence here: An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. The required targeted change is: Engineer end-to-end underlay MTU headroom for the supported VXLAN packet size.
Correct designated-forwarder election and non-DF egress suppression for that Ethernet segment and VLAN. This is a valid solution to a different Junos situation: A dual-homed customer edge receives duplicate broadcast frames when both active PEs forward remote BUM traffic toward the same segment. It does not directly correct the specific failure evidence here: An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. The required targeted change is: Engineer end-to-end underlay MTU headroom for the supported VXLAN packet size.
An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. The proposed correction is: Engineer end-to-end underlay MTU headroom for the supported VXLAN packet size. Which observation MOST directly confirms this fault is resolved?
Encapsulated tenant test packets traverse the underlay without fragmentation or MTU drops. This is the direct acceptance evidence for the observed failure: An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. The mechanism being validated is: VXLAN adds transport encapsulation overhead beyond the original Ethernet payload.
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: Encapsulated tenant test packets traverse the underlay without fragmentation or MTU drops.
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: Encapsulated tenant test packets traverse the underlay without fragmentation or MTU drops.
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: Encapsulated tenant test packets traverse the underlay without fragmentation or MTU drops.
A Junos engineer proposes this response: Engineer end-to-end underlay MTU headroom for the supported VXLAN packet size. The situation is: An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. Which technical principle BEST justifies the response?
VXLAN adds transport encapsulation overhead beyond the original Ethernet payload. This is the controlling mechanism in the specific case: An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. It predicts the acceptance result: Encapsulated tenant test packets traverse the underlay without fragmentation or MTU drops.
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: VXLAN adds transport encapsulation overhead beyond the original Ethernet payload.
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: VXLAN adds transport encapsulation overhead beyond the original Ethernet payload.
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: VXLAN adds transport encapsulation overhead beyond the original Ethernet payload.
An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. If the team bypasses or fails to implement the targeted correction (Engineer end-to-end underlay MTU headroom for the supported VXLAN packet size.), which direct operational risk or residual exposure is MOST relevant?
An underlay sized only for bare tenant frames can drop oversized encapsulated traffic. This is the consequence linked to the observed situation: An EVPN leaf sends large encapsulated tenant frames but the underlay MTU is too small for the extra VXLAN/IP/UDP headers. It is prevented by: Engineer end-to-end underlay MTU headroom for the supported VXLAN packet size. The underlying reason is: VXLAN adds transport encapsulation overhead beyond the original Ethernet payload.
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: An underlay sized only for bare tenant frames can drop oversized encapsulated traffic. The appropriate mitigation is: Engineer end-to-end underlay MTU headroom for the supported VXLAN packet size.
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: An underlay sized only for bare tenant frames can drop oversized encapsulated traffic. The appropriate mitigation is: Engineer end-to-end underlay MTU headroom for the supported VXLAN packet size.
If both multihomed PEs forward the same remote BUM packets, customer-side loops or duplicates can occur. This risk belongs to a different operational problem: A dual-homed customer edge receives duplicate broadcast frames when both active PEs forward remote BUM traffic toward the same segment. The stated condition instead exposes this direct risk: An underlay sized only for bare tenant frames can drop oversized encapsulated traffic. The appropriate mitigation is: Engineer end-to-end underlay MTU headroom for the supported VXLAN packet size.
A virtual machine moves to a different EVPN leaf, yet remote leaves continue using the stale previous VTEP for its MAC. Which targeted engineering change is MOST directly justified by the observed evidence?
Inspect new Type 2 MAC advertisement and MAC mobility sequence handling after the move. This change specifically addresses the reported evidence: A virtual machine moves to a different EVPN leaf, yet remote leaves continue using the stale previous VTEP for its MAC. The relevant protocol mechanism is: EVPN MAC mobility mechanisms coordinate changed endpoint attachment locations. A decisive acceptance test would be: Remote leaves update the MAC-to-VTEP mapping and forwarding reaches the VM's new location.
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 virtual machine moves to a different EVPN leaf, yet remote leaves continue using the stale previous VTEP for its MAC. The required targeted change is: Inspect new Type 2 MAC advertisement and MAC mobility sequence handling after the move.
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 virtual machine moves to a different EVPN leaf, yet remote leaves continue using the stale previous VTEP for its MAC. The required targeted change is: Inspect new Type 2 MAC advertisement and MAC mobility sequence handling after the move.
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 virtual machine moves to a different EVPN leaf, yet remote leaves continue using the stale previous VTEP for its MAC. The required targeted change is: Inspect new Type 2 MAC advertisement and MAC mobility sequence handling after the move.
A virtual machine moves to a different EVPN leaf, yet remote leaves continue using the stale previous VTEP for its MAC. The proposed correction is: Inspect new Type 2 MAC advertisement and MAC mobility sequence handling after the move. Which observation MOST directly confirms this fault is resolved?
Remote leaves update the MAC-to-VTEP mapping and forwarding reaches the VM's new location. This is the direct acceptance evidence for the observed failure: A virtual machine moves to a different EVPN leaf, yet remote leaves continue using the stale previous VTEP for its MAC. The mechanism being validated is: EVPN MAC mobility mechanisms coordinate changed endpoint attachment locations.
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: Remote leaves update the MAC-to-VTEP mapping and forwarding reaches the VM's new location.
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: Remote leaves update the MAC-to-VTEP mapping and forwarding reaches the VM's new location.
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: Remote leaves update the MAC-to-VTEP mapping and forwarding reaches the VM's new location.
A Junos engineer proposes this response: Inspect new Type 2 MAC advertisement and MAC mobility sequence handling after the move. The situation is: A virtual machine moves to a different EVPN leaf, yet remote leaves continue using the stale previous VTEP for its MAC. Which technical principle BEST justifies the response?
EVPN MAC mobility mechanisms coordinate changed endpoint attachment locations. This is the controlling mechanism in the specific case: A virtual machine moves to a different EVPN leaf, yet remote leaves continue using the stale previous VTEP for its MAC. It predicts the acceptance result: Remote leaves update the MAC-to-VTEP mapping and forwarding reaches the VM's new location.
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 MAC mobility mechanisms coordinate changed endpoint attachment locations.
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 MAC mobility mechanisms coordinate changed endpoint attachment locations.
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 MAC mobility mechanisms coordinate changed endpoint attachment locations.
A virtual machine moves to a different EVPN leaf, yet remote leaves continue using the stale previous VTEP for its MAC. If the team bypasses or fails to implement the targeted correction (Inspect new Type 2 MAC advertisement and MAC mobility sequence handling after the move.), which direct operational risk or residual exposure is MOST relevant?
Stale endpoint location information can blackhole traffic after a server migration. This is the consequence linked to the observed situation: A virtual machine moves to a different EVPN leaf, yet remote leaves continue using the stale previous VTEP for its MAC. It is prevented by: Inspect new Type 2 MAC advertisement and MAC mobility sequence handling after the move. The underlying reason is: EVPN MAC mobility mechanisms coordinate changed endpoint attachment locations.
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: Stale endpoint location information can blackhole traffic after a server migration. The appropriate mitigation is: Inspect new Type 2 MAC advertisement and MAC mobility sequence handling after the move.
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: Stale endpoint location information can blackhole traffic after a server migration. The appropriate mitigation is: Inspect new Type 2 MAC advertisement and MAC mobility sequence handling after the move.
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: Stale endpoint location information can blackhole traffic after a server migration. The appropriate mitigation is: Inspect new Type 2 MAC advertisement and MAC mobility sequence handling after the move.
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 targeted engineering change is MOST directly justified by the observed evidence?
Align supported ESI and multihoming configuration on both PEs and validate the CE bundle mode. This change specifically addresses the reported evidence: 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 relevant protocol mechanism is: Active-active EVPN multihoming requires participating PEs to identify the same Ethernet segment. A decisive acceptance test would be: Both PEs advertise the same intended Ethernet segment identity and load sharing follows design.
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: 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 required targeted change is: Align supported ESI and multihoming configuration on both PEs and validate the CE bundle mode.
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 multihoming pair wants active-active delivery for a dual-attached CE, but only one PE is eligible because the Ethernet segment identity differs. The required targeted change is: Align supported ESI and multihoming configuration on both PEs and validate the CE bundle mode.
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: 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 required targeted change is: Align supported ESI and multihoming configuration on both PEs and validate the CE bundle mode.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.