Cisco 500-425 Practice Test - Questions Answers, Page 5

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

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 file1Reference:1:Filter Sensitive Data

The Database Collector's Hardware Monitoring configuration allows you to enable the Database Agent to monitor the server hardware in addition to the database.You can choose from the following operating systems: Linux, Windows, and Solaris1You need to provide the credentials and the connection details for the server that hosts the database1Reference:1:Configure the Database Agent to Monitor Server Hardware

According to the Reports document1, the Report Type field determines what kind of information is captured in the report. There are different report types available, such as Application Health Report, Dashboard Report, Controller Audit Report, and so on. Each report type has different fields in the Report Data tab that can be customized. Therefore, to get the desired information in the report, you need to select the appropriate Report Type from the dropdown menu when creating a scheduled report.Reference:

Reports

Error configuration is a feature in AppDynamics that allows you to exclude certain types of errors and exceptions from being reported on the dashboard. You can use error configuration to filter out noise and focus on the most relevant and actionable issues.

According to theError Configuration - AppDynamics, the following types of errors and exceptions can be excluded using error configuration:

Database error return codes: These are codes that indicate a problem with the database server, such as 0x80004005 (access denied) or 0x8000005E (access violation). You can exclude these errors from being reported on the dashboard by adding them to the error configuration list.

JavaScript errors: These are errors that occur in the browser due to invalid or malformed JavaScript code, such as syntax errors or reference errors. You can exclude these errors from being reported on the dashboard by adding them to the error configuration list.

Therefore,A(Database error return codes) andC(JavaScript errors) are two options that can be excluded using error configuration.Reference:

Error Configuration - AppDynamics

Cisco AppDynamics Associate Administrator Certification

[Create and Manage Error and Exception Configurations - AppDynamics]

Remote Services metrics are the metrics that show the performance and behavior of the external systems that an application interacts with, such as web services, databases, message queues, etc. An AppDynamics administrator can use two locations to view Remote Services metrics: the Tier Dashboard and the Exit Point Metrics. The Tier Dashboard shows the flow map of a tier and its downstream dependencies, including the remote services that the tier calls. The administrator can click on any remote service node on the flow map to see the metrics such as average response time, calls per minute, errors per minute, etc. The Exit Point Metrics show the metrics for all the exit points (remote service calls) of an application, grouped by type, such as HTTP, JDBC, JMS, etc. The administrator can drill down to see the metrics for each exit point, such as the backend name, the tier name, the business transaction name, etc.

To examine the Java App agent logs on a host without login access, you can use the Controller UI to request the agent logs. This feature allows you to download the agent logs from the Controller UI without having to access the host machine.You can specify the log level, the time range, and the file size limit for the logs12Reference:1:Request Agent Logs2:Java Agent Logging

According to the Diagnostic Sessions document1, a diagnostic session is a timed session in which AppDynamics captures transaction snapshots for a business transaction at a more frequent interval that you set. In the session, AppDynamics captures full call graphs for the transactions. A diagnostic session can be triggered manually or automatically based on a health rule violation or a threshold of slow or error transactions. A diagnostic session is always associated with a specific business transaction, not all business transactions configured. Therefore, the correct answer is B.Reference:

Diagnostic Sessions