Explanation To create a user group in AppDynamics, you need to go to Settings > Administration > Groups. A user group is a collection of users who share the same roles and privileges. You can use user groups to manage user access and permissions more easily. You can add, edit, delete, or duplicate user groups from the Groups tab on the Administration page. According to the Manage Users and Groups - AppDynamics, the following steps are required to create a user group: Click the Add button on the Groups tab. Enter a name and description for the group. Select one or more roles for the group from the Available Roles list. You can also create a new role by clicking the Add Role button. Click Save. Therefore, D (Settings > Administration > Groups) is the correct answer. References: Manage Users and Groups - AppDynamics Cisco AppDynamics Associate Administrator Certification User Management - AppDynamics
Question 2
When troubleshooting an application using AppDynamics. which order would help narrow down a code problem with a specific business transaction the fastest?
Correct Answer: A
Explanation 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. References: Cisco AppDynamics Associate Administrator Certification Troubleshoot Business Transactions - AppDynamics Business Transaction - AppDynamics Transaction Snapshots - AppDynamics
Question 3
When creating a scheduled report which field needs to be changed so the desired information is available in the report?
Correct Answer: A
Explanation 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. References: Reports
Question 4
Your organization has defined a set of health rules that accurately represent the business functions of its applications. Which two ways should you help the organization see the current status of health rules and events of the business process? (Choose two.)
Correct Answer: A,D
Explanation 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]
Question 5
Which two conditions would be a reason to update an existing Data Collector? (Choose two.)
Correct Answer: B,D
Explanation According to the Data Collectors document1, 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
