Exam 300-415 topic 1 question 261 discussion

A Cisco SD-WAN Manager cluster consists of the following architectural components: *Application server *Configuration database *Network configuration system *Statistics database *Message bus

i think its DE

I think A y E

https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/optimization-ha/vedge/network-optimization-high-availability-book/high-availability.html This is the correct answer

https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/optimization-ha/vedge/network-optimization-high-availability-book/high-availability.html

The question asks about the architectural components of a vManage cluster, not the functions that it performs. A network configuration system is a function that the vManage cluster performs, but it is not a component of the vManage cluster. The components of the vManage cluster are the application server, the configuration database, the statistics database, and the message bus. The network configuration system runs on the application server and uses the configuration database to store and manage network configurations. Therefore, A is not a correct answer.

The two architectural components that are part of an SD-WAN high availability vManage cluster are: D. messaging server—Handles the communication between the vManage instances and the routers, as well as between the vManage instances themselves. E. application server—Runs the vManage web application and provides the GUI interface for the administrator. A network configuration system is not a component of a vManage cluster, but rather a function that the vManage cluster performs. A network configuration system is a system that manages network configurations, such as Cisco NSO, Ansible, or Puppet. A vManage cluster stores all configuration information, policies, templates, certificates, and more in the configuration database, which runs on the messaging servers. The network configuration system is not a separate component of the vManage cluster, but rather a function that the vManage cluster performs. Therefore, A is not a correct answer.

The Answer is A&E The architectural components that make up the VManage cluster are: *Application server This provides a web server for user sessions. Through these sessions, a logged-in user can view a high-level dashboard summary of networks events and status, and can drill down to view details of these events. A user can also manage network serial number files, certificates, software upgrades, device reboots, and configuration of the vManage cluster itself from the vManage application server. *Configuration database Stores the inventory and state and the configurations for all Cisco vEdge devices. *Network configuration system Stores all configuration information, policies, templates, certificates, and more. *Statistics database Stores the statistics information collected from all Cisco devices in the overlay network. *Message bus Communication bus among the different vManage instances. This bus is used to share data and coordinate operations among the vManage instances in the cluster.

It should be A, E based on my findings below. https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/optimization-ha/vedge/network-optimization-high-availability-book/high-availability.html A vManage cluster consists of the following architectural components: ->E - Application server—This provides a web server for user sessions. - Configuration database—Stores the inventory and state and the configurations for all Cisco vEdge devices. ->A - Network configuration system—Stores all configuration information, policies, templates, certificates, and more. - Statistics database—Stores the statistics information collected from all Cisco devices in the overlay network. - Message bus—Communication bus among the different vManage instances.

D and E are correct answers

This should be D and E...it's a configuration database that runs as a service so A is wrong NMS server proxy NMS application server NMS configuration database NMS coordination server NMS messaging server NMS statistics database NMS data collection agent NMS cloud agent NMS container manager NMS SDAVC proxy