Free 500-420 Exam Braindumps
Cisco AppDynamics Associate Performance Analyst Questions 11–15 (page: 4)

Updated On: 9-Feb-2026

What AppDynamics Alert Action does a Performance Analyst need to select to post an AppDynamics event to a third-party collaboration tool?

  1. Make an HTTP Request
  2. Take a thread dump
  3. Create or Update a JIRA Ticket
  4. Run a script or executable on problematic nodes

Answer(s): A

Explanation:

To post an AppDynamics event to a third-party collaboration tool, the Performance Analyst needs to select the "Make an HTTP Request" alert action. This action allows AppDynamics to send an HTTP request to a specified URL, which can be the endpoint provided by the third-party tool's API. This integration capability enables the automatic posting of events, alerts, and notifications from AppDynamics to collaboration tools, enhancing communication and response times to performance issues.


Reference:

AppDynamics documentation on Alert and Respond: Details the various alert actions available within AppDynamics, including the ability to make HTTP requests to integrate with external systems.



Which item supplements business transaction and transaction analytics data with application data?

  1. Demarcation collectors
  2. Netflow data
  3. Data collectors
  4. Endpoint sensors

Answer(s): C

Explanation:

Data collectors in AppDynamics supplement business transaction and transaction analytics data with application data by capturing additional information during transaction execution. This can include method arguments, return values, and invocation context, which enriches the transaction data with more detailed application-level insights. This capability is crucial for in-depth performance analysis and troubleshooting, providing a more comprehensive view of application behavior.


Reference:

AppDynamics documentation on Data Collectors: Explains how to configure data collectors to capture and display detailed application data within business transactions.



A Business Transaction was registered and displayed on the Business Transaction Dashboard. It has continuous load on it. After an hour the Business Transaction stopped being displayed in the Business Transaction Dashboard.
Which action stopped the display of the Business Transaction?

  1. The Business Transaction Lock Down was enabled an hour ago.
  2. The Business Transaction had been deleted an hour ago from the Business Transaction Dashboard.
  3. The Business Transaction Custom Match Rule was deleted an hour ago.
  4. The Business Transaction had been excluded an hour ago from the Business Transaction Dashboard.

Answer(s): C

Explanation:

If a Business Transaction stops being displayed on the Business Transaction Dashboard after continuous load, it could be due to the deletion of the Business Transaction Custom Match Rule. Custom Match Rules in AppDynamics are used to define custom business transactions based on specific criteria. If such a rule is deleted, transactions that were previously identified and displayed based on that rule may no longer be recognized as distinct business transactions, leading to their disappearance from the dashboard.


Reference:

AppDynamics documentation on Business Transactions: Provides insights on configuring and managing business transactions, including the use of custom match rules.



Which two methods are used to plot Host CPU and GC Time Spent in a single view? (Choose two.)

  1. Server tab under "Tiers and Nodes"
  2. JMX tab under "Tiers and Nodes"
  3. Memory tab under Tier and Nodes"
  4. Metrics Browser

Answer(s): B,D

Explanation:

To plot Host CPU and GC (Garbage Collection) Time Spent in a single view, the "JMX tab under 'Tiers and Nodes'" and the "Metrics Browser" are the appropriate methods. The JMX tab provides access to Java Management Extensions (JMX) metrics, including those related to GC time. The Metrics Browser allows for the customization and aggregation of various metrics, including Host CPU usage and GC metrics, enabling a combined view of these critical performance indicators.


Reference:

AppDynamics documentation on Monitoring Tiers and Nodes: Discusses the JMX metrics available for Java applications, including garbage collection details. AppDynamics documentation on the Metrics Browser: Describes how to use the Metrics Browser to view and analyze a wide range of performance metrics.



Which type of Data Collector will capture code data such as method arguments, variables, and return values?

  1. Method Invocation Data Collector
  2. Servlet Container Collector
  3. Transaction Data Collector
  4. URI Data Collector

Answer(s): A

Explanation:

The "Method Invocation Data Collector" is specifically designed to capture code-level data such as method arguments, variables, and return values. This type of data collector enables deep visibility into the execution of methods within transactions, providing valuable insights into the application's behavior and performance. This detailed level of monitoring is essential for diagnosing complex issues and understanding the inner workings of business transactions.


Reference:

AppDynamics documentation on Data Collectors: Details the types of data collectors available, including Method Invocation Data Collectors, and how they can be used to capture detailed code- level data.



Viewing page 4 of 14
Viewing questions 16 - 20 out of 64 questions


Post your Comments and Discuss Cisco 500-420 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!