Cisco AppDynamics Associate Administrator 500-425 CAAA Exam Questions

Answer : D

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 method1Reference:1:Create Users

Answer : A, C

Error configuration is a feature in AppDynamics that allows you to exclude certain types of errors and exceptions from being reported on the dashboard. You can use error configuration to filter out noise and focus on the most relevant and actionable issues.

According to theError Configuration - AppDynamics, the following types of errors and exceptions can be excluded using error configuration:

Database error return codes: These are codes that indicate a problem with the database server, such as 0x80004005 (access denied) or 0x8000005E (access violation). You can exclude these errors from being reported on the dashboard by adding them to the error configuration list.

JavaScript errors: These are errors that occur in the browser due to invalid or malformed JavaScript code, such as syntax errors or reference errors. You can exclude these errors from being reported on the dashboard by adding them to the error configuration list.

Therefore,A(Database error return codes) andC(JavaScript errors) are two options that can be excluded using error configuration.Reference:

Error Configuration - AppDynamics

Cisco AppDynamics Associate Administrator Certification

[Create and Manage Error and Exception Configurations - AppDynamics]

Answer : B

To capture business data for Transaction Analytics, you must first configure a data collector. A data collector is a configuration that specifies what data to capture from a business transaction and how to store it in the analytics platform. You can capture data from HTTP requests, method invocations, custom fields, or information points. You can also apply filters and transformations to the captured data. Once you have configured a data collector, you can use it to enrich the transaction analytics data with business context and enable advanced queries and visualizations

https://docs.appdynamics.com/accounts/en/cisco-appdynamics-saas-deployment-user-management/manage-custom-roles-for-cisco-appdynamics/transaction-analytics-permissions

Answer : C

Percentile metrics are a way to measure the distribution of response times for a Business Transaction. They show the value below which a certain percentage of measurements fall. For example, the 50th percentile metric shows the median response time, and the 99th percentile metric shows the worst-case response time for 99% of the transactions. To enable percentile metrics, you need to go to Configuration > Slow Transaction Thresholds and indicate 5 whole numbers between 1 and 99 as Percentiles to Collect. You can then view the percentile metrics in the Metric Browser under Business Transaction Performance > Business Transactions > <Application Name> > <Business Transaction Name> > Percentiles.

https://docs.appdynamics.com/display/PRO45X/Percentile+Metrics

Answer : A, C

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

Answer : A, D

According to the Upgrade the Java Agent document1, one of the reasons to upgrade AppDynamics agents is to resolve agent issues, such as bugs, performance problems, or compatibility issues with the Controller or the monitored application. Another reason to upgrade AppDynamics agents is to take advantage of new features, such as enhanced metrics, dashboards, alerts, or integrations, that are introduced in newer agent versions. Therefore, the correct answer is A and D. Database issues and application upgrade are not directly related to the agent upgrade, unless they affect the agent functionality or compatibility.Reference:

Upgrade the Java Agent

Answer : C

To determine and configure the exit call to the database, you need to go to Configuration > Instrumentation > Backend Detection > Java. An exit call is a call from an application component to an external service or system, such as a database, a web service, a message queue, or a cache. A backend is a logical representation of an external service or system that receives exit calls from an application component. AppDynamics automatically detects and identifies common types of backends, such as JDBC, HTTP, JMS, and so on.

According to theExit Point Detection Rules - AppDynamics, the following steps are required to determine and configure the exit call to the database:

Go to Configuration > Instrumentation > Backend Detection > Java.

Select the application and the tier that contains the exit call to the database.

Click the Add button to create a new exit point detection rule.

Enter a name and description for the rule.

Select the type of exit call from the drop-down list, such as JDBC, HTTP, JMS, and so on.

Specify the class and method that make the exit call to the database.

Specify the match criteria for the exit call, such as the URL, the query, the host, the port, and so on.

Click Save.

Therefore,C(Configuration > Instrumentation > Backend Detection > Java) is the correct answer.Reference:

Exit Point Detection Rules - AppDynamics

Cisco AppDynamics Associate Administrator Certification

Backends - AppDynamics