nerdexam
Cisco

300-420 · Question #129

How is redundancy achieved among Cisco vBond Orchestrators in a Cisco SD-WAN deployment?

The correct answer is A. The IP addresses of all Orchestrators are mapped to a single DNS name. In Cisco SD-WAN, the vBond orchestrator is the first point of contact for WAN Edge routers during onboarding - it authenticates devices and helps them discover vSmart controllers and vManage. To achieve redundancy, multiple vBond orchestrators are deployed and all of their IP…

WAN for Enterprise Networks

Question

How is redundancy achieved among Cisco vBond Orchestrators in a Cisco SD-WAN deployment?

Options

  • AThe IP addresses of all Orchestrators are mapped to a single DNS name.
  • BThe closest Orchestrator to each Cisco WAN Edge router is selected.
  • CCisco WAN Edge routers are configured with all Orchestrators using their IP addresses and
  • DA single Cisco Orchestrator is deployed in each network.

How the community answered

(18 responses)
  • A
    94% (17)
  • B
    6% (1)

Explanation

In Cisco SD-WAN, the vBond orchestrator is the first point of contact for WAN Edge routers during onboarding - it authenticates devices and helps them discover vSmart controllers and vManage. To achieve redundancy, multiple vBond orchestrators are deployed and all of their IP addresses are mapped to a single DNS name (e.g., vbond.company.com). WAN Edge routers are configured with this DNS name; when they resolve it, they receive all vBond IP addresses and can try each one, providing failover. Option B is incorrect because vBond selection is not based on geographic proximity. Option C is partially true in lab scenarios but not the recommended production design for redundancy. Option D (single orchestrator per network) provides no redundancy.

Topics

#SD-WAN#vBond Orchestrator#Redundancy#DNS

Community Discussion

No community discussion yet for this question.

Full 300-420 Practice