Cisco 500-425 Practice Exam Questions & Answers

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 theErrors 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 methodcom.example.MyClass.myMethodreturns the messageInvalid 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 keywordsErrororFatal, 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 containsError: Null pointer exception.

Therefore,B(a custom-configured error method and error message) andC(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.Reference:

Cisco AppDynamics Associate Administrator Certification

Errors and Exceptions - AppDynamics

Error Detection - AppDynamics

A group can contain multiple roles, which means that the users in the group inherit the permissions of all the roles assigned to the group.For example, you can create a group that has both the Administrator and the Analytics Administrator roles, and the users in that group can perform both the administration and the analytics tasks1Reference:1:Roles and Permissions

According to the Data Collectors document1, a data collector is a configuration that captures application data from a method invocation or an HTTP request. A data collector is associated with a specific method signature or an HTTP parameter name. Therefore, if a new class and method have been deployed to the application, or a new method parameter has been added to an instrumented class, the existing data collector may not match the new code and may need to be updated. However, if the business transaction has been deprecated, or a new HTTP parameter has been added to an existing business transaction, the existing data collector may still work as expected, unless the data collector is specifically configured to filter by the business transaction name or the HTTP parameter value.Reference:

Data Collectors

To find the information that shows the current application, tier, and node that the agent currently reports to, you can go to View my settings > AppDynamics Agents section in the Controller UI. This section shows you the list of agents that are connected to the Controller, along with their status, version, application, tier, and node names.You can also filter the list by agent type, status, or application1Reference:1:AppDynamics Agents

According to the Java Memory Leaks document1, one of the ways to detect and troubleshoot Java memory leaks is to use the Automatic Leak Detection feature on the Memory tab of the Node Dashboard. This feature captures and analyzes the collections that are actively used and growing in size over time, indicating a potential memory leak. You can also drill down into the leaking collections to see the content summary and the access traces that show the code path and the business transactions that access the collection. Therefore, the correct answer is D. Examining the values on the Server tab, configuring Object Instance Tracking, or verifying and adjusting the Memory Monitoring configuration may not directly reveal the source of the memory leak, but they may provide some useful information or metrics to support the diagnosis.Reference:

Java Memory Leaks

To examine the Java App agent logs on a host without login access, you can use the Controller UI to request the agent logs. This feature allows you to download the agent logs from the Controller UI without having to access the host machine.You can specify the log level, the time range, and the file size limit for the logs12Reference:1:Request Agent Logs2:Java Agent Logging

According to the Troubleshoot Health Rule Violations document1, one of the ways to troubleshoot health rule violations is to click on the Events tab for the application on the Default Flow Map and then analyze the health rule(s) being violated. This will show you the details of the health rule violation events, such as the affected entity, the severity, the duration, the evaluation time, and the triggered actions. You can also drill down into the health rule violation details to see the health rule configuration, the metric values, and the snapshots. This will help you identify the root cause of the issue and take appropriate remediation actions. Therefore, the correct answer is D. Using the metric browser, disabling the health rule, or rebooting the server may not be the best or the most efficient ways to troubleshoot health rule violations, as they may not reveal the source of the problem, may affect other entities, or may not resolve the issue permanently.Reference:

Troubleshoot Health Rule Violations