Which two options can be excluded using error configuration? (Choose two.)
AC
Explanation:
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 the
Error 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) and C (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]
Which two locations does an AppDynamics administrator use to view Remote Services metrics?
(Choose two.)
AC
Explanation:
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.
You need to examine the Java App agent logs on a host, but you do not have login access to the
relevant host. How do you accomplish this via the Controller User Interface (Ul)?
A
Explanation:
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
What is the result of starting a Diagnostic Session?
B
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. Reference:
Diagnostic Sessions
You have a custom dashboard that has only one widget Which statement about deleting that widget
is true?
B
Explanation:
When you have a custom dashboard that has only one widget, you can delete that widget by clicking
the Delete Widget button on the widget properties panel. This will remove the widget from the
dashboard, but it will not delete the dashboard itself. You can still view and edit the dashboard from
the Controller UI or the Events Service.
According to the
Create and Manage Custom Dashboards and Templates - AppDynamics
, when you
delete a widget from a custom dashboard, AppDynamics does not create a blank widget because
empty dashboards are not allowed. Instead, it preserves the existing widgets on the dashboard and
displays them in a single row.
Therefore, B (The widget is deleted, but an empty custom dashboard is maintained) is
true. Reference:
Create and Manage Custom Dashboards and Templates - AppDynamics
How to bulk delete custom dashboards using API - Cisco … - AppDynamics
Custom Dashboard Permissions - docs.appdynamics.com
What is the default auto-refresh interval for custom dashboards?
B
Explanation:
The default auto-refresh interval for custom dashboards is 120 seconds. This means that the data
displayed on the dashboard will be updated every two minutes. The auto-refresh interval can be
configured by the dashboard owner or administrator from the dashboard settings. The auto-refresh
interval can be set to any value between 15 and 300 seconds, or disabled altogether. The auto-
refresh interval applies to all the widgets on the dashboard, unless a widget has its own refresh
interval specified.
https://docs.appdynamics.com/appd/23.x/latest/en/appdynamics-
essentials/dashboards-and-reports/custom-dashboards/create-and-manage-custom-dashboards-
and-templates
The App Server agent configuration GUI sets the configuration for which two agent properties?
(Choose two.)
CD
Explanation:
The App Server agent configuration GUI allows you to set the configuration for the following agent
properties:
Node-name: This property defines the name of the node that appears in the Controller UI.
You can
use the GUI to change the node name or use auto-naming rules based on environment variables or
system properties1
Max-business-transactions per node: This property sets the maximum number of business
transactions that can be registered on a node. If the number of business transactions exceeds this
limit, the agent stops registering new business transactions and reports them as “All Other
Traffic”.
You can use the GUI to increase or decrease this limit2
Reference: 1
:
Node Naming 2
:
Configure Business Transaction Limits
A customer complains that their dashboard is broken They tell you that every time they change the
time range using the time picker, the data on several of their dashboard widgets do not change to
match the new time range What is happening in this situation?
C
Explanation:
According to the Time Range Comparisons document1
, you can use the Compare Time Range feature
in Dash Studio to compare two time periods on a widget. However, this feature also means that the
widget may not use the global time range set for the entire dashboard by default. Instead, the widget
may use its own time range (denoted as T1) and a second time range (denoted as T2) for
comparison. Therefore, if the customer changes the time range using the time picker, the data on the
widget may not change accordingly, unless they also update the widget’s time range settings. To fix
this problem, the customer can either disable the Compare Time Range feature or adjust the
widget’s time range to match the global time range. Reference:
Time Range Comparisons
If you clear the "Mark Business Transaction as error" checkbox under Configuration >
Instrumentation > Error Detection, which two statements are true? (Choose two)
AB
Explanation:
The Mark Business Transaction as Error checkbox under Configuration > Instrumentation > Error
Detection allows you to control whether a business transaction is reported as an error or not. If you
clear this checkbox, the business transaction will not be marked as an error and will not affect the
error count metrics.
According to the
Error Detection: Mark Business Transaction as Error - AppDynamics
, the following
statements are true when you clear this checkbox:
The transaction is included in Response Time metrics: This means that the transaction will still
contribute to the response time metric, which measures the average time it takes for a request to be
completed by AppDynamics. However, it will not affect other response time metrics, such as First
Response Time or Average Time to First Byte.
The transaction is added to error count metrics: This means that the transaction will still count
towards the error count metric, which measures the number of transactions that have failed due to
errors. However, it will not affect other error count metrics, such as Error Rate or Error Percentage.
Therefore, A (The transaction is included in Response Time metrics) and B (The transaction is added
to error count metrics) are true. Reference:
Error Detection: Mark Business Transaction as Error - AppDynamics
Business Transaction - AppDynamics
Error Detection - AppDynamics
To capture business data for Transaction Analytics what must be configured first?
B
Explanation:
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