How does a VTEP register MAC address information in a BGP EVPN-based VXLAN?

By updating the DNS server with the MAC address.

By sending a MAC registration message to a central controller.

By sending an EVPN route type 2 (MAC/IP Advertisement) route via BGP.

By flooding the MAC address in the overlay network.

A data center is running a multicast-based VXLAN fabric. The operations team is experiencing high CPU utilization on the spine switches during BUM traffic storms. The fabric has 100 VTEPs and 50 VNIs. Which design change would most effectively reduce the BUM replication load on the spine switches?

Increase the number of multicast groups per VNI

Migrate to BGP EVPN with ingress replication

Configure static VXLAN tunnels for BUM traffic

Use a single multicast group for all VNIs

A network engineer is configuring a new leaf switch in a BGP EVPN VXLAN fabric. The engineer has configured the VXLAN interface and the EVPN address family on the IBGP session. However, the leaf is not receiving any EVPN routes from the spine. What is the most likely cause?

The leaf is using OSPF instead of IS-IS for the underlay

The leaf is not configured with a loopback interface

The BGP session is not configured with the correct route distinguisher (RD) and route target (RT)

The spine is not configured with VXLAN

A network engineer is adding a new host to a VXLAN EVPN fabric. The host sends its first frame, and the local leaf learns the MAC address. What happens next in the control plane to make this MAC reachable from remote VTEPs?

The leaf generates a Type 2 route and advertises it via BGP EVPN

The leaf sends a multicast join to the VNI's multicast group

The leaf waits for a Type 3 route from the remote VTEP

The leaf sends an ARP request to the remote VTEPs

In a BGP EVPN-based VXLAN, when is a VXLAN tunnel established between two VTEPs?

When the administrator manually configures the tunnel on both VTEPs.

When the underlay network is configured with a multicast group.

When the first data packet is sent between the VTEPs.

When the VTEPs receive EVPN routes from each other that indicate they share a VXLAN segment.

Juniper NetworksCertified Professional, Data Center (JNCIP-DC)

Domain 3Objective 1

VXLAN Control Planes JN0-683 Practice Questions (Page 4)

Part of the VXLAN domain, which makes up ~8% of our current practice bank. Juniper Networks does not publish an official question count, but from its 90-minute exam (~35–60 total, ~3–5 in this domain), expect 1–2 from this objective — we provide 26 practice questions to prepare you well beyond it. (estimate)

26questions here

6free pages

7concepts

Questions 16–20

16foundation · easy
How does a VTEP register MAC address information in a BGP EVPN-based VXLAN?
Select an answer first
17expert · hard
A data center is running a multicast-based VXLAN fabric. The operations team is experiencing high CPU utilization on the spine switches during BUM traffic storms. The fabric has 100 VTEPs and 50 VNIs. Which design change would most effectively reduce the BUM replication load on the spine switches?
Select an answer first
18application · medium
A network engineer is configuring a new leaf switch in a BGP EVPN VXLAN fabric. The engineer has configured the VXLAN interface and the EVPN address family on the IBGP session. However, the leaf is not receiving any EVPN routes from the spine. What is the most likely cause?
Select an answer first
19application · medium
A network engineer is adding a new host to a VXLAN EVPN fabric. The host sends its first frame, and the local leaf learns the MAC address. What happens next in the control plane to make this MAC reachable from remote VTEPs?
Select an answer first
20foundation · easy
In a BGP EVPN-based VXLAN, when is a VXLAN tunnel established between two VTEPs?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to JN0-683

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Juniper Networks. “JN0-683” is a trademark of its owner, used for identification only.