Q: 9
Which component is part of the Cisco SD-Access overlay architecture?
Options
Discussion
Option D Cisco DNA Center is the overlay controller piece here. Seen that in official guides and labs.
Not B, it's D. DNA Center does the real overlay orchestration and policy stuff in SD-Access, it's not just about who forwards VXLAN. Pretty sure that's what Cisco wants here, even if it's a bit confusing.
B , I figured spine node since it handles VXLAN traffic in the overlay. Maybe that's a trick though, since sometimes "component" means controller too, but on tech diagrams spines look core to the overlay piece.
C or D here. DNA Center (D) is usually seen as the brains of the overlay, handling automation and policy, but sometimes Cisco test questions blur that with network nodes like border or spine (C/B). I think D fits best if they're focusing on overlay architecture from a management perspective, but not 100% sure. Anyone pick C for a reason?
D
D, DNA Center is the overlay controller, not underlay hardware like border/spine/leaf. Pretty sure that's what Cisco asks for.
D , Cisco DNA Center is part of the overlay and manages policy/automation. Border, spine, and leaf nodes are underlay components in SD-Access. Seen similar wording in practice, open to other views if I missed something.
Its B. Had something like this in a mock and pretty sure the overlay uses spine/leaf too.
D makes sense since DNA Center orchestrates the SD-Access overlay and manages control/policy planes, not just forwarding traffic. The overlays in Cisco docs always include DNA Center as a core component, pretty sure that's what they're after here. Anyone disagree?
Are they considering DNA Center (D) as part of the overlay itself, not just as a controller? Usually, overlay architecture points to devices handling actual VXLAN traffic, like spines or borders. Not fully clear from the wording.
Be respectful. No spam.
