Which URL retrieves all AppDynamics business applications from an AppDynamics Controller using the AppDynamics Rest API?
Answer : C
The AppDynamics Rest API allows you to retrieve information and perform operations on the AppDynamics platform using HTTP requests. To retrieve all AppDynamics business applications from an AppDynamics Controller using the AppDynamics Rest API, you need to use the following URL format:
http(s)://<controller-host>:
This URL returns the business application names and internal numeric identifiers for all the applications that are monitored by the Controller. You can use the application name or ID as a parameter for other API methods that require the application context. You can also specify the output format as XML (default) or JSON by adding the output query parameter. For example:
http(s)://<controller-host>:
This URL returns the same information as the previous one, but in JSON format. You can also filter the applications by their status (alive or not) by adding the time-range-type query parameter. For example:
http(s)://<controller-host>:
This URL returns only the applications that are alive in the last 60 minutes.An alive application is an application with at least one node that submits at least one metric to the Controller in the provided time range12.Reference:Application Model API,Metric and Snapshot API
An administrator is asked to improve the capacity of an Events Service cluster. What is the recommended way to add capacity to the cluster?
Answer : B
According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the recommended way to add capacity to the Events Service cluster is to add nodes running on machines with identical hardware matching the existing nodes12. This will increase the data storage, replication, and redundancy of the cluster, as well as the processing power for queries.The Events Service cluster is horizontally scalable, so nodes can be added as your data storage requirements grow32.The Events Service must run on dedicated machines with identical directory structures, user account profiles, and hardware profiles1.For heap space allocation, AppDynamics recommends allocating half of the available RAM to the Events Service process, with a minimum of 7 GB up to 31 GB1.Solid-state drives (SSD) can significantly outperform hard disk drives (HDD), and are therefore recommended for production deployments1.
The incorrect options are:
Add a new Events Service cluster to share the load. (A) This is not recommended because it will create additional complexity and overhead for managing multiple clusters and routing data and queries to the appropriate cluster. It will also require more license units to enable analytics on multiple clusters.
Add more storage to the master nodes of the cluster. This is not recommended because it will not increase the data replication and redundancy of the cluster, nor the processing power for queries. It will also create an imbalance in the cluster, as the master nodes will have more storage than the worker nodes, which may affect the performance and stability of the cluster.
Add more storage to as many of the existing nodes as possible. (D) This is not recommended because it will not increase the data replication and redundancy of the cluster, nor the processing power for queries. It will also create an imbalance in the cluster, as some nodes will have more storage than others, which may affect the performance and stability of the cluster.
1: Cisco AppDynamics Professional Implementer (500-430)
2: Events Service Requirements - AppDynamics
3: Events Service Deployment - AppDynamics
4: Events Service Deployment - AppDynamics
Which URL retrieves all AppDynamics business transactions from an application using the AppDynamics Rest API?
Answer : B
The AppDynamics Rest API to retrieve business transactions allows you to get a list of all business transactions in a business application, along with their key metrics and properties1.The correct URL format for this API is1:
http(s) ://<controller-host>:
The other options are incorrect because12:
Option A uses an invalid endpoint /allbts, which does not exist in the API.
Option C uses an incorrect base URL /controller/applications, which is used for the Controller UI, not the Rest API.
Option D uses a misspelled endpoint /allbis, which does not exist in the API.Reference:Retrieve All Business Transactions in a Business Application,AppDynamics APIs
Which two statements are true regarding the AppDynamics REST API for retrieving metrics? (Choose two.)
Answer : A, E
The AppDynamics REST API for retrieving metrics allows you to get values generated for metrics by specifying the path of the metric and the time frame for the data1.The following statements are true regarding this API12:
Metrics can be retrieved for a fixed time range. You can use the time-range-type parameter to specify a fixed time range such as BEFORE_NOW, AFTER_TIME, or BETWEEN_TIMES. You can also use the duration-in-mins parameter to specify the length of the time range in minutes.
Wildcards can be used in the REST API metric path. You can use the asterisk () character as a wildcard to match any metric name or part of a metric name. For example, you can use the metric path Business Transaction Performance|Business Transactions||*|Average Response Time (ms) to retrieve the average response time for all business transactions in all tiers.Reference:Retrieve Metric Data,Retrieve Metric Hierarchy
Which two preparatory tasks are required prior to installing an AppDynamics Controller on Linux? (Choose two.)
Answer : D, E
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.
Which artifacts are needed, at minimum, to add a custom extension to a Machine Agent?
Answer : A
To add a custom extension to a Machine Agent, you need at least three artifacts: a directory, a jar or script file, and a monitor.xml file12. The directory is where you place your extension files under the <machine_agent_home>/monitors directory. The jar or script file is the executable file that collects and reports the custom metrics to the Machine Agent. The monitor.xml file is the configuration file that defines the name, frequency, and parameters of your extension.You can also optionally include other files such as libraries, configuration files, or templates for your extension12.Reference:Build a Monitoring Extension Using Scripts,Extensions and Custom Metrics
Instead of using the Enterprise Console Ul, how can an administrator import an existing keypair to manage the Controller SSL certificate?
Answer : A
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 - AppDynamics
2: How do I resolve SSL certificate validation errors in the .NET Agent? - AppDynamics
3: Install the Controller - AppDynamics
4: Controller Settings - AppDynamics