Download Cisco AppDynamics Professional Implementer.500-430.VCEplus.2024-02-14.21q.vcex

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.

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. SeeEnable SSL for the Java Agentfor an example.Reference:Agent-to-Controller ConnectionsandEnable SSL and SSH for Database Agent Communicationsin the AppDynamics documentation.

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the REST API for health rule violations allows you to retrieve information about the health rule violations that occurred in a specified time range for a given application1. You can use the REST API for health rule violations for the following valid reasons:For determining which actions have been executed (B): The REST API response includes the details of the actions that were triggered by the health rule violation, such as email, SMS, HTTP request, or custom action1. You can use this information to verify if the actions were executed successfully, or to troubleshoot any issues with the action execution.When searching for historical events : The REST API allows you to specify a custom time range for retrieving the health rule violations, such as BEFORE_TIME, AFTER_TIME, BETWEEN_TIMES, or BEFORE_NOW1. You can use this feature to search for historical events that occurred in the past, or to analyze the trends and patterns of the health rule violations over time.The incorrect options are:For updating an AppDynamics dashboard (A): This is not a valid reason for using the REST API for health rule violations, because the AppDynamics dashboards already display the health rule violations that occurred in the selected time frame, along with the severity, status, affected entities, and actions2. You do not need to use the REST API to update the dashboard, as the dashboard is automatically refreshed with the latest data from the Controller.For sending emails (D): This is not a valid reason for using the REST API for health rule violations, because the REST API does not send emails directly. The REST API only returns the information about the health rule violations, and the actions that were triggered by them.If you want to send emails based on the health rule violations, you need to configure an email action in the health rule configuration, or use a custom action that invokes an external email service3.When pushing events to the Event Management System is NOT possible (E): This is not a valid reason for using the REST API for health rule violations, because the REST API does not push events to the Event Management System. The REST API only returns the information about the health rule violations, and the actions that were triggered by them.If you want to push events to the Event Management System, you need to configure an HTTP request action in the health rule configuration, or use a custom action that invokes an external API3.1: Health Rule Violations API - AppDynamics2: Health Rule Violations - AppDynamics3: Actions - AppDynamics

In a split-host configuration, where the EUM Server and Controller are on separate hosts, the EUM Server requires access to the Controller primary HTTP(s) port. This is because the EUM Server needs to communicate with the Controller API server to send data and receive configuration information.The default primary HTTP port for the Controller is 8090 and the default primary HTTPS port is 81811.The dedicated EUM HTTP(s) ports are used by the EUM agents to send data to the EUM Server, not by the EUM Server to access the Controller2.The GlassFish administration port is used to access the Controller Admin Console, not by the EUM Server3.The Controller database port is used by the Controller to connect to the MySQL database, not by the EUM Server4.Reference:Controller Port Settings,Configure the Port for the EUM Agent,Access the Administration Console,Controller System Requirements

Before installing an AppDynamics Controller on Linux, you need to perform some preparatory tasks to ensure the system meets the requirements and the installation runs smoothly. Two of these tasks are:Install libaio on the host machine if it does not already have it installed. This library facilitates asynchronous I/O operations on the system, which are required by the Controller. You can use the package manager of your Linux distribution to install libaio, such as yum or apt-get.For example, on CentOS, you can runyum install libaio1.Verify that you have enough temporary (tmp) space available on the system, at least 1 GB. The Controller installation uses the tmp space to extract and install the software components.You can check the tmp space by runningdf -h /tmp2.If the tmp space is insufficient, you can either free up some space by deleting unnecessary files, or specify a different temporary directory for the installation by passing the-Djava.io.tmpdirparameter to the installer3.Other preparatory tasks include verifying the user account permissions, configuring the virus scanners, installing the netstat network utility, and setting the file descriptor limit2.Reference:Prepare Linux for the Controller,Install the Controller on Linux, and [Controller System Requirements] in the AppDynamics documentation.

