Cisco AppDynamics Associate Administrator 500-425 CAAA Exam Questions

Answer : A, C

Remote Services metrics are the metrics that show the performance and behavior of the external systems that an application interacts with, such as web services, databases, message queues, etc. An AppDynamics administrator can use two locations to view Remote Services metrics: the Tier Dashboard and the Exit Point Metrics. The Tier Dashboard shows the flow map of a tier and its downstream dependencies, including the remote services that the tier calls. The administrator can click on any remote service node on the flow map to see the metrics such as average response time, calls per minute, errors per minute, etc. The Exit Point Metrics show the metrics for all the exit points (remote service calls) of an application, grouped by type, such as HTTP, JDBC, JMS, etc. The administrator can drill down to see the metrics for each exit point, such as the backend name, the tier name, the business transaction name, etc.

Answer : C

According to the Reports document1, the Report Type field determines what kind of information is captured in the report. There are different report types available, such as Application Health Report, Dashboard Report, Controller Audit Report, and so on. Each report type has different fields in the Report Data tab that can be customized. Therefore, to get the desired information in the report, you need to select the appropriate Report Type from the dropdown menu when creating a scheduled report.Reference:

Reports

Answer : A, C

To confirm that the agent is communicating properly to the controller, you can use the following methods:

Check if data is being written to the agent log in /logs. This indicates that the agent is able to send metrics and events to the controller.You can also look for any errors or warnings in the log file that might indicate a connection issue1

Select Application > Tiers and Nodes > Look for the Node. This shows you the list of nodes that are registered with the controller and their status.You can see if the node is up or down, the agent version, the last reported time, and the machine name2

Answer : B, C

Database Visibility provides metrics on the performance of your database and helps troubleshoot performance-related issues. Database Visibility consists of four main components: Database Agent, Collector, Controller, and Events Service (on-premises only). The Database Agent is a standalone Java program that collects performance metrics about your database instances and database servers. The Collector is the process that runs within the Database Agent to collect performance metrics about your database instances and database servers. The Controller is the central interface where you can see all your database instances and database server performance metrics. The Events Service stores high volumes of metric data.

According to theOverview of Database Visibility, the following types of information are sent to the Controller:

Database-level metrics, such as the number of queries processed and other database statistics

Names and attributes of all sessions, clients, queries, and other objects on the monitored system

The following types of information are sent to the Events Service:

Time that each query spends at each wait state

Individual query statistics for databases that support it

Information about individual execution plans in databases that support it

Therefore,B(Average Number of Slow Connections) andC(Top Leaked Connections) are two stats that are available in Database Visibility.Reference:

Cisco AppDynamics Associate Administrator Certification

Overview of Database Visibility - AppDynamics

Database Visibility - AppDynamics

Answer : D, E

According to the Actions document1, there are four types of standard controller actions that are available to be created: Notification, Diagnostic, Remediation, and JIRA. Each type of action has different subtypes that perform specific tasks. For example, the Notification type includes Email, SMS, and HTTP Request subtypes, while the Diagnostic type includes Thread Dump, Heap Dump, and Diagnostic Session subtypes. Therefore, the correct answer is D and E, as Email and Thread Dump are subtypes of standard controller actions. Resolve, Close Incident, and Undeploy are not standard controller actions, but they may be custom actions that are created by the user or the administrator.Reference:

Actions

Answer : D

According to the Troubleshoot Health Rule Violations document1, one of the ways to troubleshoot health rule violations is to click on the Events tab for the application on the Default Flow Map and then analyze the health rule(s) being violated. This will show you the details of the health rule violation events, such as the affected entity, the severity, the duration, the evaluation time, and the triggered actions. You can also drill down into the health rule violation details to see the health rule configuration, the metric values, and the snapshots. This will help you identify the root cause of the issue and take appropriate remediation actions. Therefore, the correct answer is D. Using the metric browser, disabling the health rule, or rebooting the server may not be the best or the most efficient ways to troubleshoot health rule violations, as they may not reveal the source of the problem, may affect other entities, or may not resolve the issue permanently.Reference:

Troubleshoot Health Rule Violations

Answer : B

The Policy Test Bench gives administrators the ability to test and debug policy execution. It allows you to simulate events and see how the policies and actions respond to them.You can also view the policy execution logs and troubleshoot any issues1Reference:1: Policy Test Bench