Pass Juniper JN0-650 Exam in First Attempt Easily
Real Juniper JN0-650 Exam Questions, Accurate & Verified Answers As Experienced in the Actual Test!

Verified by experts

JN0-650 Premium File

  • 107 Questions & Answers
  • Last Update: Nov 8, 2026
$69.99 $76.99

Enterprise Routing and Switching, Professional (JNCIP-ENT) JN0-650 Practice Test 66

Question 650

Two EVPN fabric leaves share a broadcast domain, but unknown-unicast and broadcast packets do not reach remote VTEPs. The proposed correction is: Check Type 3 inclusive-multicast EVPN routes and the configured BUM delivery method for that VNI. Which observation MOST directly confirms this fault is resolved?

  1. Traffic reaches only VTEPs participating in the appropriate tenant VNI.
  2. Type 2 entries identify the host next hop while Type 3 supports BUM delivery.
  3. Only the elected DF delivers remote BUM frames to the customer segment for the affected VLAN.
  4. The intended remote VTEPs appear in the VNI's BUM replication or multicast distribution state.

Explanation

Correct Answer

D:

The intended remote VTEPs appear in the VNI's BUM replication or multicast distribution state. This is the direct acceptance evidence for the observed failure: Two EVPN fabric leaves share a broadcast domain, but unknown-unicast and broadcast packets do not reach remote VTEPs. The mechanism being validated is: EVPN Type 3 routes signal inclusive multicast membership for broadcast, unknown unicast, and multicast delivery.

Incorrect Answers

A:

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: The intended remote VTEPs appear in the VNI's BUM replication or multicast distribution state.

B:

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 intended remote VTEPs appear in the VNI's BUM replication or multicast distribution state.

C:

Only the elected DF delivers remote BUM frames to the customer segment for the affected VLAN. That would validate a different condition: A dual-homed customer edge receives duplicate broadcast frames when both active PEs forward remote BUM traffic toward the same segment. The decisive check for the current issue is: The intended remote VTEPs appear in the VNI's BUM replication or multicast distribution state.

Question 651

A Junos engineer proposes this response: Check Type 3 inclusive-multicast EVPN routes and the configured BUM delivery method for that VNI. The situation is: Two EVPN fabric leaves share a broadcast domain, but unknown-unicast and broadcast packets do not reach remote VTEPs. Which technical principle BEST justifies the response?

  1. EVPN Type 3 routes signal inclusive multicast membership for broadcast, unknown unicast, and multicast delivery.
  2. VXLAN VNIs identify isolated logical overlay segments over a shared routed underlay.
  3. EVPN Type 2 and Type 3 signal different reachability functions and are not interchangeable.
  4. EVPN DF election limits downstream BUM forwarding to avoid loops on multihomed segments.

Explanation

Correct Answer

A:

EVPN Type 3 routes signal inclusive multicast membership for broadcast, unknown unicast, and multicast delivery. This is the controlling mechanism in the specific case: Two EVPN fabric leaves share a broadcast domain, but unknown-unicast and broadcast packets do not reach remote VTEPs. It predicts the acceptance result: The intended remote VTEPs appear in the VNI's BUM replication or multicast distribution state.

Incorrect Answers

B:

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 Type 3 routes signal inclusive multicast membership for broadcast, unknown unicast, and multicast delivery.

C:

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 3 routes signal inclusive multicast membership for broadcast, unknown unicast, and multicast delivery.

D:

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 Type 3 routes signal inclusive multicast membership for broadcast, unknown unicast, and multicast delivery.

Question 652

Two EVPN fabric leaves share a broadcast domain, but unknown-unicast and broadcast packets do not reach remote VTEPs. If the team bypasses or fails to implement the targeted correction (Check Type 3 inclusive-multicast EVPN routes and the configured BUM delivery method for that VNI.), which direct operational risk or residual exposure is MOST relevant?

  1. Reusing a tenant VNI inadvertently can merge unrelated broadcast domains.
  2. Missing Type 3 membership can blackhole broadcast and discovery traffic across the VXLAN overlay.
  3. Using only Type 3 membership cannot provide specific remote unicast MAC location information.
  4. If both multihomed PEs forward the same remote BUM packets, customer-side loops or duplicates can occur.

Explanation

Correct Answer

B:

Missing Type 3 membership can blackhole broadcast and discovery traffic across the VXLAN overlay. This is the consequence linked to the observed situation: Two EVPN fabric leaves share a broadcast domain, but unknown-unicast and broadcast packets do not reach remote VTEPs. It is prevented by: Check Type 3 inclusive-multicast EVPN routes and the configured BUM delivery method for that VNI. The underlying reason is: EVPN Type 3 routes signal inclusive multicast membership for broadcast, unknown unicast, and multicast delivery.

