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

Go to page:

Question # 17

You need to examine the Java App agent logs on a host, but you do not have login access to the relevant host. How do you accomplish this via the Controller User Interface (Ul)?

Controller Ul > Node Dashboard > Agents tab >App Server Agent tab > Agent Operations > Request Agent Logs

Controller Ul > application > Transaction Snapshots > Periodic Collection, then wait for the log to download

Controller Ul > Configuration > Instrumentation > Data Collectors > and then add a new collector for class *.*

Controller Ul > application > Alert Respond > Create Action then issue an HTTP request to request agent logs

Full Access

Question # 18

Which two would be marked as an exception in AppDynamics? (Choose two)

HTTP errors that do not occur in the context of a Business Transaction

a custom-configured error method and error message

any message that is logged with a severity of Error or Fatal

a handled exception after the business transaction terminates

Full Access

Answer:

Explanation:

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: