What Is Required for On-Premises vBond via PnP Connect?

Answer Correct answer: A — deploying on-premises vBond controllers through Cisco Plug and Play Connect requires a defined controller profile.

What is a requirement for deployment of on-premises vBond controllers through the Cisco Plug and Play Connect process?

a defined controller profile Correct Answer
a DNS name that identifies vBond
Internet connectivity from vManage
a CSV file that contains all controllers

vbond pnp connect requirement on-premises vbond deployment cisco plug and play connect controller profile sd-wan

Community Votes

50%

33%

17%

50% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

Tests the specific prerequisite for onboarding an on-premises vBond via PnP Connect; the trap is confusing general SD-WAN connectivity requirements with the PnP Connect controller profile requirement.

The Cisco Plug and Play Connect process for on-premises vBond controllers requires a defined controller profile in the PnP Connect portal. This page establishes that option A is correct, not the suggested Internet connectivity answer.

Many learners choose C (Internet connectivity from vManage) because vManage is central to SD-WAN management, but PnP Connect requires the vBond's controller profile, not vManage internet access.

Community Discussion (7 comments)

just_another_netguy 👍 1 Selected: A

Go with A > then the devices will be automatically associated with a default VBOND profile if existing in the account. https://www.cisco.com/c/dam/en_us/services/downloads/plug-play-connect.pdf B: vBond should also be fine with IP add only. C: Without Internet connectivity, you should also be fine with manual inputting required info into vManage. D: Don't think you need to do this for using PnP connect.

mikidvd51 👍 1 Selected: B

B: DNS name that identifies vBond 390 question - How is vBond reachability resolved by vManage? answer: DNS

mikidvd51 👍 1

right on next question is : How is vBond reachability resolved by vManage? and correct answer is - DNS

Rcont 👍 1 Selected: C

internet connectivity.

hamidreza0010 👍 1 Selected: B

B is the correct answer

iking 👍 2 Selected: C

C. Internet connectivity from vManage The requirement for deployment of on-premises vBond controllers through the Cisco Plug and Play Connect process is Internet connectivity from vManage (Option C). The Cisco Plug and Play Connect process is used to establish secure connectivity between the vManage Network Management system and the vBond orchestrators, which are responsible for authenticating and orchestrating the control plane connections between vSmart controllers and vEdge routers. For this process to work, the vManage system must have Internet connectivity to reach and communicate with the vBond orchestrators during the initial deployment and configuration phase.

Stanleymahamadi 👍 1

B correct answer

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

The Cisco Plug and Play Connect (PnP Connect) process for on-premises vBond controllers requires a defined controller profile in the PnP Connect portal. This profile tells the PnP Connect service which vBond controller the device should contact and includes attributes such as the controller type and IP address. Without a controller profile, the on-premises vBond cannot be properly associated with the account and redirected to the correct SD-WAN fabric. The Cisco Plug and Play Connect PDF explicitly describes creating a controller profile as part of onboarding controllers. Therefore, option A is the necessary requirement.

Why the Other Options Are Wrong

Option B (a DNS name that identifies vBond) is not strictly required because vBond can be identified by IP address in the controller profile; DNS is useful for vManage reachability resolution but not a PnP Connect deployment prerequisite. Option C (Internet connectivity from vManage) is incorrect because vManage can be configured manually without direct Internet access for PnP Connect; it is the vBond or edge device that needs to reach the PnP Connect service. Option D (a CSV file that contains all controllers) is a bulk import convenience, not a requirement for deploying a single on-premises vBond through PnP Connect.

Community Comment Notes

Community opinion was split, with a majority voting for C, but as iking commented, "Internet connectivity from vManage" is often assumed due to cloud management, yet it is not a PnP Connect requirement. just_another_netguy correctly advised "Go with A" and linked the official Cisco Plug and Play Connect PDF, noting that devices are automatically associated with a default vBond profile if one exists in the account. mikidvd51 and others chose B based on a separate question about vBond reachability being resolved by DNS, but that scenario does not define the PnP Connect deployment requirement. The vote count does not override the documented controller profile requirement.

Official Reference

https://www.cisco.com/c/dam/en_us/services/downloads/plug-play-connect.pdf

Exam Strategy

Focus on the specific PnP Connect workflow: a controller profile must exist before the on-premises vBond can be onboarded. Remember that Internet connectivity is needed by the controller, not vManage, and DNS is optional when an IP is provided.

Frequently Asked Questions

Why is Internet connectivity from vManage not required for PnP Connect?

vManage can be configured manually without direct Internet access; the vBond controller itself reaches the PnP Connect service to obtain its configuration.

Can vBond be deployed via PnP Connect without a DNS name?

Yes, the controller profile can use an IP address to identify vBond; DNS is not a strict requirement for the PnP Connect deployment process.

Related Analysis

Practice All 300-415 Questions

Access 120 questions with complete answers and detailed explanations.

View Full 300-415 Practice Test →

← Back to 300-415 Study Guide