Download Full Version 500-425 Cisco Exam

Metrics are the numerical values that AppDynamics collects and reports to measure the performance and availability of your applications and their components. You can use metrics to create custom dashboards that display the data that is relevant to your needs and interests.

According to the Metrics - AppDynamics, the following two places are where you would find metrics to be added to a custom dashboard:

• The JMX tab on the Node: This tab shows the Java Management Extensions (JMX) metrics that are exposed by the Java Virtual Machine (JVM) or the application server. JMX metrics provide information about the JVM memory, threads, garbage collection, and other aspects of the Java environment. You canadd JMX metrics to a custom dashboard by selecting them from the metric browser tree and dragging them to the dashboard canvas.
• The Metric Browser: This is a tool that allows you to browse, search, and view all the metrics that are available in AppDynamics. The metric browser shows the metrics in a hierarchical tree structure that reflects the logical organization of your applications and their components. You can add metrics to a custom dashboard by selecting them from the metric browser tree and dragging them to the dashboard canvas.

Therefore, C (the JMX tab on the Node) and D (the Metric Browser) are two places where you would find metrics to be added to a custom dashboard. References:

• Metrics - AppDynamics
• Custom Dashboards - AppDynamics
• Cisco AppDynamics Associate Administrator Certification

One possible reason why Java APM agents used in a production environment are consistently found to be disabled while no development environments exhibit this behavior is that the production agents are running out of heap memory and crashing. This can happen if the production agents are monitoring a high volume of business transactions, metrics, or snapshots, and the default heap size is not sufficient to handle the load. To resolve this issue, you can enable the heap-storage-monitor-enabled setting on the agent, which allows the agent to monitor its own heap usage and automatically reduce the amount of data it collects when the heap usage reaches a certain threshold. This can help to prevent the agent from running out of memory and crashing. You can also adjust the heap-storage-monitor-threshold setting to specify the percentage of heap usage that triggers the data reduction1. Alternatively, you can also increase the heap space for the agent by using the -Xmx option in the agent startup script, but this may require more resources from the host machine2.

The other options are not valid solutions to resolve this issue. Enabling agent auto-restart in the controller UI will not prevent the agent from crashing due to heap exhaustion, but only restart the agent after it crashes. This may cause data loss and performance degradation3. Decreasing the worker thread count will not affect the heap usage of the agent, but only limit the number of concurrent tasks that the agent can execute. This may reduce the agent throughput and responsiveness.

https://docs.appdynamics.com/display/PRMY22/Java+Agent

https://docs.appdynamics.com/appd/23.x/latest/en/application-security-monitoring/cisco-secure-application-requirements

By default, the Java Agent enables two Sensitive Data Filters substring: substring “key” and substring “password”. These filters prevent the agent from capturing and sending any data that contains these substrings to the Controller, such as query parameters, HTTP headers, cookies, environment variables, or system properties. This helps to protect sensitive information from being exposed in the Controller UI or reports. You can also add more filters or modify the existing ones by editing the agent configuration file1 References: 1: Filter Sensitive Data

Capacity planning is the process of estimating and allocating the resources needed to meet the current and future demands of an application. For a regionally partitioned application, where different users and organizations are assigned to different databases based on their location, capacity planning requires that the administrator monitors the number of users and orgs mapped to each database and ensures that they do not exceed the available resources.

According to the AppDynamics Analytics - AppDynamics, one way to meet this requirement is to schedule an analytics query to check and report on the result periodically. An analytics query is a SQL-like query that allows you to analyze and visualize the data collected by AppDynamics, such as business transactions, logs, metrics, events, and custom data. You can use analytics queries to create dashboards, widgets, reports, and alerts that provide insights into the performance and behavior of your applications and their components.

To schedule an analytics query to check and report on the number of users and orgs mapped to a database, the administrator can follow these steps:

• Go to Analytics > Search.
• Select the data source that contains the user and org information, such as Business Transactions, Logs, or Custom Data.
• Enter the query that counts the number of users and orgs for each database, such as SELECT database, COUNT(DISTINCT user), COUNT(DISTINCT org) FROM data_source GROUP BY database.
• Click the Save button and enter a name and description for the query.
• Click the Schedule button and select the frequency, time range, and recipients for the query execution and report delivery.
• Click Save.

Therefore, A (Schedule an analytics query to check and report on the result periodically) is the correct answer. References:

• AppDynamics Analytics - AppDynamics
• Cisco AppDynamics Associate Administrator Certification
• Analytics Queries - AppDynamics