Free Juniper JN0-683 Actual Exam Questions - Question 10 Discussion

Question No. 10
Which statement is correct about a collapsed fabric EVPN-VXLAN architecture?
Select one option, then reveal solution.
US
SW
Shoaib W.
2026-02-16

I’m not sure about B because if the fabric is collapsed, wouldn't having multiple vendors complicate the uniform VXLAN encapsulation? Also, A feels off since collapsed fabrics usually avoid complex spine meshing.

0
YY
Yasir Y.
2026-01-31

B. The question mentions a collapsed fabric EVPN-VXLAN setup, which typically means using identical devices for simplification. Saying it supports multiple vendors as long as the spines are all Juniper L2 VTEPs sounds off because mixing vendors usually complicates the fabric consistency and interoperability. So, B feels less likely. Also, fully meshed spine links (A) aren’t strictly needed if the fabric is collapsed and simplified. Virtual Chassis at leaf (C) is about resiliency but not a defining feature of collapsed EVPN-VXLAN fabrics. D fits best with standard border leaf duties.

0
AN
Andre N.
2026-01-26

Makes sense to go with D since border leafs generally do the routing to outside networks. A full mesh between spines isn’t really a must-have in this setup. D

0
AN
Andre N.
2026-01-23

I’m with D too. Border leaves typically handle routing to external networks, so that fits the standard role in collapsed EVPN-VXLAN fabrics better than options about spine mesh or virtual chassis. D

0
IY
Irfan Y.
2026-01-21

I think D is the better pick here. In collapsed fabrics, border leafs usually handle the gateway functions for routing outside the fabric, so it fits well. A full mesh between spines (A) doesn’t seem necessary in this design since spines might also act as leaves, which changes the traditional layout. B sounds off because vendor lock-in isn’t a given, and C’s virtual chassis at leaf layer might help resiliency but isn’t a defining trait of collapsed fabric EVPN-VXLAN. So D’s role for border gateway functions on border leaf devices feels most accurate to me.

0
NL
Noah L.
2026-01-16

Maybe D makes sense since border leafs usually handle border gateway roles to connect external networks. That fits typical EVPN-VXLAN designs better than full mesh spines or vendor-specific rules.

0
NL
Noah L.
2026-01-15

A/C? The question about spine links or leaf virtual chassis isn't clear enough for me. The explanation I found didn’t cover how spine switches connect in a collapsed fabric-do they need a full mesh always? And about virtual chassis on leafs, does that really boost resiliency or just adds complexity? Would help if someone could break down why one is clearly right and the others aren’t.

0