Cisco 500-425 Exam Questions - Navigate Your Path to Success

Correct : A

When troubleshooting an application using AppDynamics, the fastest way to narrow down a code problem with a specific business transaction is to follow this order:

Review Application Dashboard: This is the first step to get an overview of the health and performance of your application and its components. You can see the key metrics, such as response time, throughput, error rate, and load, for each tier, node, and business transaction. You can also see the health rule violations, events, and alerts that indicate any issues or anomalies in your application.

Check transaction scorecard: This is the second step to drill down to the details of a specific business transaction that you want to troubleshoot. You can see the transaction scorecard by clicking on the business transaction name on the application dashboard. The transaction scorecard shows the metrics, such as average response time, calls per minute, errors per minute, and slow calls, for the selected business transaction. You can also see the breakdown of the response time by tier, node, and remote service, and the distribution of the response time by percentile.

Check transaction snapshots for problems: This is the third step to identify the root cause of the code problem for the selected business transaction. You can see the transaction snapshots by clicking on the View Snapshots button on the transaction scorecard. Transaction snapshots are the detailed records of the execution of a business transaction, including the call graph, the exit calls, the errors, the exceptions, the logs, the HTTP parameters, the cookies, the session attributes, and the custom data. You can use the transaction snapshots to analyze the code execution, the database queries, the web service calls, the message queues, the errors, and the exceptions that affect the performance of the business transaction.

Therefore,A(Review Application Dashboard > Check transaction scorecard > Check Transactions snapshots for problems) is the correct answer.Reference:

Cisco AppDynamics Associate Administrator Certification

Troubleshoot Business Transactions - AppDynamics

Business Transaction - AppDynamics

Transaction Snapshots - AppDynamics

Correct : D

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