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 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

According to the Upgrade the Java Agent document1, one of the reasons to upgrade AppDynamics agents is to resolve agent issues, such as bugs, performance problems, or compatibility issues withthe Controller or the monitored application. Another reason to upgrade AppDynamics agents is to take advantage of new features, such as enhanced metrics, dashboards, alerts, or integrations, that are introduced in newer agent versions. Therefore, the correct answer is A and D. Database issues and application upgrade are not directly related to the agent upgrade, unless they affect the agent functionality or compatibility. References:

• Upgrade the Java Agent