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

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

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

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. References:

• Diagnostic Sessions