500-425: Cisco AppDynamics Associate Administrator

Health Rules are the rules that define the normal or expected behavior of your application, such as the response time, error rate, or CPU utilization of a business transaction, tier, node, or backend. You can create health rules to monitor the performance and availability of your application and its components. When a health rule is violated, it changes the status of the corresponding key performance indicator (KPI) from normal to warning or critical, depending on the severity of the violation. The status change is also represented as an event in the AppDynamics Controller UI, which can trigger alerts, policies, and actions. You can view the health rule events in the Events tab of the application dashboard, or in the Health tab of the entity dashboard.

https://developer.cisco.com/docs/appdynamics/health-rules/

https://university.appdynamics.com/certifications/associate-administrator

According to the Widgets document1, there are various types of widgets that can be used to create visual representations of data in custom dashboards and war rooms. Some of the widget types are:

Flow Map: A flow map widget displays the flow of traffic between different entities, such as applications, tiers, nodes, backends, and so on. You can customize the flow map to show different metrics, filters, and drill-down options.

iFrame: An iFrame widget allows you to embed an external web page or another dashboard within a custom dashboard. You can specify the URL, height, and width of the iFrame widget.

Health List: A health list widget displays the health status of different entities, such as applications, tiers, nodes, business transactions, and so on. You can customize the health list to show different metrics, filters, and drill-down options.

Therefore, the correct answer is A, B, and C. Snapshot and Funnel Analysts are not widget types, but features or tools that can be accessed from other widgets or dashboards.Reference:

Widgets

The option that would solve this the fastest for the customer is to include baseline data within widgets on the dashboard. Baseline data is the data that represents the normal or expected behavior of a metric, based on the historical data collected by the AppDynamics Cognition Engine. By including baseline data within widgets on the dashboard, the customer can easily compare the current value of the metric with the past average value for the same time. For example, if the customer wants to see the number of current database connections on their application in a Timeseries graph, and compare it to the past averages for the same time, they can create a Timeseries graph widget that shows the metric ''Database Connections'' and enable the option ''Show Baseline Data'' in the widget settings.This will display the current and the baseline values of the metric in the same graph, and allow the customer to see the trends and deviations over time1.

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 health rule violation canceled warning event or a health rule violation canceled critical event is generated when the health rule processor can no longer accurately assert that the health rule violation continues to violate or that it has ended1.This can happen when the health rule is edited or disabled, among other reasons1.Adding a new condition to the health rule or disabling the health rule are two actions that would trigger a health rule violation canceled event, as they would change the evaluation criteria or stop the evaluation altogether1.Marking the health rule as canceled or removing the health rule from a policy are not valid actions, as they do not affect the health rule configuration or status

https://docs.appdynamics.com/appd/22.x/22.1/en/appdynamics-essentials/alert-and-respond/troubleshoot-health-rule-violations

Infrastructure monitoring is the feature in AppDynamics that allows you to monitor and troubleshoot the health and availability of the servers that host your applications and their components. Infrastructure monitoring includes metrics such as CPU utilization, memory usage, disk I/O, network traffic, and so on. You can use infrastructure monitoring to detect and resolve the problems that affect the performance and reliability of your servers and applications.

According to theServer Visibility - AppDynamics, the following kind of problem is detected with infrastructure monitoring:

Process level problems: These are the problems that occur at the process level of the server, such as high CPU consumption, memory leaks, excessive disk I/O, or network congestion. You can use infrastructure monitoring to identify the processes that are consuming the most resources, and drill down to the details of each process, such as the command line, the environment variables, the open files, the threads, and the sockets. You can also use infrastructure monitoring to correlate the process level problems with the application performance problems, such as slow response time, high error rate, or low throughput.

Therefore,E(process level problems) is the correct answer.Reference:

Server Visibility - AppDynamics

Cisco AppDynamics Associate Administrator Certification

Server Monitoring - 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