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 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:
Which directory should an administrator back up if the goal is to back up the EUM Server?
The
A company set up an on-premises AppDynamics Controller and an on-premises Events Service cluster. What describes setting up this Events Service cluster?
The Events Service API ports cannot be reconfigured from the default 9080/2081.
The Controller must be able to initiate communication with the Events Service cluster.
The Events Service cluster must be able to initiate communication with the Controller.
There is no need for a load balancer or virtual IP address in front of the Events Service cluster.
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 the conf/events-service-api-store.properties file 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. References: Events Service Deployment, Install the Events Service on Linux, and Install the Events Service on Windows in the AppDynamics documentation.
The AppDynamics Controller is instrumented by an internal, out-of-the-box, AppDynamics Java agent. Which account and user name are used to connectto the Controller to view theinformation provided by the internal AppDynamics agent?
The account is ‘root’ and the user is ‘admin’.
The account is ‘customer!’ and the user is ‘root’.
The account is 'system' and the user is "root.
The account is internal’ and the user is ‘admin’.
The AppDynamics Controller is instrumented by an internal, out-of-the-box, AppDynamics Java agent that monitors the performance and health of the Controller itself1. To access the information provided by the internal agent, you need to log in to the Controller UI with the following credentials2:
The system account is a special account that is used only for internal monitoring and troubleshooting purposes. It is not visible in the normal Controller UI and requires a special URL to access it2. The root user is the default administrator user for the system account and has the same password as the admin user for the customer1 account3. References: Controller Self-Monitoring, Monitoring a Controller Using the Internal Monitoring Agent, Controller Accounts
Which implementation mode should be used when deploying an EUM Server with reverse proxy from a security and performance standpoint in a production environment?
Install the EUM Server on the same host as the Controller, behind the reverse proxy.
Install the EUM Server on a separate host from the Controller, in front of the reverse proxy.
Install the EUM Server on the same host as the Controller, in front of the reverse proxy.
Install the EUM Server on a separate host from the Controller, behind the reverse proxy.
The EUM Server is the on-premises version of the EUM Cloud that receives, processes, and stores data from EUM agents. For production installation, AppDynamics recommends that the EUM Server and the Controller sit on different hosts, and the EUM Server hosts its own MySQL instance. This improves the scalability and performance of both components. Moreover, AppDynamics strongly recommends that SSL traffic from agents to the EUM Server is terminated at a reverse proxy that sits in front of the EUM Server in the network path, and forwards connections to the EUM Server using HTTP. This relieves the SSL processing load from the EUM Server, simplifies the certificate management, and enhances the security by isolating the EUM Server from the external Internet. Therefore, the best implementation mode for deploying an EUM Server with reverse proxy in a production environment is option D. References: EUM Server Deployment, Install a Production EUMServer, Reverse Proxy configuration for EUM, and Browser EUM installation in the AppDynamics documentation and community.
What are three recommended steps to prepare a Linux environment for the installation of an AppDynamics Controller with a Large performance profile? (Choose three.)
Install libaio,
Install MySQL.
Verify the user account has root access,
Verify the open file descriptor limit.
Verify that Java is installed.
Verify the process limit.
To prepare a Linux environment for the installation of an AppDynamics Controller with a Large performance profile, which is suitable for monitoring up to 1000 agents, you need to perform the following steps:
Other steps that are not required but recommended for the Controller installation are verifying the user account permissions, configuring the virus scanners, installing the netstat network utility, and setting the NUMA configuration2. You do not need to install MySQL or Java separately, as they are included in the Controller installation package3. References: Prepare Linux for the Controller, Install the Controller on Linux, and Controller System Requirements in the AppDynamics documentation.
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.
Which data is unavailable in a hybrid deployment of AppDynamics where the AppDynamics Controller and Events Service are installed on-premises and the EUM Server is hosted inAppDynamics' SaaS cloud?
Analytics metrics for End-User Monitoring data sets
End-User Monitoring resource loading times
End-User Monitoring session information
End-User Monitoring browser snapshots
In a hybrid deployment of AppDynamics, where the AppDynamics Controller and Events Service are installed on-premises and the EUM Server is hosted in AppDynamics’ SaaS cloud, the data that is unavailable is the analytics metrics for End-User Monitoring data sets. This is because the analytics metrics require the Events Service to store and process the unstructured data generated by the EUM agents. However, in a hybrid deployment, the EUM Server and the Events Service are not connected, and the EUM Server does not send the EUM data to the Events Service. Therefore, the analytics metrics for EUM data sets, such as browser records, mobile snapshots, network requests, and custom events, are not available in the Controller UI or the Analytics UI1. The other data, such as resource loading times, session information, and browser snapshots, are available in the EUM Server UI, as they are stored and displayed by the EUM Server itself2. References: Hybrid Deployment and EUM Data Sets in the AppDynamics documentation.
Which two user accounts are created by the AppDynamies Controller during installation? (Choose two.)
Elastic search root user
GlassFish asadmin user
Customer-specified Controller administrator account
OS user that will run the controller
REST API user
MySQL appd admin user
The AppDynamics Controller is a Java web application that runs on a GlassFish application server and uses a MySQL database. During the installation of the Controller, two user accounts are created by default:
The other options are not user accounts that are created by the Controller installation. The Elastic search root user, the REST API user, and the MySQL appd admin user are user accounts that are used internally by the Controller components and are not exposed to the end user. The OS user that will run the controller is a user account that you need to create on the host machine before the installation, and it is not created by the Controller installation3. References: Controller Installation, Manage Users and Groups, and Update the Root User and Glassfish Admin Passwords in the AppDynamics documentation.
A Java-based web application was instrumented. The browser snapshots provide a detailed look at an individual page request, however the correlated server-side snapshots are missing for
all requests. What are two reasons for this missing correlated server-side snapshots? (Choose two.)
Server has set the the HitpOnly flag on all cookies.
Correlated server-side snapshots work only for NET Applications.
Correlated snapshots are visible only if the injection mechanism is Automatic.
Correlated snapshots are visible only if browser is Chrome.
Server side application is not instrumented with server agent.
Correlated server-side snapshots are visible only if Java version is 1.7+.
According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the two reasons for the missing correlated server-side snapshots are:
The incorrect options are:
References:
What are three reasons you would create custom events using the Machine Agent REST API? (Choose three.)
to create an event to track application deployment
to create an event to be displayed in a Controller Audit report
to create an alert that is to be triggered when a custom event is created
to create an event to be displayed along with Time Series data in a custom dashboard
to create an event to be used to trigger a health rule violation
to create a new metric
The Machine Agent REST API allows you to create custom events that can be used for various purposes in AppDynamics. Some of the reasons you would create custom events using this API are12:
The user under which the JVM runs must have write privileges to the_________ directories in the Java Agent home. (Choose the correct option to complete the sentence.)
conf and logs
lib and logs
bin and logs
conf and lib
The user under which the JVM runs must have write privileges to the conf and logs directories in the Java Agent home. This is because the conf directory contains the agent configuration files, such as controller-info.xml and agent-config.xml, which may need to be modified or updated by the user. The logs directory contains the agent log files, such as agent.log and agent-errors.log, which are generated by the agent and may need to be accessed or rotated by the user. The user can install the agent as the same user that owns the JVM or as an administrator on the host machine. The user can restrict the remaining contents of the agent directory, such as the lib and bin directories, to read-only access12. References: Install the Java Agent, Java Agent fails to start
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.)
Use the modifyJvmOptions utility provided by AppDynamics.
Define JVM options on the Controller Settings page of the Enterprise Console.
Pass JVM options to the Controller via java -javaagent:“options jar”.
Use the controller.sh script provided by AppDynamics.
Define JVM options manually in the domain. xmi file.
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:
The incorrect options are:
References:
What are three requirements to set up AppDynamics Controllers as a high availability pair? (Choose three.)
Passwordless SSH must be configured between the two Controller servers.
The Controller MySQL database must be installed on a shared location.
The replicate sh script can be run only once.
Both servers must have the Controller software installed prior to setting up high availability.
A unique high availability license file is required for each Controller server.
Both servers must have identical directory structures for the Controller installation.
To set up AppDynamics Controllers as a high availability pair, you need to meet the following requirements1:
Copyright © 2014-2024 CertsTopics. All Rights Reserved