CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Cisco®
  5. 500-430

Free 500-430 Exam Braindumps (page: 6)

Page 5 of 13
PDF with 50 Questions

Which directory should an administrator back up if the goal is to back up the EUM Server?

  1. <eum_server_home= directory
  2. <controller_home=/bin directory
  3. <controller_home>
  4. <controller_home>/bin/eum_server directory

Answer(s): A

Explanation:

The <eum_server_home> directory contains the EUM Server installation files, configuration files, and data files. It is recommended to back up this directory as a precaution before upgrading or migrating the EUM Server. The default location of this directory is <installDir>/AppDynamics/EUM, where <installDir> is the directory where you installed the Controller. You can also use the backup-eum.sh script to back up the EUM Server data.


Reference:

Upgrade the Production EUM Server, Configure the EUM Server



Which framework would require the implementation of custom correlation?

  1. Custom TCP concurrent server
  2. Customer proprietary SOAP application
  3. Vendor-supplied enterprise application that uses JMS
  4. Pre-packaged WCF application

Answer(s): A

Explanation:

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.


Reference:

Custom Correlation for Java Applications and Configure Custom Correlation for .NET Applications in the AppDynamics community.



Which two statements are true regarding the AppDynamics REST API for retrieving metrics? (Choose two.)

  1. Metrics can be retrieved for a fixed time range.
  2. Median is one of the returned values,
  3. End-time value must be provided if using the time-range-type of AFTER_TIME.
  4. Minimum and maximum values are meaningful for all metric types.
  5. Wildcards can be used in the REST API metric path.

Answer(s): A,E

Explanation:

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 data. 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 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.)

  1. Use the modifyJvmOptions utility provided by AppDynamics.
  2. Define JVM options on the Controller Settings page of the Enterprise Console.
  3. Pass JVM options to the Controller via java -javaagent:"options jar".
  4. Use the controller.sh script provided by AppDynamics.
  5. Define JVM options manually in the domain. xmi file.

Answer(s): A,B

Explanation:

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 upgrade. 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 page.
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 behavior.
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 behavior.
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 configuration.


Reference:

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
7: Configuring the WebSphere Application Server - IBM






Post your Comments and Discuss Cisco® 500-430 exam with other Community members:

500-430 Discussions & Posts