Free Cisco AppDynamics Associate Administrator 500-425 Exam Questions

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 theAppDynamics 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 asSELECT 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.Reference:

AppDynamics Analytics - AppDynamics

Cisco AppDynamics Associate Administrator Certification

Analytics Queries - AppDynamics

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.

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

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 Diagnostic Sessions document1, a diagnostic session is a timed session in which AppDynamics captures transaction snapshots for a business transaction at a more frequent interval that you set. In the session, AppDynamics captures full call graphs for the transactions. A diagnostic session can be triggered manually or automatically based on a health rule violation or a threshold of slow or error transactions. A diagnostic session is always associated with a specific business transaction, not all business transactions configured. Therefore, the correct answer is B.Reference:

Diagnostic Sessions

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 systems1Reference:1:Events

Business Transaction metrics are the key performance indicators that measure the health and performance of your applications. They include metrics such as average response time, calls per minute, errors per minute, and so on. You can use various types of performance degradation analysis to identify and troubleshoot the root causes of performance issues using Business Transaction metrics.

According to theTroubleshoot Business Transactions - AppDynamics, the following types of performance degradation analysis are used with Business Transaction metrics:

Correlation Analysis: This type of analysis helps you to find the correlation between different metrics and events that may affect the performance of your Business Transactions. For example, you can use the correlation analysis to see how the response time of a Business Transaction is related to the CPU utilization of a node, or how the error rate of a Business Transaction is related to the number of slow database calls.

Remote Services Analysis: This type of analysis helps you to understand how the performance of your Business Transactions is impacted by the calls to remote services, such as databases, web services, message queues, and so on. For example, you can use the remote services analysis to see the response time, call count, error count, and wait time of each remote service call, and drill down to the details of each call.

Compare Releases: This type of analysis helps you to compare the performance of your Business Transactions across different releases of your application. For example, you can use the compare releases analysis to see how the response time, error rate, and throughput of your Business Transactions have changed after a new deployment, and identify any performance regressions or improvements.

Therefore,A(Correlation Analysis),B(Remote Services Analysis), andE(Compare Releases) are three types of performance degradation analysis that are used with Business Transaction metrics.Reference:

Troubleshoot Business Transactions - AppDynamics

Business Transaction - AppDynamics

Cisco AppDynamics Associate Performance Analyst Certification

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 type1

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 permissions2

The App Server agent configuration GUI allows you to set the configuration for the following agent properties:

Node-name: This property defines the name of the node that appears in the Controller UI.You can use the GUI to change the node name or use auto-naming rules based on environment variables or system properties1

Max-business-transactions per node: This property sets the maximum number of business transactions that can be registered on a node. If the number of business transactions exceeds this limit, the agent stops registering new business transactions and reports them as ''All Other Traffic''.You can use the GUI to increase or decrease this limit2

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-intermittent-issues/td-p/42896