Free Cram & Latest Exams Dumps

Explanation
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 the Exit 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.
References:
Exit Point Detection Rules – AppDynamics
Cisco AppDynamics Associate Administrator Certification
Backends – AppDynamics

Explanation
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 References: 1: Add Database Collectors 2: Database Permissions

Explanation
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

Explanation
By default, the Java Agent enables two Sensitive Data Filters substring: substring “key” and substring
“password”. These filters prevent the agent from capturing and sending any data that contains these substrings to the Controller, such as query parameters, HTTP headers, cookies, environment variables, or system properties. This helps to protect sensitive information from being exposed in the Controller UI or reports. You can also add more filters or modify the existing ones by editing the agent configuration file1 References: 1: Filter Sensitive Data

Explanation
According to the Widgets document1, 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

Explanation
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 References: 1: Troubleshoot Agent Connectivity 2

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

Explanation
https://docs.appdynamics.com/display/PRO45X/Install+the+Database+Agent
To properly configure a database agent from a zip file, you need to provide the following minimum details:
Controller Host: This is the hostname or IP address of the machine where the Controller is installed. You need to specify this so that the Database Agent can communicate with the Controller and send the collected data1 Controller Port: This is the port number that the Controller listens on for incoming connections. You need to specify this so that the Database Agent can connect to the Controller using the correct protocol. The default ports are 8090 for HTTP and 8181 for HTTPS for on-premise Controllers, and 80 for HTTP and 443 for HTTPS for SaaS Controllers1 Account Access Key: This is the key that authenticates the Database Agent with the Controller. You need to specify this so that the Database Agent can register itself with the Controller and access the license. You can find the account access key in the Controller UI under Settings > License > Account1 Account Name: This is the name of the account that the Database Agent belongs to. You need to specify this so that the Database Agent can associate itself with the correct application and user permissions. You can find the account name in the Controller UI under Settings > License > Account1 References: 1: Install the Database Agent

Explanation
On a custom dashboard, a non-administrator user can view the following types of information:
The company logo: A custom dashboard can display the company logo in the upper left corner of the dashboard. This can help to brand the dashboard and make it more recognizable for the intended audience. The logo can be configured by the dashboard owner or administrator from the dashboard settings1.
The version of the AppDynamics Controller: A custom dashboard can display the version of the AppDynamics Controller in the upper right corner of the dashboard. This can help to identify the Controller that is hosting the dashboard and the features that are available. The version can be configured by the dashboard owner or administrator from the dashboard settings1.
A Timeseries graph: A custom dashboard can display a Timeseries graph widget that shows the trend of a metric over time. This can help to visualize the performance and behavior of the application, server, or database that is being monitored. A Timeseries graph can be configured by the dashboard owner or administrator from the widget settings2.
A non-administrator user cannot view the following types of information on a custom dashboard:
The current weather in Seattle: A custom dashboard cannot display the current weather in Seattle or any other location, as this is not a metric or data point that is reported by AppDynamics agents or the analytics platform. A custom dashboard can only display the data that is collected and stored by AppDynamics2.
The number of AppDynamics licenses consumed: A custom dashboard cannot display the number of AppDynamics licenses consumed, as this is a Controller-level information that is only accessible by the Controller administrator. A custom dashboard can only display the data that is scoped by the dashboard owner’s permissions1 .
https://docs.appdynamics.com/accounts/en/cisco-appdynamics-saas-deployment-user-management/m

Explanation
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 the Troubleshoot 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), and E (Compare Releases) are three types of performance degradation analysis that are used with Business Transaction metrics. References:
Troubleshoot Business Transactions – AppDynamics
Business Transaction – AppDynamics
Cisco AppDynamics Associate Performance Analyst Certification

Explanation
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

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

Explanation
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. References:
Diagnostic Sessions

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

Explanation
Infrastructure monitoring is the feature in AppDynamics that allows you to monitor and troubleshoot the health and availability of the servers that host your applications and their components. Infrastructure monitoring includes metrics such as CPU utilization, memory usage, disk I/O, network traffic, and so on. You can use infrastructure monitoring to detect and resolve the problems that affect the performance and reliability of your servers and applications.
According to the Server Visibility – AppDynamics, the following kind of problem is detected with infrastructure monitoring:
Process level problems: These are the problems that occur at the process level of the server, such as high CPU consumption, memory leaks, excessive disk I/O, or network congestion. You can use infrastructure monitoring to identify the processes that are consuming the most resources, and drill down to the details of each process, such as the command line, the environment variables, the open files, the threads, and the sockets. You can also use infrastructure monitoring to correlate the process level problems with the application performance problems, such as slow response time, high error rate, or low throughput.
Therefore, E (process level problems) is the correct answer. References:
Server Visibility – AppDynamics
Cisco AppDynamics Associate Administrator Certification
Server Monitoring – AppDynamics

Explanation
The main benefit of defining Database Collectors is that you can see which applications are calling a database and how they impact the database performance. Database Collectors enable the Database Agent to collect data from your database instances and database servers, such as metrics, queries, sessions, wait states, and more1 You can also link a database on the application flow maps to a database instance monitored by Database Visibility, which allows you to see the correlation between the application and the database2 References: 1: Add Database Collectors 2: [Link a Database on the Application Flow Map to a Database Instance Monitored by Database Visibility]

Explanation
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