300-415 · Question #352
How is vBond reachability resolved by vManage?
The correct answer is B. DNS. vManage resolves vBond reachability using DNS, allowing the vBond FQDN to be mapped to one or more vBond IP addresses for controller discovery.
Question
Exhibit
Options
- AIPsec
- BDNS
- CBGP
- DOMP
How the community answered
(20 responses)- A5% (1)
- B90% (18)
- C5% (1)
Why each option
vManage resolves vBond reachability using DNS, allowing the vBond FQDN to be mapped to one or more vBond IP addresses for controller discovery.
IPsec is a tunneling and encryption protocol used for securing data plane traffic, not a mechanism for resolving vBond controller reachability.
vManage uses DNS resolution to determine the IP address(es) of the vBond orchestrator based on the configured FQDN. This enables WAN Edge devices to discover and authenticate with the correct vBond instance, which is especially important in redundant vBond deployments where multiple IPs may be returned.
BGP is a routing protocol used for exchanging routing information between autonomous systems and is not used by vManage to resolve vBond reachability.
OMP (Overlay Management Protocol) is used for exchanging routing and policy information within the SD-WAN overlay, not for initial vBond address resolution by vManage.
Concept tested: vBond reachability resolution via DNS in vManage
Source: https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/system-interface/vedge-20-x/systems-interfaces-book/system-interface.html
Topics
Community Discussion
No community discussion yet for this question.