Incorrect Answers

A:

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: Missing Type 3 membership can blackhole broadcast and discovery traffic across the VXLAN overlay. The appropriate mitigation is: Check Type 3 inclusive-multicast EVPN routes and the configured BUM delivery method for that VNI.

C:

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: Missing Type 3 membership can blackhole broadcast and discovery traffic across the VXLAN overlay. The appropriate mitigation is: Check Type 3 inclusive-multicast EVPN routes and the configured BUM delivery method for that VNI.

D:

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: Missing Type 3 membership can blackhole broadcast and discovery traffic across the VXLAN overlay. The appropriate mitigation is: Check Type 3 inclusive-multicast EVPN routes and the configured BUM delivery method for that VNI.

Question 653

A multihomed customer edge loses a PE uplink, yet remote ingress PEs keep forwarding toward withdrawn Ethernet segment reachability. Which targeted engineering change is MOST directly justified by the observed evidence?

  1. Correct designated-forwarder election and non-DF egress suppression for that Ethernet segment and VLAN.
  2. Align supported ESI and multihoming configuration on both PEs and validate the CE bundle mode.
  3. Verify the VNI's route-target import/export and Type 2 route visibility across the EVPN peers.
  4. Verify EVPN Type 1 Ethernet autodiscovery withdrawal and affected aliasing or mass-withdraw convergence.

Explanation

Correct Answer

D:

Verify EVPN Type 1 Ethernet autodiscovery withdrawal and affected aliasing or mass-withdraw convergence. This change specifically addresses the reported evidence: A multihomed customer edge loses a PE uplink, yet remote ingress PEs keep forwarding toward withdrawn Ethernet segment reachability. The relevant protocol mechanism is: EVPN Type 1 Ethernet autodiscovery supports multihoming convergence and Ethernet segment reachability withdrawal. A decisive acceptance test would be: Remote PEs withdraw or reroute dependent MAC reachability promptly after the segment fails.

Incorrect Answers

A:

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: A multihomed customer edge loses a PE uplink, yet remote ingress PEs keep forwarding toward withdrawn Ethernet segment reachability. The required targeted change is: Verify EVPN Type 1 Ethernet autodiscovery withdrawal and affected aliasing or mass-withdraw convergence.

B:

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 multihomed customer edge loses a PE uplink, yet remote ingress PEs keep forwarding toward withdrawn Ethernet segment reachability. The required targeted change is: Verify EVPN Type 1 Ethernet autodiscovery withdrawal and affected aliasing or mass-withdraw convergence.

C:

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 multihomed customer edge loses a PE uplink, yet remote ingress PEs keep forwarding toward withdrawn Ethernet segment reachability. The required targeted change is: Verify EVPN Type 1 Ethernet autodiscovery withdrawal and affected aliasing or mass-withdraw convergence.

Question 654

A multihomed customer edge loses a PE uplink, yet remote ingress PEs keep forwarding toward withdrawn Ethernet segment reachability. The proposed correction is: Verify EVPN Type 1 Ethernet autodiscovery withdrawal and affected aliasing or mass-withdraw convergence. Which observation MOST directly confirms this fault is resolved?

  1. Remote PEs withdraw or reroute dependent MAC reachability promptly after the segment fails.
  2. The two PEs recognize the shared ESI and participate in the intended DF election.
  3. Frames received from a multihomed segment are not forwarded back toward that same Ethernet segment.
  4. The remote tenant VRF receives the appropriate IP prefix with valid overlay next-hop resolution.

Explanation

Correct Answer

A:

Remote PEs withdraw or reroute dependent MAC reachability promptly after the segment fails. This is the direct acceptance evidence for the observed failure: A multihomed customer edge loses a PE uplink, yet remote ingress PEs keep forwarding toward withdrawn Ethernet segment reachability. The mechanism being validated is: EVPN Type 1 Ethernet autodiscovery supports multihoming convergence and Ethernet segment reachability withdrawal.

Incorrect Answers

B:

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: Remote PEs withdraw or reroute dependent MAC reachability promptly after the segment fails.

C:

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: Remote PEs withdraw or reroute dependent MAC reachability promptly after the segment fails.

D:

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: Remote PEs withdraw or reroute dependent MAC reachability promptly after the segment fails.

Question 655

