What are two settings that an administrator can configure from the AppDynamics Controller Admin Console? (Choose two.)
Metrics baseline calculation
Controller log file rotation
Controller heap size
License allocation
Retention periods
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:
References: Access the Administration Console, License Rules, Data Retention
What is the minimum recommended number of nodes for a redundant Events Service?
1
2
3
4
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:
References:
If using SSL for agent communication with an AppDynamics Controller, it is recommended that agent SSL traffic
is encrypted with a 64-bit encryption key
is decrypted and then encrypted again at the firewall
terminates at a reverse proxy or a load balancer in front of the Controller
terminates at the Controller
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.
Which type of Alert and Respond action is available only on an on-premises Controller?
Remediation action
Cloud auto-scaling
Diagnostic action
Custom action
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
What is the correct method to perform a NET Agent upgrade?
Perform the agent upgrade on the application server host by running the MSI Installer Package.
Perform the agent upgrade on a remote server host by using the AppDynamics Controller REST API.
Perform the agent upgrade on the application server host by running the Agent Configuration Utility.
Perform the agent upgrade via the AppDynamics Controller Ul.
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:
References:
What are two reasons that would require an administrator to install the Events Service cluster manually? (Choose two.)
Installation on SUSE Linux
Security concerns with passwordless SSH
Security requirements to install using a non-root user account
Installation on Windows
According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the two reasons that would require an administrator to install the Events Service cluster manually are:
The incorrect options are:
References:
Which framework would require the implementation of custom correlation?
Custom TCP concurrent server
Customer proprietary SOAP application
Vendor-supplied enterprise application that uses JMS
Pre-packaged WCF application
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.
An administrator is asked toimprove the capacity of an Events Service cluster. What is the recommended way to add capacity to the cluster?
Add a new Events Service cluster to share the load.
Add nodes running on machines with identical hardware matching the existing nodes.
Add more storage to the master nodes of the cluster.
Add more storage to as many of the existing nodes as possible.
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:
References:
Instead of using the Enterprise Console Ul, how can an administrator import an existing keypair to manage the Controller SSL certificate?
Add the keypair to the keystore.jks using a third-party tool.
Re-run the Controller installer and specify the new keypair.
Upload a new keystore.jks file through the Controller Ul.
Upload the keypair from within the Controller UL.
 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:
References:
Which two statements are true when updating the Database Agent? (Choose two.)
The Database Agent must be stopped and restarted during the upgrade.
If the agent is moved to a new location during the upgrade, the AppDynamics Controller must be reconfigured to reference the new location of the agent.
All data collectors created from the previous agent must be migrated to the new agent.
Controller-info.xml is the only file that needs to be migrated from the previous agent to the new agent.
After the Database Agent is upgraded, the AppDynamics Controller must be restarted.
According to the Cisco AppDynamics Professional Implementer (CAPI) documents, when updating the Database Agent, you need to follow these steps12:
Therefore, the correct statements are:
The incorrect statements are:
References:
The application server was restarted after an upgrade. What are two valid ways to confirm that the upgraded Java Agent is running successfully? (Choose two.)
Verify that the application log contains a message indicating success.
Verify that the node within the Controller Ul indicates the app agent is reporting.
Verify the Java Agent Version metric for that node in the Metric Browser.
Verify that the Java Agent log contains a message indicating the agent started successfully.
According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the two valid ways to confirm that the upgraded Java Agent is running successfully are:
The incorrect options are:
References:
What are three valid reasons to use the AppDynamics REST API to retrieve metrics? (Choose three.)
to archive 1-minute granularity data
to create a custom report to be run monthly to show average node availability
to calculate a new metric based on two existing metrics
to evaluate health rules
to retrieve health rule violations
to create an alert using a baseline to send to an internal ticketing system
The AppDynamics REST API to retrieve metrics allows you to get values generated for metrics by specifying the path of the metric and the time frame for the data1. Some of the valid reasons to use this API are12: