500-430 Exam Dumps : Cisco AppDynamics Professional Implementer(CAPI)

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:

• Account = system
• Username = root
• Password =

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

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 /bin directory and can be run on Linux or Windows platforms. The utility updates the /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 instrumentthe 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 /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.

References:

• 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

According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the two reasons for the missing correlated server-side snapshots are:

• Server has set the HttpOnly flag on all cookies. (A) This is a valid reason because the HttpOnly flag is a security feature that prevents client-side scripts from accessing the cookies. However, the AppDynamics JavaScript Agent relies on the cookies to correlate the browser snapshots with the server-side snapshots. The JavaScript Agent injects a cookie named _appdyn_browser into the browser requests, which contains the correlation information. If the server sets the HttpOnly flag on all cookies, including the _appdyn_browser cookie, the JavaScript Agent cannot read or modify the cookie, and the correlation fails. To enable the correlation, the server should not set the HttpOnly flag on the _appdyn_browser cookie12.
• Server-side application is not instrumented with server agent. (E) This is a valid reason because the server-side snapshots are collected by the AppDynamics app agents that instrument the application servers. The app agents monitor the business transactions that are executed by the server-side application, and capture the execution context, call graphs, errors, and metrics. If the server-side application is not instrumented with the app agent, the server-side snapshots are not available, and the correlation fails. To enable the correlation, the server-side application should be instrumented with the app agent that is compatible with the application server and the Controller34.

The incorrect options are:

• Correlated server-side snapshots work only for .NET Applications. (B) This is not a valid reason because the correlated server-side snapshots work for any application server that is instrumented with the AppDynamics app agent, not only for .NET applications. The AppDynamics platform supports various application servers, such as Java, .NET, PHP, Node.js, Python, and C/C++. The app agents collect the server-side snapshots for the business transactions that are executed by the application server, regardless of the programming language or framework34.
• Correlated snapshots are visible only if the injection mechanism is Automatic. © This is not a valid reason because the correlated snapshots are visible regardless of the injection mechanism. The injection mechanism refers to the way the AppDynamics JavaScript Agent is inserted into the web pages. There are two injection mechanisms: Automatic and Manual. The Automatic injection mechanism uses the app agent to inject the JavaScript Agent into the web pages that are served by the application server. The Manual injection mechanism requires the user to manually insert the JavaScript Agent into the web pages. Both injection mechanisms support the correlation of the browser snapshots and the server-side snapshots, as long as the JavaScript Agent and the app agent are configured correctly .
• Correlated snapshots are visible only if browser is Chrome. (D) This is not a valid reason because the correlated snapshots are visible regardless of the browser. The AppDynamics JavaScript Agent supports various browsers, such as Chrome, Firefox, Safari, Edge, and Internet Explorer. The JavaScript Agent collects the browser snapshots for the web pages that are loaded by the browser, and correlates them with the server-side snapshots, regardless of the browser type or version .
• Correlated server-side snapshots are visible only if Java version is 1.7+. (F) This is not a valid reason because the correlated server-side snapshots are visible regardless of the Java version. The AppDynamics Java Agent supports various Java versions, such as 1.5, 1.6, 1.7, 1.8, and 11. The Java Agent collects the server-side snapshots for the business transactions that are executed by the Java application server, and correlates them with the browser snapshots, regardless of the Java version or vendor .

References:

• 1: Browser Snapshots - AppDynamics
• 2: Troubleshoot Browser RUM - AppDynamics
• 3: Transaction Snapshots - AppDynamics
• 4: Supported Environments and Versions - AppDynamics
• [5]: Browser Real User Monitoring - AppDynamics
• [6]: Set Up and Configure Web EUM - AppDynamics
• [7]: Browser Support - AppDynamics
• [8]: Java Agent - AppDynamics
• [9]: Java Supported Environments - AppDynamics