Cisco 500-430 Cisco AppDynamics Professional Implementer Online Training

Question #11

Default configuration of the Mobile SDK enables____and_____ . (Choose the two correct options to complete the sentence.)

A . Crash Reports
B . User Data
C . Network Requests
D . Custom Timers
E . Breadcrumbs

Reveal Solution Hide Solution

Question #12

What are two valid reasons for using the REST API to retrieve health rule violations? (Choose two.)

A . For updating an AppDynamics dashboard
B . For determining which actions have been executed
C . When searching for historical events
D . For sending emails
E . When pushing events to the Event Management System is NOT possible

Reveal Solution Hide Solution

Correct Answer: BC
BC

Explanation:

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the REST API for health rule violations allows you to retrieve information about the health rule violations that occurred in a specified time range for a given application1.

You can use the REST API for health rule violations for the following valid reasons:

For determining which actions have been executed (B): The REST API response includes the details of the actions that were triggered by the health rule violation, such as email, SMS, HTTP request, or custom action1. You can use this information to verify if the actions were executed successfully, or to troubleshoot any issues with the action execution.

When searching for historical events ©: The REST API allows you to specify a custom time range for retrieving the health rule violations, such as BEFORE_TIME, AFTER_TIME, BETWEEN_TIMES, or BEFORE_NOW1. You can use this feature to search for historical events that occurred in the past, or to analyze the trends and patterns of the health rule violations over time. The incorrect options are:

For updating an AppDynamics dashboard (A): This is not a valid reason for using the REST API for health rule violations, because the AppDynamics dashboards already display the health rule violations that occurred in the selected time frame, along with the severity, status, affected entities, and actions2. You do not need to use the REST API to update the dashboard, as the dashboard is automatically refreshed with the latest data from the Controller.

For sending emails (D): This is not a valid reason for using the REST API for health rule violations, because the REST API does not send emails directly. The REST API only returns the information about the health rule violations, and the actions that were triggered by them. If you want to send emails based on the health rule violations, you need to configure an email action in the health rule configuration, or use a custom action that invokes an external email service3.

When pushing events to the Event Management System is NOT possible (E): This is not a valid reason for using the REST API for health rule violations, because the REST API does not push events to the Event Management System. The REST API only returns the information about the health rule violations, and the actions that were triggered by them. If you want to push events to the Event Management System, you need to configure an HTTP request action in the health rule configuration, or use a custom action that invokes an external API3.

Reference:

1: Health Rule Violations API – AppDynamics

2: Health Rule Violations – AppDynamics

3: Actions – AppDynamics

Question #13

Which AppDynamics Controller port(s) does the EUM Server require access to in a configuration where the EUM Server and Controller are on separate hosts (split-host configuration)?

A . dedicated EUM HTTP(s) ports
B . GlassFish administration port
C . Controller database and HTTP(s) ports
D . Controller primary HTTP{s) port

Reveal Solution Hide Solution

Question #14

Which two preparatory tasks are required prior to installing an AppDynamics Controller on Linux? (Choose two.)

A . Install JRE.
B . Ensure that MySQL port (3388) is opened.
C . Install SSH.
D . Install libaio.
E . Verify that sufficient temporary (tmp) space is available (at least 1 GB).

Reveal Solution Hide Solution

Question #15

The AppDynamics Controller is instrumented by an internal, out-of-the-box, AppDynamics Java agent.

Which account and user name are used to connect to the Controller to view the information provided by the internal AppDynamics agent?

A . The account is ‘root’ and the user is ‘admin’.
B . The account is ‘customer!’ and the user is ‘root’.
C . The account is ‘system’ and the user is "root.
D . The account is internal’ and the user is ‘admin’.

Reveal Solution Hide Solution

Question #16

What is the correct method to perform a NET Agent upgrade?

A . Perform the agent upgrade on the application server host by running the MSI Installer Package.
B . Perform the agent upgrade on a remote server host by using the AppDynamics Controller REST API.
C . Perform the agent upgrade on the application server host by running the Agent Configuration Utility.
D . Perform the agent upgrade via the AppDynamics Controller Ul.

Reveal Solution Hide Solution

Correct Answer: A
A

Explanation:

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 your account access key for single-tenant Controller accounts. After the installation, you need to restart Windows services and standalone applications.

The incorrect options are:

Perform the agent upgrade on a remote server host by using the AppDynamics Controller REST API.

(B) This is not a valid method for upgrading the NET Agent, because the AppDynamics Controller REST API does not provide any endpoint for agent installation or upgrade. The REST API is mainly used for retrieving or updating configuration data, metrics, events, snapshots, and other information from the Controller3.

Perform the agent upgrade on the application server host by running the Agent Configuration Utility. © This is not a valid method for upgrading the NET Agent, because the Agent Configuration Utility is a tool for modifying the agent configuration after installation, not for installing or upgrading the agent. The Agent Configuration Utility allows you to change the Controller connection settings, the agent logging level, the proxy settings, and other advanced options4.

Perform the agent upgrade via the AppDynamics Controller UI. (D) This is not a valid method for upgrading the NET Agent, because the AppDynamics Controller UI does not provide any feature for agent installation or upgrade. The Controller UI is mainly used for monitoring, analyzing, and troubleshooting the performance of the applications, business transactions, tiers, nodes, and other entities that are instrumented by the agents5.

Reference:

1: Upgrade the .NET Agent for Windows – AppDynamics

2: Release Upgrade Checklist for .NET Agents – AppDynamics

3: REST API – AppDynamics

4: Configure the .NET Agent – AppDynamics

5: AppDynamics Application Performance Monitoring Platform – AppDynamics

Question #17

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

A . <eum_server_home= directory
B . <controller_home=/bin directory
C . <controller_home>
D . <controller_home>/bin/eum_server directory

Reveal Solution Hide Solution

Question #18

Which framework would require the implementation of custom correlation?

A . Custom TCP concurrent server
B . Customer proprietary SOAP application
C . Vendor-supplied enterprise application that uses JMS
D . Pre-packaged WCF application

Reveal Solution Hide Solution

Question #19

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

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

Reveal Solution Hide Solution

Question #20

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

A . Use the modifyJvmOptions utility provided by AppDynamics.
B . Define JVM options on the Controller Settings page of the Enterprise Console.
C . Pass JVM options to the Controller via java -javaagent:“options jar”.
D . Use the controller.sh script provided by AppDynamics.
E . Define JVM options manually in the domain. xmi file.

Reveal Solution Hide Solution

Correct Answer: AB
AB

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

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