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

The AppDynamics Controller Admin Console lets you configure certain global settings for the Controller, such as metric retention periods, UI notification triggers, tenancy mode, and accounts in multi-tenancy mode1. Two of the settings that an administrator can configure from the AppDynamics Controller Admin Console are:

• License allocation: This setting allows you to view and manage the license usage and availability for your Controller. You can see the total number of licenses, the number of licenses in use, the number of licenses available, and the license expiration date for each agent type. You can also allocate licenses to specific applications or accounts, and set license limits and alerts2.
• Retention periods: This setting allows you to specify how long the Controller retains the metric data and the event data for your monitored applications. You can configure the retention periods for different types of data, such as minute-level metrics, hour-level metrics, day-level metrics, transaction snapshots, and events. You can also configure the data purge schedule and the data backup schedule3.

References: Access the Administration Console, License Rules, Data Retention

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the minimum recommended number of nodes for a redundant Events Service is three ©. The Events Service is a distributed database that stores and processes the analytics data collected by the AppDynamics platform. The Events Service cluster consists of multiple nodes that share the data load and provide fault tolerance and high availability. The minimum number of nodes for a functional Events Service cluster is one, but this is not recommended for production environments, as it does not provide any redundancy or resilience. The minimum number of nodes for a redundant Events Service cluster is three, as this allows the cluster to tolerate the failure of one node without losing any data or availability. The recommended number of nodes for a redundant Events Service cluster is five or more, as this provides better performance and scalability12.

The incorrect options are:

• 1 (A): This is not a valid option because a single-node Events Service cluster does not provide any redundancy or resilience. If the node fails, the cluster becomes unavailable and the data is lost. A single-node Events Service cluster is only suitable for testing or development purposes, not for production environments12.
• 2 (B): This is not a valid option because a two-node Events Service cluster does not provide sufficient redundancy or resilience. If one node fails, the cluster becomes unstable and may lose data or availability. A two-node Events Service cluster is not recommended for production environments12.
• 4 (D): This is not a valid option because a four-node Events Service cluster is not optimal for redundancy or resilience. A four-node Events Service cluster has an even number of nodes, which may cause a split-brain scenario, where the cluster is divided into two equal partitions that cannot communicate with each other. This may result in data inconsistency or unavailability. A four-node Events Service cluster can be improved by adding a fifth node to avoid the split-brain scenario12.

References:

• 1: Events Service Deployment - AppDynamics
• 2: Events Service Requirements - AppDynamics

AppDynamics recommends that you terminate SSL connections from agents at a reverse proxy or a load balancer in front of the Controller, rather than at the Controller itself. This improves the performance and scalability of the Controller by offloading the SSL processing to the proxy or load balancer. It also simplifies the configuration and management of SSL certificates and truststores. To enable this option, you need to configure the proxy or load balancer to accept SSL connections from agents and forward them to the Controller using HTTP. You also need to configure the agents to use SSL and point to the proxy or load balancer host and port. See Enable SSL for the Java Agent for an example. References: Agent-to-Controller Connections and Enable SSL and SSH for Database Agent Communications in the AppDynamics documentation.

A custom action is a type of Alert and Respond action that allows you to integrate AppDynamics notifications with your own alerting or ticketing system. You can create a custom action by writing an executable script and an XML file that describe how to pass information from AppDynamics to your system. A custom action can be triggered by a policy based on a health rule violation or an event. A custom action is available only on an on-premises Controller, because it requires access to the Controller file system and the ability to execute scripts on the Controller host machine. For a SaaS Controller, you can use HTTP request templates instead of custom actions to integrate with external systems. References: Build a Custom Action, Alert and Respond, Actions, Custom Actions

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the correct method to perform a NET Agent upgrade is to perform the agent upgrade on the application server host by running the MSI Installer Package12. This method will install updated agent files and maintain legacy configurations. You do not need to uninstall the old agent first when you upgrade from the NET Agent >= 3.9, except for patch releases. You need to stop IIS, instrumented Windows services, and instrumented standalone applications before running the MSI Installer Package. You also need to launch an elevated command prompt with full administrator privileges and specify youraccount access key for single-tenant Controller accounts. After the installation, you need to restart Windows services and standalone applications.

The incorrect options are:

• Perform the agent upgrade on a remote server host by using the AppDynamics Controller REST API. (B) This is not a valid method for upgrading the NET Agent, because the AppDynamics Controller REST API does not provide any endpoint for agent installation or upgrade. The REST API is mainly used for retrieving or updating configuration data, metrics, events, snapshots, and other information from the Controller3.
• Perform the agent upgrade on the application server host by running the Agent Configuration Utility. © This is not a valid method for upgrading the NET Agent, because the Agent Configuration Utility is a tool for modifying the agent configuration after installation, not for installing or upgrading the agent. The Agent Configuration Utility allows you to change the Controller connection settings, the agent logging level, the proxy settings, and other advanced options4.
• Perform the agent upgrade via the AppDynamics Controller UI. (D) This is not a valid method for upgrading the NET Agent, because the AppDynamics Controller UI does not provide any feature for agent installation or upgrade. The Controller UI is mainly used for monitoring, analyzing, and troubleshooting the performance of the applications, business transactions, tiers, nodes, and other entities that are instrumented by the agents5.

References:

• 1: Upgrade the .NET Agent for Windows - AppDynamics
• 2: Release Upgrade Checklist for .NET Agents - AppDynamics
• 3: REST API - AppDynamics
• 4: Configure the .NET Agent - AppDynamics
• 5: AppDynamics Application Performance Monitoring Platform - AppDynamics