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

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

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

 The default auto-refresh interval for custom dashboards is 120 seconds. This means that the data displayed on the dashboard will be updated every two minutes. The auto-refresh interval can be configured by the dashboard owner or administrator from the dashboard settings. The auto-refresh interval can be set to any value between 15 and 300 seconds, or disabled altogether. The auto-refresh interval applies to all the widgets on the dashboard, unless a widget has its own refresh interval specified.