A Junos engineer proposes this response: Verify EVPN Type 1 Ethernet autodiscovery withdrawal and affected aliasing or mass-withdraw convergence. The situation is: A multihomed customer edge loses a PE uplink, yet remote ingress PEs keep forwarding toward withdrawn Ethernet segment reachability. Which technical principle BEST justifies the response?

  1. EVPN DF election limits downstream BUM forwarding to avoid loops on multihomed segments.
  2. EVPN Type 1 Ethernet autodiscovery supports multihoming convergence and Ethernet segment reachability withdrawal.
  3. Active-active EVPN multihoming requires participating PEs to identify the same Ethernet segment.
  4. EVPN route targets constrain which tenant reachability a participating leaf imports.

Explanation

Correct Answer

B:

EVPN Type 1 Ethernet autodiscovery supports multihoming convergence and Ethernet segment reachability withdrawal. This is the controlling mechanism in the specific case: A multihomed customer edge loses a PE uplink, yet remote ingress PEs keep forwarding toward withdrawn Ethernet segment reachability. It predicts the acceptance result: Remote PEs withdraw or reroute dependent MAC reachability promptly after the segment fails.

Incorrect Answers

A:

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 Type 1 Ethernet autodiscovery supports multihoming convergence and Ethernet segment reachability withdrawal.

C:

Active-active EVPN multihoming requires participating PEs to identify the same Ethernet segment. This principle explains a separate 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. For this issue the relevant mechanism is: EVPN Type 1 Ethernet autodiscovery supports multihoming convergence and Ethernet segment reachability withdrawal.

D:

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: EVPN Type 1 Ethernet autodiscovery supports multihoming convergence and Ethernet segment reachability withdrawal.

Question 656

A multihomed customer edge loses a PE uplink, yet remote ingress PEs keep forwarding toward withdrawn Ethernet segment reachability. If the team bypasses or fails to implement the targeted correction (Verify EVPN Type 1 Ethernet autodiscovery withdrawal and affected aliasing or mass-withdraw convergence.), which direct operational risk or residual exposure is MOST relevant?

  1. Missing segment discovery can create inconsistent designated-forwarder decisions for BUM delivery.
  2. Ignoring ESI split-horizon state can create loops even when remote MAC learning works.
  3. Ignoring Type 1 withdrawal can prolong traffic blackholing after a multihomed attachment fails.
  4. Expecting MAC-only routes to replace required tenant IP prefix exchange can break routed overlay traffic.

Explanation

Correct Answer

C:

Ignoring Type 1 withdrawal can prolong traffic blackholing after a multihomed attachment fails. This is the consequence linked to the observed situation: A multihomed customer edge loses a PE uplink, yet remote ingress PEs keep forwarding toward withdrawn Ethernet segment reachability. It is prevented by: Verify EVPN Type 1 Ethernet autodiscovery withdrawal and affected aliasing or mass-withdraw convergence. The underlying reason is: EVPN Type 1 Ethernet autodiscovery supports multihoming convergence and Ethernet segment reachability withdrawal.

Incorrect Answers

A:

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 Type 1 withdrawal can prolong traffic blackholing after a multihomed attachment fails. The appropriate mitigation is: Verify EVPN Type 1 Ethernet autodiscovery withdrawal and affected aliasing or mass-withdraw convergence.

B:

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: Ignoring Type 1 withdrawal can prolong traffic blackholing after a multihomed attachment fails. The appropriate mitigation is: Verify EVPN Type 1 Ethernet autodiscovery withdrawal and affected aliasing or mass-withdraw convergence.

D:

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 Type 1 withdrawal can prolong traffic blackholing after a multihomed attachment fails. The appropriate mitigation is: Verify EVPN Type 1 Ethernet autodiscovery withdrawal and affected aliasing or mass-withdraw convergence.

Question 657

Two provider edge switches attach the same customer Ethernet segment but do not discover each other for designated-forwarder coordination. Which targeted engineering change is MOST directly justified by the observed evidence?

  1. Verify their EVPN Type 4 Ethernet segment routes and consistent nonzero Ethernet segment identifier.
  2. Inspect EVPN ESI split-horizon filtering and associated multihoming route attributes.
  3. Confirm that host MAC/IP advertisements use Type 2 routes in addition to Type 3 BUM membership.
  4. Verify the VNI's route-target import/export and Type 2 route visibility across the EVPN peers.

Explanation

Correct Answer

A:

Verify their EVPN Type 4 Ethernet segment routes and consistent nonzero Ethernet segment identifier. This change specifically addresses the reported evidence: Two provider edge switches attach the same customer Ethernet segment but do not discover each other for designated-forwarder coordination. The relevant protocol mechanism is: EVPN Type 4 Ethernet segment routes support discovery among PEs attached to one multihomed segment. A decisive acceptance test would be: The two PEs recognize the shared ESI and participate in the intended DF election.

