An exception in AppDynamics is a code-level event that indicates a problem or abnormality in the

execution of a business transaction. AppDynamics captures and presents information on exceptions

in the monitored environment, and allows you to configure the rules and criteria for detecting and

reporting exceptions.

According to the Errors and Exceptions - AppDynamics, the following two types of events would be

marked as an exception in AppDynamics:

A custom-configured error method and error message: This is a type of event that you can define as

an exception based on a specific method and message that indicate an error condition in your

application code. You can configure the error detection rules to mark a business transaction as an

error and capture the exception information when such a method and message are encountered. For

example, you can configure a rule to mark a business transaction as an error and capture the

exception when the method com.example.MyClass.myMethod returns the message Invalid input.

Any message that is logged with a severity of Error or Fatal: This is a type of event that AppDynamics

automatically detects as an exception based on the log messages that are generated by your

application code. AppDynamics scans the log messages for the keywords Error or Fatal, and marks

the business transaction as an error and captures the exception information when such a message is

found. For example, AppDynamics will mark a business transaction as an error and capture the

exception when the log message contains Error: Null pointer exception.

Therefore, B (a custom-configured error method and error message) and C (any message that is

logged with a severity of Error or Fatal) are two types of events that would be marked as an

exception in AppDynamics. Reference:

Cisco AppDynamics Associate Administrator Certification

Errors and Exceptions - AppDynamics

Error Detection - AppDynamics

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-usermanagement/manage-custom-roles-for-cisco-appdynamics/transaction-analytics-permissions

According to the Java Memory Leaks document1, one of the ways to detect and troubleshoot Java

memory leaks is to use the Automatic Leak Detection feature on the Memory tab of the Node

Dashboard. This feature captures and analyzes the collections that are actively used and growing in

size over time, indicating a potential memory leak. You can also drill down into the leaking

collections to see the content summary and the access traces that show the code path and the

business transactions that access the collection. Therefore, the correct answer is D. Examining the

values on the Server tab, configuring Object Instance Tracking, or verifying and adjusting the Memory

Monitoring configuration may not directly reveal the source of the memory leak, but they may

provide some useful information or metrics to support the diagnosis. Reference:

Java Memory Leaks

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 > > <Business

Transaction Name> > Percentiles.

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

According to the Cisco AppDynamics Associate Administrator Certification document1, one of the

topics covered in the exam is “Monitor agent performance and connectivity”. To do this, you need to

ensure that the application agent can communicate with the controller, which may require SSL

configuration if the controller is using SSL2. You also need to check that there are enough licenses

available on the controller for the application agent to register and report data3. If the agent is using

the wrong application name or does not have enough memory, it may not start at all or may crash,

which are different problems from not being able to connect to the controller. Reference:

Cisco AppDynamics Associate Administrator Certification

Configure SSL for the Controller and the App Server Agent

License Rules and Restrictions

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

AppDynamics Analytics - AppDynamics

Cisco AppDynamics Associate Administrator Certification

Analytics Queries - AppDynamics

A data collector is used to capture application data in a single business transaction. A data collector is

a configuration that specifies what data to capture from a business transaction and how to store it in

the AppDynamics Controller or 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. The captured data can be used for various purposes, such as

adding context to business transactions, creating custom metrics, triggering health rules, enriching

transaction analytics, or creating business journeys.

https://university.appdynamics.com/certifications/associate-administrator

https://docs.appdynamics.com/appd/22.x/latest/en/application-monitoring/business-transactions

To examine the Java App agent logs on a host without login access, you can use the Controller UI to

request the agent logs. This feature allows you to download the agent logs from the Controller UI

without having to access the host machine. You can specify the log level, the time range, and the file

size limit for the logs12 Reference: 1: Request Agent Logs 2: Java Agent Logging

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

Troubleshoot Business Transactions - AppDynamics

Business Transaction - AppDynamics

Cisco AppDynamics Associate Performance Analyst Certification

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