300-415 · Question #454
Which VPNs must be configured outside the workflow to complete the SD-WAN overlay setup when using the Quick Connect workflow?
The correct answer is A. service VPNs. The Quick Connect workflow automates transport and management VPN configuration but requires service VPNs, which carry enterprise user traffic, to be configured manually outside the workflow.
Question
Options
- Aservice VPNs
- Btransport VPNs
- Cservice and transport VPNs
- Dmanagement VPNs
How the community answered
(44 responses)- A93% (41)
- B2% (1)
- C2% (1)
- D2% (1)
Why each option
The Quick Connect workflow automates transport and management VPN configuration but requires service VPNs, which carry enterprise user traffic, to be configured manually outside the workflow.
Service VPNs (VPN 1 and above) carry actual enterprise application traffic between sites and must be configured outside the Quick Connect workflow because they require organization-specific decisions about segmentation, routing policies, and firewall rules. The Quick Connect workflow is scoped to establishing the SD-WAN overlay itself by automating transport (VPN 0) and management (VPN 512) configurations, leaving service VPN design to the engineer.
Transport VPNs (VPN 0) are directly handled by the Quick Connect workflow as they are fundamental to establishing the SD-WAN underlay tunnels and overlay fabric.
Transport VPNs are within the scope of the Quick Connect workflow automation, so only service VPNs - not both service and transport - require manual configuration outside the workflow.
Management VPNs (VPN 512) are configured as part of the Quick Connect workflow to enable out-of-band device management connectivity.
Concept tested: SD-WAN Quick Connect workflow VPN configuration scope
Source: https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/system-interface/ios-xe-17/systems-interfaces-book-xe-sdwan/quick-connect-workflow.html
Topics
Community Discussion
No community discussion yet for this question.