500-430 Exam Dumps : Cisco AppDynamics Professional Implementer(CAPI)

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, when updating the Database Agent, you need to follow these steps12:

• Stop the agent as described for your specific installation in Start and Stop the Database Agent.
• Make a copy of the existing agent directory, . Backing up allows you to revert to the previous agent installation if you need to. You can also copy over the controller-info.xml configuration file to the new installation to ensure the agent configuration is maintained.
• Install the Database Agent as described for your specific installation in Administer the Database Agent.
• Copy the \conf\controller-info.xml file to the new installation directory, \conf. To ensure the agent configuration is maintained, copy the \conf\controller-info.xml file to the new installation directory, \conf.
• Start the new agent. See Start and Stop the Database Agent.
• Verify the Database Agent Installation. See Verify the Database Agent Installation.

Therefore, the correct statements are:

• The Database Agent must be stopped and restarted during the upgrade. (A)
• Controller-info.xml is the only file that needs to be migrated from the previous agent to the new agent. (D)

The incorrect statements are:

• If the agent is moved to a new location during the upgrade, the AppDynamics Controller must be reconfigured to reference the new location of the agent. (B) This is not true because the controller-info.xml file contains the information about the Controller host, port, account name, access key, and SSL settings. As long as this file is copied to the new agent location, the Controller does not need to be reconfigured.
• All data collectors created from the previous agent must be migrated to the new agent. © This is not true because the data collectors are configured on the Controller UI, not on the agent. The agent collects the metrics from the databases and sends them to the Controller. The data collectors do not need to be migrated to the new agent.
• After the Database Agent is upgraded, the AppDynamics Controller must be restarted. (E) This is not true because the Controller does not depend on the agent version. The agent and the Controller are compatible as long as they meet the Agent and Controller Compatibility requirements.

References:

• 1: Upgrade the Database Agent - AppDynamics
• 2: Release Upgrade Checklist for Database Agents - AppDynamics

The Events Service is the on-premises data storage facility for unstructured data generated by Application Analytics, Database Visibility, and End User Monitoring deployments. The Events Service can be deployed as a single node or a cluster of three or more nodes, depending on the data volume and availability requirements. The Controller and other Events Service clients connect to the Events Service to store and retrieve analytics data. Therefore, it is essential that the Controller is able to initiate communication with the Events Service cluster, using the Events Service API ports (default 9080/2081). The Events Service cluster does not need to initiate communication with the Controller, as it only responds to the requests from the clients. The Events Service API ports can be reconfigured from the default values, if needed, by modifying the conf/events-service-api-store.properties file on each node. However, the clients must also be updated with the new port values. It is also recommended to use a load balancer or a virtual IP address in front of the Events Service cluster, to provide a single endpoint for the clients and to enable load balancing and failover among the nodes. References: Events Service Deployment, Install the Events Service on Linux, and Install the Events Service on Windows in the AppDynamics documentation.

In a hybrid deployment of AppDynamics, where the AppDynamics Controller and Events Service are installed on-premises and the EUM Server is hosted in AppDynamics’ SaaS cloud, the data that is unavailable is the analytics metrics for End-User Monitoring data sets. This is because the analytics metrics require the Events Service to store and process the unstructured data generated by the EUM agents. However, in a hybrid deployment, the EUM Server and the Events Service are not connected, and the EUM Server does not send the EUM data to the Events Service. Therefore, the analytics metrics for EUM data sets, such as browser records, mobile snapshots, network requests, and custom events, are not available in the Controller UI or the Analytics UI1. The other data, such as resource loading times, session information, and browser snapshots, are available in the EUM Server UI, as they are stored and displayed by the EUM Server itself2. References: Hybrid Deployment and EUM Data Sets in the AppDynamics documentation.