How Many vBond Controllers Are Needed for Four SD-WAN Tenants?

Why the Answer Is Correct

In Cisco SD-WAN multitenancy, the service provider hosts multiple tenants on vManage, but the vBond orchestrator is a shared control-plane component that authenticates and orchestrates WAN edge devices across all tenants. The vBond does not need to be duplicated per tenant; it serves as the common rendezvous point for every overlay device added to the network. Therefore, whether the provider has one tenant or four tenants, a single shared vBond controller is sufficient for the multitenancy deployment. As abvga noted, "vBond Orchestrators serve WAN edge devices of multiple tenants" as devices are added to the overlay.

Why the Other Options Are Wrong

Option B is incorrect because Cisco SD-WAN does not require exactly three vBond controllers in a multitenancy deployment; the number of vBonds is not tied to the tenant count. Option C is wrong because per-tenant vBond redundancy is not a multitenancy sizing rule, and two vBonds per tenant would unnecessarily multiply the orchestrator layer. Option D is the most tempting distractor because it applies per-tenant isolation to the wrong component: while vManage and vSmart resources are partitioned by tenant, the vBond remains shared. No Cisco SD-WAN multitenancy design calls for a dedicated vBond for each tenant.

Community Comment Notes

All visible learner votes selected option A, which matches the official architecture. Knowledge33 cited Cisco documentation stating that a "service provider can manage multiple customers, called tenants, from Cisco vManage," reinforcing that vManage is the tenant-aware component, not vBond. Outlaw_87 also chose A, and the unanimous community pick reflects the shared-vBond design principle tested here.