The AppDynamics Controller properties that govern how long metric data is retained in the database are1:metrics.ten.min.retention.period: This property specifies the number of days to retain metric data at 10-minute granularity. The default value is 32 days.metrics.retention.period: This property specifies the number of days to retain metric data at 1-hour granularity. The default value is 365 days.metrics.min.retention.period: This property specifies the number of hours to retain metric data at 1-minute granularity. The default value is 4 hours.The other options are incorrect because1:metrics.ten.sec.retention.period: This property does not exist in the AppDynamics Controller. The finest granularity for metric data is 1 minute.metrics.day.retention.period: This property does not exist in the AppDynamics Controller. The coarsest granularity for metric data is 1 hour.metrics.week.retention.period: This property does not exist in the AppDynamics Controller. The metric data retention is based on days, not weeks.Reference:Database Size and Data Retention

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the method to import an existing keypair to manage the Controller SSL certificate without using the Enterprise Console UI is to add the keypair to the keystore.jks using a third-party tool (A). The keystore.jks file is the default keystore for the Controller that contains the private keys and certificates for the secure communication on port 8181. If the administrator already has a custom keypair that is signed by a third-party Certificate Authority (CA) or an internal CA, they can use a third-party tool, such as KeyStore Explorer or OpenSSL, to import the keypair into the keystore.jks file. The administrator should also import the root or intermediate certificates of the CA into the cacerts.jks file, which is the default truststore for the Controller. The administrator should use the keytool utility, which is bundled with the Controller installation, to import the certificates into the cacerts.jks file.The administrator should also update the password for the keystore.jks and cacerts.jks files, and restart the Controller to apply the changes12.The incorrect options are:Re-run the Controller installer and specify the new keypair. (B) This is not a valid method because the Controller installer does not allow the administrator to specify a custom keypair for the Controller SSL certificate. The Controller installer only allows the administrator to specify the Controller host name, port, account name, access key, and database settings.The Controller installer does not modify the keystore.jks or cacerts.jks files, and does not import any custom keypair or certificate into the Controller keystore or truststore3.Upload a new keystore.jks file through the Controller UI. This is not a valid method because the Controller UI does not provide any feature to upload a new keystore.jks file for the Controller SSL certificate. The Controller UI only allows the administrator to view and edit the Controller settings, such as the license, the security, the email, the analytics, and the EUM.The Controller UI does not access or modify the keystore.jks or cacerts.jks files, and does not import any custom keypair or certificate into the Controller keystore or truststore4.Upload the keypair from within the Controller UI. (D) This is not a valid method because the Controller UI does not provide any feature to upload a custom keypair for the Controller SSL certificate. The Controller UI only allows the administrator to view and edit the Controller settings, such as the license, the security, the email, the analytics, and the EUM.The Controller UI does not access or modify the keystore.jks or cacerts.jks files, and does not import any custom keypair or certificate into the Controller keystore or truststore4.1: Controller SSL and Certificates - AppDynamics2: How do I resolve SSL certificate validation errors in the .NET Agent? - AppDynamics3: Install the Controller - AppDynamics4: Controller Settings - AppDynamics

The most important factor in determining sizing for AppDynamics Controller is the projected metric load per minute on the Controller. This is because the metric load represents the actual workload on the Controller, which depends on the nature of the application, the AppDynamics configuration, and the usage patterns. The number of agents, the type of agents, the number of administrators/end users, and the number of AppDynamics applications are only rough estimates that can vary greatly depending on the specific scenario. Therefore, it is recommended to test the performance of the system in a staging environment and verify the Controller sizing using the metric upload rate before deploying to production.Reference:Controller System Requirements,Performance and Controller sizing guidelines,How to Run AppDynamics in Microsoft Azure,Platform Requirements

The Health Rule REST API allows you to create, configure, update, and delete health rules for multiple applications simultaneously. To use this API, you need to specify the application in the URL string. You can use either the application ID or the application name for this purpose. The application ID is a unique numeric identifier for each application in the Controller. The application name is the display name of the application in the AppDynamics UI. You cannot use the application alias, GUID, or REGEX for the Health Rule REST API.Reference:Health Rule APIandRetrieve All Business Applicationsin the AppDynamics documentation.

To set up AppDynamics Controllers as a high availability pair, you need to meet the following requirements1:Passwordless SSH must be configured between the two Controller servers. This allows the Enterprise Console to automate the configuration and administration tasks associated with a highly available deployment on Linux systems.Both servers must have the Controller software installed prior to setting up high availability. The Controllers in an HA pair must be equivalent versions, and be in the same data center.Both servers must have identical directory structures for the Controller installation. The individual machines in the Controller HA pair need to have an equivalent amount of disk space.Reference:Prerequisites for High Availability