A new manufacturing site powers on its WAN Edge behind NAT with only the controller DNS name configured. It must authenticate its identity, learn the SD-WAN Controller and Manager addresses, and report its public IP and port. Which SD-WAN Validator role explains that bootstrap sequence?
Select an answer to reveal the explanation.
Short Explanation
Bootstrapping can feel magical until you see the handshake! Your edge checks in, gets introductions, and shares its return address via orchestration. That first Validator contact unlocks everything else.
Full Explanation
The SD-WAN Validator (formerly vBond) is the initial orchestrator that authenticates WAN Edges and controllers using PKI certificates, provides the list of SD-WAN Manager and SD-WAN Controller addresses to join, and performs NAT discovery by observing the source IP and port of incoming connections so edges and controllers can establish DTLS/TLS control sessions and later IPsec tunnels through NAT. Terminating user IPsec tunnels and routing service-VPN traffic fails by concept because that is the WAN Edge data-plane function, while the Validator never forwards customer payload. Distributing OMP prefixes and enforcing policy fails by concept because that is the SD-WAN Controller (formerly vSmart) control-plane role after orchestration completes. Collecting telemetry and rendering dashboards fails by concept because that is the SD-WAN Manager (formerly vManage) management-plane role once devices are onboarded. For the exam remember Validator involvement is heaviest at bring-up and recovery when devices need peer discovery, and in practice verify organization name matches, certificates are valid, and required ports to the Validator are reachable from behind NAT.