The default length of time events can be viewed with full detail before being purged is 7 days, unless

archived. Events are records of significant occurrences in the monitored environment, such as errors,

exceptions, policy violations, health rule violations, and more. You can view the events in the

Controller UI under Events > All Events. You can also archive the events to retain them for longer

periods or export them to external systems1 Reference: 1: Events

Thank you for your visit.

Snapshots are the detailed records of the execution of a business transaction, including the call stack,

the exit points, the errors, and the metrics. To locate snapshots showing slow database response, you

can use the following methods:

Go to the list of snapshots and apply a filter based on slow database response: You can access the list

of snapshots from the Business Transaction Dashboard or the Tier Dashboard. You can then apply a

filter to show only the snapshots that have a slow database response time, which is the time spent

by the business transaction in calling the database. You can specify the minimum and maximum

values for the slow database response time, or use the predefined options such as slower than 1

second, slower than 5 seconds, etc. You can also combine this filter with other filters, such as time

range, business transaction name, tier name, node name, etc. to narrow down the results1.

From the flow map, right-click the database icon and select view snapshots: You can access the flow

map from the Application Dashboard, the Business Transaction Dashboard, or the Tier Dashboard.

The flow map shows the graphical representation of the flow of the business transactions, including

the tiers, the nodes, the backends, and the remote services. You can right-click on any database icon

on the flow map and select view snapshots to see the list of snapshots that have called that

database. You can then sort or filter the snapshots by the database response time column to find the

slowest ones2.

The other options are not valid methods to locate snapshots showing slow database response. Going

to the dashboard for the database and selecting slowest database calls will show the metrics and the

flow map for the database, but not the snapshots. Going to the list of snapshots and selecting

analyze for a group of snapshots will show the summary and the comparison of the selected

snapshots, but not the database response time.

https://community.appdynamics.com/t5/Share-a-tip/Snapshots-and-identifying-intermittentissues/td-p/42896

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-andrespond/troubleshoot-health-rule-violations

To create a user in the web user interface, you need to go to Settings > Groups and Roles > Create

User. This option allows you to add a new user account and assign it to one or more groups. You can

also specify the user’s name, email, password, and authentication method1 Reference: 1: Create

Users

When troubleshooting an application using AppDynamics, the fastest way to narrow down a code

problem with a specific business transaction is to follow this order:

Review Application Dashboard: This is the first step to get an overview of the health and

performance of your application and its components. You can see the key metrics, such as response

time, throughput, error rate, and load, for each tier, node, and business transaction. You can also see

the health rule violations, events, and alerts that indicate any issues or anomalies in your

application.

Check transaction scorecard: This is the second step to drill down to the details of a specific business

transaction that you want to troubleshoot. You can see the transaction scorecard by clicking on the

business transaction name on the application dashboard. The transaction scorecard shows the

metrics, such as average response time, calls per minute, errors per minute, and slow calls, for the

selected business transaction. You can also see the breakdown of the response time by tier, node,

and remote service, and the distribution of the response time by percentile.

Check transaction snapshots for problems: This is the third step to identify the root cause of the code

problem for the selected business transaction. You can see the transaction snapshots by clicking on

the View Snapshots button on the transaction scorecard. Transaction snapshots are the detailed

records of the execution of a business transaction, including the call graph, the exit calls, the errors,

the exceptions, the logs, the HTTP parameters, the cookies, the session attributes, and the custom

data. You can use the transaction snapshots to analyze the code execution, the database queries, the

web service calls, the message queues, the errors, and the exceptions that affect the performance of

the business transaction.

Therefore, A (Review Application Dashboard > Check transaction scorecard > Check Transactions

snapshots for problems) is the correct answer. Reference:

Cisco AppDynamics Associate Administrator Certification

Troubleshoot Business Transactions - AppDynamics

Business Transaction - AppDynamics

Transaction Snapshots - AppDynamics