Incorrect Answers

B:

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: Two provider edge switches attach the same customer Ethernet segment but do not discover each other for designated-forwarder coordination. The required targeted change is: Verify their EVPN Type 4 Ethernet segment routes and consistent nonzero Ethernet segment identifier.

C:

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: Two provider edge switches attach the same customer Ethernet segment but do not discover each other for designated-forwarder coordination. The required targeted change is: Verify their EVPN Type 4 Ethernet segment routes and consistent nonzero Ethernet segment identifier.

D:

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: Two provider edge switches attach the same customer Ethernet segment but do not discover each other for designated-forwarder coordination. The required targeted change is: Verify their EVPN Type 4 Ethernet segment routes and consistent nonzero Ethernet segment identifier.

Question 658

Two provider edge switches attach the same customer Ethernet segment but do not discover each other for designated-forwarder coordination. The proposed correction is: Verify their EVPN Type 4 Ethernet segment routes and consistent nonzero Ethernet segment identifier. Which observation MOST directly confirms this fault is resolved?

  1. Remote PEs withdraw or reroute dependent MAC reachability promptly after the segment fails.
  2. The two PEs recognize the shared ESI and participate in the intended DF election.
  3. Frames received from a multihomed segment are not forwarded back toward that same Ethernet segment.
  4. The intended remote VTEPs appear in the VNI's BUM replication or multicast distribution state.

Explanation

Correct Answer

B:

The two PEs recognize the shared ESI and participate in the intended DF election. This is the direct acceptance evidence for the observed failure: Two provider edge switches attach the same customer Ethernet segment but do not discover each other for designated-forwarder coordination. The mechanism being validated is: EVPN Type 4 Ethernet segment routes support discovery among PEs attached to one multihomed segment.

Incorrect Answers

A:

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: The two PEs recognize the shared ESI and participate in the intended DF election.

C:

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: The two PEs recognize the shared ESI and participate in the intended DF election.

D:

The intended remote VTEPs appear in the VNI's BUM replication or multicast distribution state. That would validate a different condition: Two EVPN fabric leaves share a broadcast domain, but unknown-unicast and broadcast packets do not reach remote VTEPs. The decisive check for the current issue is: The two PEs recognize the shared ESI and participate in the intended DF election.

Question 659

A Junos engineer proposes this response: Verify their EVPN Type 4 Ethernet segment routes and consistent nonzero Ethernet segment identifier. The situation is: Two provider edge switches attach the same customer Ethernet segment but do not discover each other for designated-forwarder coordination. Which technical principle BEST justifies the response?

  1. EVPN DF election limits downstream BUM forwarding to avoid loops on multihomed segments.
  2. EVPN Type 2 and Type 3 signal different reachability functions and are not interchangeable.
  3. EVPN Type 4 Ethernet segment routes support discovery among PEs attached to one multihomed segment.
  4. EVPN route targets constrain which tenant reachability a participating leaf imports.

Explanation

Correct Answer

C:

EVPN Type 4 Ethernet segment routes support discovery among PEs attached to one multihomed segment. This is the controlling mechanism in the specific case: Two provider edge switches attach the same customer Ethernet segment but do not discover each other for designated-forwarder coordination. It predicts the acceptance result: The two PEs recognize the shared ESI and participate in the intended DF election.

Incorrect Answers

A:

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 Type 4 Ethernet segment routes support discovery among PEs attached to one multihomed segment.

B:

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 4 Ethernet segment routes support discovery among PEs attached to one multihomed segment.

D:

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: EVPN Type 4 Ethernet segment routes support discovery among PEs attached to one multihomed segment.

Question 660

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?

  1. Ignoring Type 1 withdrawal can prolong traffic blackholing after a multihomed attachment fails.
  2. Ignoring ESI split-horizon state can create loops even when remote MAC learning works.
  3. Missing Type 3 membership can blackhole broadcast and discovery traffic across the VXLAN overlay.
  4. Missing segment discovery can create inconsistent designated-forwarder decisions for BUM delivery.

Explanation

Correct Answer

D:

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.

Incorrect Answers

A:

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.

B:

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.

C:

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.

Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests

SPECIAL OFFER: GET 10% OFF
This is ONE TIME OFFER

You save
10%

Enter Your Email Address to Receive Your 10% Off Discount Code

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

Please check your mailbox for a message from support@examlabs.com and follow the directions.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your email address below to get started with our interactive software demo of your free trial.

  • Realistic exam simulation and exam editor with preview functions
  • Whole exam in a single file with several different question types
  • Customizable exam-taking mode & detailed score reports