500-425 Exam Dumps : Cisco AppDynamics Associate Administrator (CAAA)

Database Visibility provides metrics on the performance of your database and helps troubleshoot performance-related issues. Database Visibility consists of four main components: Database Agent, Collector, Controller, and Events Service (on-premises only). The Database Agent is a standalone Java program that collects performance metrics about your database instances and database servers. The Collector is the process that runs within the Database Agent to collect performance metrics about your database instances and database servers. The Controller is the central interface where you can see all your database instances and database server performance metrics. The Events Service stores high volumes of metric data.

According to the Overview of Database Visibility, the following types of information are sent to the Controller:

• Database-level metrics, such as the number of queries processed and other database statistics
• Names and attributes of all sessions, clients, queries, and other objects on the monitored system

The following types of information are sent to the Events Service:

• Time that each query spends at each wait state
• Individual query statistics for databases that support it
• Information about individual execution plans in databases that support it

Therefore, B (Average Number of Slow Connections) and C (Top Leaked Connections) are two stats that are available in Database Visibility. References:

• Cisco AppDynamics Associate Administrator Certification
• Overview of Database Visibility - AppDynamics
• Database Visibility - AppDynamics

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 logs12 References: 1: Request Agent Logs 2: Java Agent Logging

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.