Question No. 1

A company set up an on-premises AppDynamics Controller and an on-premises Events Service cluster. What describes setting up this Events Service cluster?

AThe Events Service API ports cannot be reconfigured from the default 9080/2081.

BThe Controller must be able to initiate communication with the Events Service cluster.

CThe Events Service cluster must be able to initiate communication with the Controller.

DThere is no need for a load balancer or virtual IP address in front of the Events Service cluster.

Show Answer

Correct Answer: B

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 theconf/events-service-api-store.propertiesfile 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.Reference:Events Service Deployment,Install the Events Service on Linux, andInstall the Events Service on Windowsin the AppDynamics documentation.

Question No. 2

Instead of using the Enterprise Console Ul, how can an administrator import an existing keypair to manage the Controller SSL certificate?

AAdd the keypair to the keystore.jks using a third-party tool.

BRe-run the Controller installer and specify the new keypair.

CUpload a new keystore.jks file through the Controller Ul.

DUpload the keypair from within the Controller UL.

Show Answer

Correct 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

Question No. 3

What is the minimum recommended number of nodes for a redundant Events Service?

A1

B2

C3

D4

Show Answer

Correct Answer: C

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.

1: Events Service Deployment - AppDynamics

2: Events Service Requirements - AppDynamics

Question No. 4

Which two methods are available to define JVM options for an AppDynamics Controller so that the JWM options are retained across upgrades of the Controller? (Choose two.)

AUse the modifyJvmOptions utility provided by AppDynamics.

BDefine JVM options on the Controller Settings page of the Enterprise Console.

CPass JVM options to the Controller via java -javaagent:''options jar''.

DUse the controller.sh script provided by AppDynamics.

EDefine JVM options manually in the domain. xmi file.

Show Answer

Correct Answer: A, B

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the two methods that are available to define JVM options for an AppDynamics Controller so that the JVM options are retained across upgrades of the Controller are:

Use the modifyJvmOptions utility provided by AppDynamics. (A) This is a valid method because the modifyJvmOptions utility is a script that allows you to add, remove, or list the JVM options for the Controller without manually editing any files. The utility also validates the syntax and format of the JVM options and creates a backup of the original configuration. The utility is located in the <controller_home>/bin directory and can be run on Linux or Windows platforms.The utility updates the <controller_home>/appserver/glassfish/domains/domain1/config/domain.xml file with the specified JVM options, which are preserved during the Controller upgrade12.

Define JVM options on the Controller Settings page of the Enterprise Console. (B) This is a valid method because the Controller Settings page of the Enterprise Console is a graphical user interface that allows you to configure various settings for the Controller, including the JVM options. The Enterprise Console is a web-based application that provides a centralized way to manage the AppDynamics platform components, such as the Controller, the Events Service, and the EUM Server.The Enterprise Console also handles the Controller upgrade process and preserves the JVM options that are defined on the Controller Settings page34.

The incorrect options are:

Pass JVM options to the Controller via java -javaagent:''options jar''. This is not a valid method because the java -javaagent option is used to specify the path to the AppDynamics agent jar file, not the JVM options for the Controller. The agent jar file is used to instrument the Java applications that are monitored by the AppDynamics platform, not the Controller itself. The agent jar file also contains the agent configuration properties, such as the Controller host, port, account name, access key, and application name.Passing JVM options to the Controller via this option will not have any effect on the Controller performance or behavior5.

Use the controller.sh script provided by AppDynamics. (D) This is not a valid method because the controller.sh script is used to start, stop, or restart the Controller, not to define the JVM options for the Controller. The controller.sh script is located in the <controller_home>/bin directory and can be run on Linux platforms. The controller.sh script does not accept any arguments or parameters for the JVM options, and does not update any configuration files with the JVM options.Using this script to define the JVM options for the Controller will not have any effect on the Controller performance or behavior6.

Define JVM options manually in the domain. xmi file. (E) This is not a valid method because the domain. xmi file is not a configuration file for the JVM options for the Controller, but a configuration file for the WebSphere Application Server. The WebSphere Application Server is a Java EE application server that can be used to host the Java applications that are monitored by the AppDynamics platform, not the Controller itself. The domain. xmi file contains the settings for the WebSphere Application Server, such as the server name, port, security, data sources, and class loaders.Defining JVM options manually in this file will not have any effect on the Controller performance or behavior, and may cause errors or conflicts with the WebSphere Application Server configuration7.

1: Modify JVM Options for the Controller - AppDynamics

2: Release Upgrade Checklist for Controllers - AppDynamics

3: Configure the Controller Using the Enterprise Console - AppDynamics

4: Upgrade the Controller Using the Enterprise Console - AppDynamics

5: Install the Java Agent - AppDynamics

6: Start and Stop the Controller - AppDynamics