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. https://docs.appdynamics.com/appd/23.x/latest/en/appdynamics-essentials/dashboards-and-reports/custom-dashboards/create-and-manage-custom-dashboards-and-templates

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 logs 1 2   References :  1 :  Request Agent Logs   2 :  Java Agent Logging

Capacity planning is the process of estimating and allocating the resources needed to meet the current and future demands of an application. For a regionally partitioned application, where different users and organizations are assigned to different databases based on their location, capacity planning requires that the administrator monitors the number of users and orgs mapped to each database and ensures that they do not exceed the available resources.

According to the  AppDynamics Analytics - AppDynamics , one way to meet this requirement is to schedule an analytics query to check and report on the result periodically. An analytics query is a SQL-like query that allows you to analyze and visualize the data collected by AppDynamics, such as business transactions, logs, metrics, events, and custom data. You can use analytics queries to create dashboards, widgets, reports, and alerts that provide insights into the performance and behavior of your applications and their components.

To schedule an analytics query to check and report on the number of users and orgs mapped to a database, the administrator can follow these steps:

Go to Analytics > Search.

Select the data source that contains the user and org information, such as Business Transactions, Logs, or Custom Data.

Enter the query that counts the number of users and orgs for each database, such as  SELECT database, COUNT(DISTINCT user), COUNT(DISTINCT org) FROM data_source GROUP BY database .

Click the Save button and enter a name and description for the query.

Click the Schedule button and select the frequency, time range, and recipients for the query execution and report delivery.

Click Save.

Therefore,  A  (Schedule an analytics query to check and report on the result periodically) is the correct answer.  References:

AppDynamics Analytics - AppDynamics

Cisco AppDynamics Associate Administrator Certification

Analytics Queries - AppDynamics

To alert the operations team that a cloud-based application has provisioned a new instance of a JVM, an administrator should create a policy trigger for Discovery > New Node Discovered. This policy trigger will fire an event when a new node is discovered by the AppDynamics Controller, either by auto-discovery or manual registration. The event will contain information such as the node name, tier name, application name, and agent type. The administrator can then configure an action to send an email, SMS, or custom notification to the operations team with the event details. Alternatively, the administrator can also use the built-in alerting feature of the cloud provider to notify the operations team of the new instance creation.

https://docs.appdynamics.com/display/PRO42/Alert+and+Respond

According to the Widgets document 1 , 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.  References :

Widgets

According to the Database Visibility Supported Environments document 1 , Database Visibility can monitor the following databases: PostgreSQL, Cassandra, MongoDB, MySQL, SQL Server, Oracle, Sybase ASE, Sybase IQ, and Couchbase. Therefore, the correct answer is A, B, and D. Derby and DB2 are not supported by Database Visibility.  References :

Database Visibility Supported Environments

Before creating a new database collector, you need to perform the following actions:

Verify the database connection details. You need to provide the host, port, database name, and credentials for the database that you want to monitor.  You also need to select the database type and the collector type 1

Create a database user and set user permissions. You need to create a database user with the minimum required permissions to access the database and run the queries that the Database Agent needs.  You can use the scripts provided by AppDynamics to create the user and grant the permissions 2

References :  1 :  Add Database Collectors   2 :  Database Permissions

According to the Data Collectors document 1 , 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.  References :

Data Collectors

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

Health rules are the criteria that AppDynamics uses to evaluate the performance and availability of your applications and their components. Health rules can trigger alerts and actions when the conditions are violated or cleared. Events are the occurrences that AppDynamics records when something significant happens in your monitored environment, such as a health rule violation, a policy execution, a deployment, or a custom event.

According to the  Health Rules - AppDynamics , the following two ways can help you see the current status of health rules and events of the business process:

Set up a policy to send an email or text when a health rule status changes: This way, you can get notified in real time when a health rule condition is met or cleared, and take appropriate actions to resolve or prevent issues. You can configure policies to send emails, texts, or other notifications to specific recipients or groups, and include relevant information such as the health rule name, the affected entity, the severity level, and the time range.

Create a dashboard with health and events widgets displayed: This way, you can visualize the health and performance of your applications and their components in a single view, and drill down to the details of each health rule or event. You can create custom dashboards with various widgets that show the health status, the event list, the event summary, the event correlation, and the event timeline of your applications and their components.

Therefore,  A  (Set up a policy to send an email or text when a health rule status changes) and  D  (Create a dashboard with health and events widgets displayed) are two ways that can help you see the current status of health rules and events of the business process.  References:

Cisco AppDynamics Associate Administrator Certification

Health Rules - AppDynamics

[Policies and Actions - AppDynamics]

[Events - AppDynamics]

[Custom Dashboards - AppDynamics]