300-415 · Question #351
What is a requirement for deployment of on-premises vBond controllers through the Cisco Plug and Play Connect process?
The correct answer is B. a DNS name that identifies vBond. When deploying on-premises vBond controllers via Cisco Plug and Play Connect, a DNS name that resolves to the vBond address is required so that WAN Edge devices can automatically discover the controller.
Question
Options
- Aa defined controller profile
- Ba DNS name that identifies vBond
- CInternet connectivity from vManage
- Da CSV file that contains all controllers
How the community answered
(36 responses)- A3% (1)
- B92% (33)
- D6% (2)
Why each option
When deploying on-premises vBond controllers via Cisco Plug and Play Connect, a DNS name that resolves to the vBond address is required so that WAN Edge devices can automatically discover the controller.
A controller profile is associated with vManage cloud-based deployment, not a specific requirement for PnP Connect for on-premises vBond deployment.
Cisco PnP Connect uses a DNS name to identify the vBond orchestrator, which is the entry point for WAN Edge devices during zero-touch provisioning. Without a resolvable DNS name for vBond, edge devices cannot automatically discover and connect to the controller during the onboarding process.
Internet connectivity from vManage is a general networking requirement, not the specific PnP Connect requirement for deploying on-premises vBond controllers.
A CSV file is used for bulk device onboarding in vManage, not a PnP Connect requirement for deploying on-premises vBond controllers.
Concept tested: On-premises vBond Plug and Play Connect DNS requirement
Source: https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/sdwan-xe-gs-book/cisco-sd-wan-overlay-network-bringup.html
Topics
Community Discussion
No community discussion yet for this question.