Cisco AppDynamics Associate Administrator 500-425 Exam Questions with Experts Answers Updated Recently

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

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

An exception in AppDynamics is a code-level event that indicates a problem or abnormality in the execution of a business transaction. AppDynamics captures and presents information on exceptions in the monitored environment, and allows you to configure the rules and criteria for detecting and reporting exceptions.

According to the Errors and Exceptions - AppDynamics, the following two types of events would be marked as an exception in AppDynamics:

• A custom-configured error method and error message: This is a type of event that you can define as an exception based on a specific method and message that indicate an error condition in your application code. You can configure the error detection rules to mark a business transaction as an error and capture the exception information when such a method and message are encountered. For example, you can configure a rule to mark a business transaction as an error and capture the exception when the method com.example.MyClass.myMethod returns the message Invalid input.
• Any message that is logged with a severity of Error or Fatal: This is a type of event that AppDynamics automatically detects as an exception based on the log messages that are generated by your application code. AppDynamics scans the log messages for the keywords Error or Fatal, and marks the business transaction as an error and captures the exception information when such a message is found. For example, AppDynamics will mark a business transaction as an error and capture the exception when the log message contains Error: Null pointer exception.

Therefore, B (a custom-configured error method and error message) and C (any message that is logged with a severity of Error or Fatal) are two types of events that would be marked as an exception in AppDynamics. References:

• Cisco AppDynamics Associate Administrator Certification
• Errors and Exceptions - AppDynamics
• Error Detection - AppDynamics