Question 580
A post-incident design review discusses the following: New Cisco SD-WAN edges cannot discover required controllers during initial secure onboarding. Which preventive design control MOST DIRECTLY addresses this specific risk?
Explanation
Correct Answer
Document bootstrap DNS, permitted ports and certificate lifecycle before site shipment. This control targets the underlying design risk. Secure SD-WAN onboarding depends on authenticated controllers and connectivity to the orchestration services. The follow-up acceptance check remains: A fresh edge registers successfully and establishes the expected authenticated controller connections.
Incorrect Answers
SD-WAN management centralizes configuration and visibility, while WAN edges forward application packets. The repeat risk here is different: Secure SD-WAN onboarding depends on authenticated controllers and connectivity to the orchestration services. A directly relevant preventive control is: Document bootstrap DNS, permitted ports and certificate lifecycle before site shipment.
The SD-WAN overlay control plane distributes reachability or policy, not the application payload itself. The repeat risk here is different: Secure SD-WAN onboarding depends on authenticated controllers and connectivity to the orchestration services. A directly relevant preventive control is: Document bootstrap DNS, permitted ports and certificate lifecycle before site shipment.
A carrier MPLS L3VPN separates customer routing via provider VRFs and distributes eligible customer prefixes. The repeat risk here is different: Secure SD-WAN onboarding depends on authenticated controllers and connectivity to the orchestration services. A directly relevant preventive control is: Document bootstrap DNS, permitted ports and certificate lifecycle before site shipment.