A regional retailer with 40 stores approved hosted SD-WAN Manager, SD-WAN Controller, and SD-WAN Validator in AWS. Branches have internet only, the overlay must use valid certificates, and all controllers must share the same organization name. Which prerequisite set must the engineer confirm first to onboard the cloud-hosted controller overlay?
Select an answer to reveal the explanation.
Short Explanation
You nailed the cloud checklist if you locked identity first. Cloud controllers only trust each other when organization name matches everywhere, with Smart Account and Validator reachability confirmed.
Full Explanation
Cloud-hosted controller onboarding hinges on identity and reachability before any device template is pushed, which is why matching organization name across Manager (formerly vManage), Controller (formerly vSmart), and Validator (formerly vBond), plus Smart Account entitlement for certificates, plus the public address of the Validator for initial discovery, plus internet reachability to required ports forms the prerequisite set. Matching site IDs with OMP passwords fails because site ID is per-site on edges and OMP credentials do not replace organization-wide trust and certificate entitlement. Matching serial files with VLAN maps fails because VLAN design is a branch LAN task that does not establish controller-to-controller authentication or cloud access. Matching hostnames with private Validator address fails because a private address is not reachable for cloud discovery from internet-only branches and hostname consistency alone does not prove organizational identity. Exam caveat is that organization name is case-sensitive and must match the certificate organization, and practical check is to verify Smart Account, certificate validity, and Validator DNS resolution from a branch internet circuit before bootstrapping.