Impacts of Losing vManage Connectivity to Cisco SD-WAN Fabric

300-415 By islever Editorial Last updated

Short answer

AD Policy changes propagation stops and Statistics collection stops when vManage loses connectivity to the fabric.

Question

What are the two impacts of losing vManage connectivity to fabric in the Cisco SD-WAN network? (Choose two.)
  1. Policy changes propagation stops. Correct Answer
  2. Creation of templates is impossible.
  3. BFD peering between WAN Edge devices are established.
  4. Statistics collection stops. Correct Answer
  5. IPsec tunnels tear down for WAN Edge devices.

Key Takeaways

The exam tests the distinction between configuration storage (vManage) and runtime enforcement/telemetry; losing connectivity stops live data flow but not local device operation or config drafting.

This question examines the operational consequences when a vManage controller loses connectivity to the SD-WAN fabric. It clarifies that while management functions like template creation remain possible, active policy propagation and telemetry collection are halted.

Common mistake: Many candidates select B (Template creation impossible), failing to realize that templates can still be created in the vManage GUI even if they cannot be pushed to the fabric.

Expert Analysis

Why the Answer Is Correct

When vManage loses connectivity to the fabric, it can no longer push configuration changes to WAN Edge devices via OMP or NETCONF, meaning Policy changes propagation stops (A). Additionally, vManage relies on this connection to collect telemetry and statistics from the devices; without it, Statistics collection stops (D). These are direct impacts of the control plane disconnect.

Why the Other Options Are Wrong

Option B is incorrect because administrators can still create and save templates within the vManage database itself, even if they cannot be deployed. Option C is false because BFD peering occurs directly between WAN Edge devices and does not rely on vManage for establishment. Option E is incorrect because IPsec tunnels are maintained by the WAN Edge devices independently; loss of vManage connectivity does not tear down existing secure tunnels.

Community Comment Notes

Community feedback highlights the nuance between "creating" and "pushing" configurations. As noted by user ManjeshM, "templates can be created... but it can't be pushed." User Gycu reinforces this by stating that policy propagation stops because you cannot push changes, whereas option B is false because creation is local. Some users initially chose BD, confusing template creation with policy activation, but the consensus confirms AD as the accurate technical impacts.

Exam Strategy

Always distinguish between 'configuration' (stored in vManage) and 'enforcement' (on WAN Edges). If vManage is disconnected, you lose the ability to change the network state, but the network continues to run based on its last known good configuration.

Frequently Asked Questions

Can I still create templates if vManage loses fabric connectivity?

Yes, you can create and edit templates in the vManage GUI/database. The limitation is only that these templates cannot be pushed (propagated) to the WAN Edge devices.

Do IPsec tunnels go down if vManage is unreachable?

No, IPsec tunnels are established and maintained directly between WAN Edge devices. They do not depend on vManage connectivity to stay up.

More 300-415 FAQ →

Community Votes

AD
55%
BD
45%

55% of anonymous learners picked answer AD. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 6 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 6

  1. Zamochit 👍 3
    Propagation stop? you can't modify it if you dont have vmanage.
  2. Gycu 👍 2
    AD A. Policy changes propagation stops. -> true / if you change a policy you cannot push it B. Creation of templates is impossible. -> false, you can create on vManage only C. BFD peering between WAN Edge devices are established. ->false D. Statistics collection stops. -> true E. IPsec tunnels tear down for WAN Edge devices. ->false
  3. ManjeshM 👍 2
    Options A & D are correct. The vManage lost connectivity to the Fabric, but it is still accessible to the Admin. Hence, template can be created, but it can't be pushed or propagated to the Fabric due to the connectivity loss.
  4. Matt2727 👍 2
    A, D seem correct. The question state loss of connectivity to the fabric and not loss of management.
  5. Knowledge33 👍 1
    It is important to understand that policies are configured on vSmart or vEdge. vManage is only a graphical user interface used to create and store policies, but once a policy is activated through the vManage GUI, it is configured with a NETCONF transaction either on vSmart or vEdge. https://www.networkacademy.io/ccie-enterprise/sdwan/policies
Show 1 more comment
  1. Rcont 👍 1
    A. Policy changes propagation stops. is not right because you don't have vManage to modify Policy.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

What Is Required for On-Premises vBond via PnP Connect?

S-grade

WAN Edge Registration with Enterprise CA Certificates

S-grade

Which Component Creates a Feature Profile in Cisco SD-WAN UX 2.0?

S-grade

What Is the BFD Multiplier in Application-Aware Routing?

S-grade

Practice All 300-415 Questions

Access 120 questions with complete answers and detailed explanations.

View Full 300-415 Practice Test →

← Back to 300-415 Study Guide