If vManage loses connectivity to the fabric, which two effects occur? (Choose two.)

When vManage loses connectivity to the SD-WAN fabric, two key effects occur. First, policy change propagation stops because vManage is the centralized orchestrator responsible for pushing configuration and policy updates to all devices in the overlay network. Without connectivity, it cannot distribute these changes. Second, statistics collection stops. vManage acts as the central repository and collector for operational data, performance metrics, and logs from all SD-WAN devices. If the connection is lost, devices can no longer send this data to vManage for aggregation and analysis. Template creation becoming impossible is incorrect because template creation is a function of the vManage GUI, which can still be accessed and used to create templates even if vManage itself is disconnected from the fabric. BFD peering between WAN Edges is established is incorrect; BFD peering is a data plane function between WAN Edge devices and operates independently of vManage connectivity. IPsec tunnels tearing down for WAN Edges is also incorrect; existing IPsec tunnels between WAN Edges remain up and operational as long as the underlying network connectivity is stable, as their establishment and maintenance are handled by the WAN Edge devices themselves, not continuously by vManage.