Pass the Cisco AppDynamics Certified Associate 500-425 Questions and answers with CertsForce

According to the Transaction Thresholds document1, you can set static thresholds for individual business transactions by selecting Individual Transaction Thresholds from the Business Transaction Configuration window. You can then specify the values for Slow, Very Slow, and Stall thresholds for each business transaction. This way, you can customize the thresholds according to the SLA and the expected performance of the long-running transactions. Setting the default thresholds or adjusting the health rules would affect all the business transactions, not just the long-running ones. Therefore, the correct answer is C. References:

Transaction Thresholds

The option that would solve this the fastest for the customer is to include baseline data within widgets on the dashboard. Baseline data is the data that represents the normal or expected behaviorof a metric, based on the historical data collected by the AppDynamics Cognition Engine. By including baseline data within widgets on the dashboard, the customer can easily compare the current value of the metric with the past average value for the same time. For example, if the customer wants to see the number of current database connections on their application in a Timeseries graph, and compare it to the past averages for the same time, they can create a Timeseries graph widget that shows the metric “Database Connections” and enable the option “Show Baseline Data” in the widget settings. This will display the current and the baseline values of the metric in the same graph, and allow the customer to see the trends and deviations over time1.

On a custom dashboard, a non-administrator user can view the following types of information:

The company logo: A custom dashboard can display the company logo in the upper left corner of the dashboard. This can help to brand the dashboard and make it more recognizable for the intended audience. The logo can be configured by the dashboard owner or administrator from the dashboard settings1.

The version of the AppDynamics Controller: A custom dashboard can display the version of the AppDynamics Controller in the upper right corner of the dashboard. This can help to identify the Controller that is hosting the dashboard and the features that are available. The version can be configured by the dashboard owner or administrator from the dashboard settings1.

A Timeseries graph: A custom dashboard can display a Timeseries graph widget that shows the trend of a metric over time. This can help to visualize the performance and behavior of the application, server, or database that is being monitored. A Timeseries graph can be configured by the dashboard owner or administrator from the widget settings2.

A non-administrator user cannot view the following types of information on a custom dashboard:

The current weather in Seattle: A custom dashboard cannot display the current weather in Seattle or any other location, as this is not a metric or data point that is reported by AppDynamics agents or the analytics platform. A custom dashboard can only display the data that is collected and stored by AppDynamics2.

The number of AppDynamics licenses consumed: A custom dashboard cannot display the number of AppDynamics licenses consumed, as this is a Controller-level information that is only accessible by the Controller administrator. A custom dashboard can only display the data that is scoped by the dashboard owner’s permissions1 . https://docs.appdynamics.com/accounts/en/cisco-appdynamics-saas-deployment-user-management/manage-custom-roles-for-cisco-appdynamics/custom-dashboard-permissions

https://docs.appdynamics.com/display/PRO45X/Install+the+Database+Agent

To properly configure a database agent from a zip file, you need to provide the following minimum details:

Controller Host: This is the hostname or IP address of the machine where the Controller is installed. You need to specify this so that the Database Agent can communicate with the Controller and send the collected data1

Controller Port: This is the port number that the Controller listens on for incoming connections. You need to specify this so that the Database Agent can connect to the Controller using the correct protocol. The default ports are 8090 for HTTP and 8181 for HTTPS for on-premise Controllers, and 80 for HTTP and 443 for HTTPS for SaaS Controllers1

Account Access Key: This is the key that authenticates the Database Agent with the Controller. You need to specify this so that the Database Agent can register itself with the Controller and access the license. You can find the account access key in the Controller UI under Settings > License > Account1

Account Name: This is the name of the account that the Database Agent belongs to. You need to specify this so that the Database Agent can associate itself with the correct application and user permissions. You can find the account name in the Controller UI under Settings > License > Account1

References: 1: Install the Database Agent

Two types of information that can be shared without an AppDynamics login are Flow Map and Custom Dashboards. Flow Map is a graphical representation of the application topology, showing the interactions between the tiers, nodes, backends, and remote services. CustomDashboards are user-defined views of the application performance data, metrics, and events. You can share these types of information by generating a shareable link from the Controller UI, which can be accessed by anyone who has the link, without requiring a login12 References: 1: Share a Flow Map 2: Share a Custom Dashboard

Percentile metrics are a way to measure the distribution of response times for a Business Transaction. They show the value below which a certain percentage of measurements fall. For example, the 50th percentile metric shows the median response time, and the 99th percentile metric shows the worst-case response time for 99% of the transactions. To enable percentile metrics, you need to go to Configuration > Slow Transaction Thresholds and indicate 5 whole numbers between 1 and 99 as Percentiles to Collect. You can then view the percentile metrics in the Metric Browser under Business Transaction Performance > Business Transactions > > > Percentiles.

<a href="https://docs.appdynamics.com/display/PRO45X/Percentile+Metrics">https://docs.appdynamics.com/display/PRO45X/Percentile+Metrics

Snapshots are the detailed records of the execution of a business transaction, including the call stack, the exit points, the errors, and the metrics. To locate snapshots showing slow database response, you can use the following methods:

Go to the list of snapshots and apply a filter based on slow database response: You can access the list of snapshots from the Business Transaction Dashboard or the Tier Dashboard. You can then apply a filter to show only the snapshots that have a slow database response time, which is the time spent by the business transaction in calling the database. You can specify the minimum and maximum values for the slow database response time, or use the predefined options such as slower than 1 second, slower than 5 seconds, etc. You can also combine this filter with other filters, such as time range, business transaction name, tier name, node name, etc. to narrow down the results1.

From the flow map, right-click the database icon and select view snapshots: You can access the flow map from the Application Dashboard, the Business Transaction Dashboard, or the Tier Dashboard. The flow map shows the graphical representation of the flow of the business transactions, including the tiers, the nodes, the backends, and the remote services. You can right-click on any database icon on the flow map and select view snapshots to see the list of snapshots that have called that database. You can then sort or filter the snapshots by the database response time column to find the slowest ones2.

The other options are not valid methods to locate snapshots showing slow database response. Going to the dashboard for the database and selecting slowest database calls will show the metrics and the flow map for the database, but not the snapshots. Going to the list of snapshots and selecting analyze for a group of snapshots will show the summary and the comparison of the selected snapshots, but not the database response time.

https://community.appdynamics.com/t5/Share-a-tip/Snapshots-and-identifying-intermittent-issues/td-p/42896

The UniqueHostID agent property is recommended to be used when the machine agent is with multiple app agents on the same machine or when the machine agent is with an app agent on the same machine. This property allows you to specify a unique identifier for the host machine that overrides the default hostname resolution. This helps to avoid conflicts or confusion when multiple agents are running on the same host or when the hostname is not consistent across different agents1 References: 1: How are you able to associate the machine agent with application

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

When you have a custom dashboard that has only one widget, you can delete that widget by clicking the Delete Widget button on the widget properties panel. This will remove the widget from the dashboard, but it will not delete the dashboard itself. You can still view and edit the dashboard from the Controller UI or the Events Service.

According to the Create and Manage Custom Dashboards and Templates - AppDynamics, when you delete a widget from a custom dashboard, AppDynamics does not create a blank widget because empty dashboards are not allowed. Instead, it preserves the existing widgets on the dashboard and displays them in a single row.

Therefore, B (The widget is deleted, but an empty custom dashboard is maintained) is true. References:

Create and Manage Custom Dashboards and Templates - AppDynamics

How to bulk delete custom dashboards using API - Cisco … - AppDynamics

Custom Dashboard Permissions - docs.appdynamics.com