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

Custom correlation is needed when the default detection mechanisms of AppDynamics are not capable of auto-correlating transactions across tiers or across parent-child threads in complex multithreaded applications. Custom correlation enables the user to configure AppDynamics to propagate a unique correlation key by using the extension points of the distributed protocol or by decorating the payload. Among the four options, a custom TCP concurrent server is the most likely to require the implementation of custom correlation, as it is an unsupported framework and protocol that may not have easily-defined method calls or payload objects to configure as exit points or entry points. The other options, such as SOAP, JMS, and WCF, are supported by AppDynamics and can be automatically correlated by the agents without the need for custom configuration. References: Custom Correlation for Java Applications and Configure Custom Correlation for .NET Applications in the AppDynamics community.

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.

The directory contains the EUM Server installation files, configuration files, and data files. It is recommended to back up this directory as a precaution before upgrading or migrating the EUM Server. The default location of this directory is /AppDynamics/EUM, where is the directory where you installed the Controller. You can also use the backup-eum.sh script to back up the EUM Server data12. References: Upgrade the Production EUM Server, Configure the EUM Server