A data center fabric is using eBGP as the underlay. A new leaf device has been added, and it can ping all spine devices, but it cannot establish BGP sessions with them. The engineer has verified that the BGP configuration on the new leaf is correct. What is the most likely cause of the issue?

The spine devices do not have the new leaf's IP address configured as a BGP neighbor.

The new leaf has a different AS number than the spines.

The new leaf's loopback IP is not reachable from the spines.

The new leaf's BGP export policy is not configured.

A data center fabric is experiencing intermittent connectivity issues between two servers in different racks. The underlay (OSPF) is fully converged, and all leaf and spine devices can ping each other. The engineer suspects a VXLAN tunnel issue. Which diagnostic step should the engineer take first to isolate the problem?

Check the underlay routing table for the loopback IPs of the remote leaf.

Check the EVPN route table on the leaf devices for the server IP routes.

Check the VXLAN tunnel endpoint (VTEP) status on both leaf devices.

Check the MAC address table on the leaf devices for the server MAC addresses.

When configuring an OSPF underlay in an IP fabric, what is the purpose of advertising loopback interfaces?

To provide a backup path for OSPF adjacencies in case of link failure

To allow OSPF to load-balance traffic across multiple equal-cost paths

To provide stable router IDs and reachable addresses for overlay protocols like BGP and VXLAN

To enable OSPF to calculate the shortest path to each server subnet

In an EVPN-VXLAN fabric, what is the role of the VXLAN Network Identifier (VNI)?

It identifies the overlay Layer 2 or Layer 3 segment

It identifies the underlay routing instance

It identifies the BGP peer group used for EVPN

It identifies the physical interface on the leaf device

What is the primary purpose of EVPN in an EVPN-VXLAN IP fabric?

To provide a routing protocol for the underlay network

To provide a backup path for VXLAN tunnels in case of failure

To encapsulate Layer 2 frames in UDP packets for transport over the IP fabric

To provide a control plane for MAC and IP address learning and distribution

Juniper NetworksCertified Professional, Data Center (JNCIP-DC)

Domain 2Objective 6

Configure, Monitor, or Troubleshoot an IP Fabric JN0-683 Practice Questions (Page 1)

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

16questions here

4free pages

5concepts

Questions 1–5

1expert · medium
A data center fabric is using eBGP as the underlay. A new leaf device has been added, and it can ping all spine devices, but it cannot establish BGP sessions with them. The engineer has verified that the BGP configuration on the new leaf is correct. What is the most likely cause of the issue?
Select an answer first
2expert · medium
A data center fabric is experiencing intermittent connectivity issues between two servers in different racks. The underlay (OSPF) is fully converged, and all leaf and spine devices can ping each other. The engineer suspects a VXLAN tunnel issue. Which diagnostic step should the engineer take first to isolate the problem?
Select an answer first
3foundation · easy
When configuring an OSPF underlay in an IP fabric, what is the purpose of advertising loopback interfaces?
Select an answer first
4foundation · easy
In an EVPN-VXLAN fabric, what is the role of the VXLAN Network Identifier (VNI)?
Select an answer first
5foundation · easy
What is the primary purpose of EVPN in an EVPN-VXLAN IP fabric?
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.