[2026] Pass 500-420 Exam - Real Questions and Answers
500-420 Exam Questions Get Updated [2026] with Correct Answers
NEW QUESTION # 35
When a team of developers refactored their code, resulting in class-name changes, Business iQ users reported that metrics had disappeared. Where should a Performance Analyst look to troubleshoot this problem?
- A. Databases > Configuration > Collectors
- B. Applications > Troubleshoot > Errors
- C. Configuration > Slow Transaction Thresholds
- D. Configuration > Instrumentation > Data Collectors
Answer: D
Explanation:
The Performance Analyst should review Configuration > Instrumentation > Data Collectors. Business iQ commonly depends on transaction data collected from application code, including values obtained through method invocation data collectors. These collectors can be configured against specific class names, method names, method arguments, return values, object properties, or getter chains.
When developers refactor code and rename or relocate classes, an existing data collector may no longer match the instrumented method. As a result, the expected business data is not captured, and the related Business iQ fields, measures, or metrics can disappear from analytics views even though the application continues processing transactions.
The analyst should verify the configured class and method signatures, confirm that the new classes are instrumented, update any affected getter chains, and validate collection through new transaction snapshots or Analytics data.
The Errors page focuses on application exceptions, while Slow Transaction Thresholds controls performance classifications. Database collectors configure Database Visibility connections and are unrelated to application- code refactoring.
Relevant CAAPA Study Guide topics include Business iQ, Analytics Data Collection, Method Invocation Data Collectors, Class and Method Matching, Getter Chains, Instrumentation Configuration, and Transaction Snapshot Validation.
NEW QUESTION # 36
What AppDynamics Alert Action does a Performance Analyst need to select to post an AppDynamics event to a third-party collaboration tool?
- A. Create or Update a JIRA Ticket
- B. Make an HTTP Request
- C. Run a script or executable on problematic nodes
- D. Take a thread dump
Answer: B
Explanation:
The correct action is Make an HTTP Request. AppDynamics uses HTTP Request actions to send event information to external systems that expose a REST API, webhook, or other HTTP-based integration endpoint. A Performance Analyst can configure the destination URL, HTTP method, headers, authentication, and request body, then include AppDynamics event variables in the payload.
This allows a health rule violation, policy trigger, or other supported event to be posted directly into a third- party collaboration platform. The external tool can then display the alert in a channel, notify an operations team, or initiate its own workflow.
Create or Update a JIRA Ticket is intended specifically for issue-tracking integration rather than general collaboration-platform messaging. Take a thread dump is a diagnostic action used to capture application thread activity. Run a script or executable on problematic nodes is a remediation action and does not directly post an event to an external collaboration service.
Relevant CAAPA Study Guide topics include Policies, Alert Actions, HTTP Request Actions, Webhook Integrations, Event Templates, Health Rule Violations, and Third-Party Notification Workflows.
NEW QUESTION # 37
If a user request results in the discovery of an entry point, what is the one key item that must be defined as one or more asynchronous activities are spawned?
- A. Business Transaction
- B. Endpoint Metrics
- C. Custom Endpoint
- D. Asynchronous Metric
Answer: A
Explanation:
A Business Transaction must be defined when a discovered entry point initiates one or more asynchronous activities. The Business Transaction establishes the logical monitoring context for the original user request and enables AppDynamics to associate subsequently spawned asynchronous work with that request.
When asynchronous processing occurs, execution may continue on different threads, task executors, queues, or callback mechanisms after the initiating thread has completed or moved on. AppDynamics propagates the Business Transaction correlation context across these asynchronous boundaries so the resulting activity can be represented as part of the same end-to-end transaction. This allows the analyst to evaluate total response time, asynchronous segments, downstream calls, errors, and call-graph execution in the proper transaction context.
A Custom Endpoint is not required merely because asynchronous work is spawned. Asynchronous metrics and endpoint metrics are measurements generated from monitoring; they do not establish the identity or correlation boundary of the request.
Relevant CAAPA Study Guide topics include Business Transaction Discovery, Entry Points, Asynchronous Transaction Tracking, Thread Handoffs, Transaction Correlation, Call Graphs, and End-to-End Transaction Visibility.
NEW QUESTION # 38
Which statement is true for shared AppDynamics Dashboards?
- A. Users are required to log in to their AppDynamics account and be inside the organization network.
- B. Users are required to have administrator access to the Controller.
- C. Users are required to log in to their AppDynamics account.
- D. Users are not required to be logged in to their AppDynamics account.
Answer: D
Explanation:
A shared AppDynamics dashboard can be published through a shareable URL that allows viewers to access the dashboard without logging in to an AppDynamics account. This capability is intended for distributing operational or business-performance information to stakeholders who do not require full Controller access, such as support teams, management, or external display systems.
The dashboard owner controls whether the dashboard is shared and which information is exposed. Shared access is generally read-only, so unauthenticated viewers can examine the dashboard's widgets and current data but cannot modify its configuration, create monitoring rules, or access unrelated areas of the Controller.
Administrator access is not required merely to view a shared dashboard. Likewise, authenticated AppDynamics access is not mandatory when the dashboard has been explicitly published for external or public viewing. Network restrictions may still apply at the organization, proxy, firewall, or Controller-hosting level, but they are deployment controls rather than an AppDynamics login requirement for the shared dashboard itself.
Relevant CAAPA Study Guide topics include Custom Dashboards, Dashboard Sharing, Shareable URLs, Read-Only Access, Controller Permissions, and Role-Based Access Control.
NEW QUESTION # 39
A development team responsible for the front-end shopping application has asked to receive an email every time the Java container thread count exceeds 25. Which alert and response capabilities settings will provide the email?
- A. Node Health - JMX Thread Pools (> Baseline) + Notification Action (Send an Email)
- B. Node Health - Thread Pools (> Specific Value) + Notification Action (Send an Email)
- C. Node Health - Thread Pools (> Specific Value) + Notification Action (Custom Action)
- D. Node Health - JMX Thread Pools (> Specific Value) + Notification Action (Send an Email)
Answer: B
Explanation:
In AppDynamics, you can create health rules to monitor various metrics and set up actions based on the thresholds defined for these metrics. For monitoring Java container thread counts, you can set a health rule based on Node Health - specifically on thread pools - to trigger when the thread count exceeds a specific value. The Notification Action can then be configured to send an email to the development team whenever this threshold is breached.
References:
AppDynamics documentation on Health Rules:
https://docs.appdynamics.com/21.6/en/infrastructure-visibility/health-rules
NEW QUESTION # 40
Which two views can a Controller-level custom dashboard provide? (Choose two.)
- A. Aggregate and compare data from different applications on the same Controller
- B. Show a single view of only historical data.
- C. A customized view of applications, servers, and database performance data
- D. Aggregate and compare data from only a single application on the same Controller
Answer: A,C
Explanation:
Controller-level custom dashboards in AppDynamics have the flexibility to provide views that aggregate and compare data from different applications on the same Controller, as well as offer a customized view of applications, servers, and database performance data. This capability enables a holistic view of the IT environment, facilitating cross-application insights and the ability to correlate performance across different layers of the technology stack. Such dashboards are invaluable for understanding overarching trends, pinpointing systemic issues, and driving informed decision-making across multiple applications and infrastructure components.
References:
AppDynamics documentation on Custom Dashboards: Provides detailed instructions on creating and customizing dashboards at the Controller level, including the aggregation and comparison of data from various sources.
AppDynamics documentation on Controller UI: Explains the functionalities available within the Controller UI, including the creation of comprehensive dashboards that encompass application, server, and database metrics.
NEW QUESTION # 41
A client needs to reference a metric from different applications on an AppDynamics dashboard. Which of the following is true?
- A. Metrics from different applications cannot be cross referenced or combined on an AppDynamics dashboard
- B. Metrics from different applications can be cross referenced on an AppDynamics dashboard
- C. Metrics from different applications can be cross referenced but cannot be combined in a single dashboard
- D. Metrics from different applications cannot be cross referenced on an AppDynamics dashboard
Answer: B
Explanation:
In AppDynamics, metrics from different applications can indeed be cross-referenced on a single dashboard.
This allows for a more holistic view of an organization's application ecosystem, facilitating the comparison and correlation of performance metrics across different applications within the same AppDynamics controller.
References:
AppDynamics documentation on Custom Dashboards: Details how to create custom dashboards that can include metrics from multiple applications, enabling cross-referencing and comprehensive performance monitoring.
NEW QUESTION # 42
What does the Live Preview option in a Business Transaction Discovery Session allow a user to do?
- A. Stream entry points in your application
- B. Provide streaming logs from the application agent
- C. Search classes and methods currently running on the system
- D. See if new Transaction Discovery Rules work
Answer: D
Explanation:
The Live Preview option in a Business Transaction Discovery Session in AppDynamics allows a user to verify the effectiveness of newly configured Transaction Discovery Rules. This feature provides real-time feedback on how these rules identify and categorize business transactions, enabling users to adjust and fine-tune the rules to ensure accurate and meaningful transaction monitoring.
References:
AppDynamics documentation on Business Transaction Management: Includes information on Business Transaction Discovery Sessions and the use of Live Preview to validate Transaction Discovery Rules.
NEW QUESTION # 43
A Performance Analyst notices an increase in Business Transaction error rate that is much higher than normal alerts. The Performance Analyst can see these are related to the Health Rules defined for the Shopping Service that is monitored with AppDynamics Browser RUM. While troubleshooting the Performance Analyst wants details on which Browsers and Devices are affected. Which section of the Browser App Dashboard will provide this detail for a given time period?
- A. Overview
- B. Pages & Ajax Requests
- C. Sessions
- D. Usage Stats
Answer: D
Explanation:
In the Browser Real User Monitoring (RUM) Dashboard, the Usage Stats section provides insights into user demographics, including the types of browsers and devices they are using. This section would help the Performance Analyst understand which browsers and devices are affected during a specific time period when there has been an increase in the Business Transaction error rate.
References:
AppDynamics documentation on Browser RUM:
https://docs.appdynamics.com/21.6/en/end-user-monitoring/browser-monitoring/browser-real-user-monito
NEW QUESTION # 44
Which type of Data Collector will capture code data such as method arguments, variables, and return values?
- A. URI Data Collector
- B. Method Invocation Data Collector
- C. Servlet Container Collector
- D. Transaction Data Collector
Answer: B
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.
References:
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.
NEW QUESTION # 45 
Refer to the exhibit. The transaction score in the graphic displays an interesting performance pattern outside of business hours on 6/16/18. Which additional performance anomaly should be of most interest to a Performance Analyst?
- A. Lower than usual volume at 6/17/18
- B. Elevated Response Time at 6/25/18
- C. Elevated Response Time at 6/19/18
- D. Low volume at 6/15/18
Answer: C
Explanation:
The performance pattern outside of business hours on 6/16/18 that would be of most interest to a Performance Analyst is the elevated response time, as indicated on 6/19/18. This is because it shows a significant spike in response time, which could indicate a performance issue that needs to be addressed. Anomalies in response time can often be more indicative of underlying problems than changes in call volume, especially when they occur outside of expected peak periods.
References:
AppDynamics documentation on Transaction Score:
https://docs.appdynamics.com/latest/en/application-monitoring/application-dashboard/transaction-score
NEW QUESTION # 46
In which two features of AppDynamics can Information Points metric data be used? (Choose two.)
- A. Flow Maps
- B. Custom Dashboards
- C. Analytics
- D. Alerting
Answer: B,D
Explanation:
Information Points in AppDynamics are custom metrics that track specific data within your applications, such as method invocations or the value of method arguments. These metrics can be utilized in various features of AppDynamics, most notably in "Alerting" and "Custom Dashboards." Alerting allows you to set up notifications based on the thresholds set for Information Points, ensuring that teams are promptly informed about significant changes or anomalies. Custom Dashboards enable the visualization of Information Points metrics alongside other key performance indicators, providing a comprehensive view of application health and performance tailored to specific needs.
References:
AppDynamics documentation on Information Points: Explains how to create and use Information Points to monitor specific business-relevant metrics.
AppDynamics documentation on Alerting: Details the process of setting up health rules and alerts based on various metrics, including those from Information Points.
AppDynamics documentation on Custom Dashboards: Guides on how to create dashboards that incorporate a wide range of metrics, including Information Points, for customized monitoring.
NEW QUESTION # 47
Which option is a prerequisite for installing the AppDynamics Database Agent?
- A. The database host is reachable from the agent host.
- B. The database administrator dropped system table keys.
- C. The TCP queue's tcp_max_syn_backlog is sized correctly.
- D. The data architect has reviewed the most frequently used primary keys.
Answer: A
Explanation:
The database host must be reachable from the Database Agent host. The AppDynamics Database Agent normally runs as a standalone process and connects remotely to monitored database instances. Before installation and configuration, the agent host therefore requires network connectivity to each target database over the appropriate database listener port.
This prerequisite includes successful hostname or IP resolution, routing, firewall access, and permission for the agent host to establish a TCP connection to the database service. The Database Agent also requires valid monitoring credentials with the database-specific permissions needed to collect performance statistics, sessions, waits, queries, and other diagnostic data.
Reviewing frequently used primary keys is a database-design activity and is unrelated to agent installation.
Adjusting tcp_max_syn_backlog is an operating-system network-tuning task, not a standard Database Agent prerequisite. Dropping system-table keys would be unnecessary and potentially damaging; AppDynamics monitoring does not require destructive changes to database system objects.
Relevant CAAPA Study Guide topics include Database Visibility Architecture, Database Agent Deployment, Network Connectivity Requirements, Database Collector Configuration, Listener Ports, and Monitoring User Permissions.
NEW QUESTION # 48
A Performance Analyst is reviewing Business Transactions with an application team. The application team wants to increase the Application Business Transaction limit because it needs visibility into all the different transactions. What should the Performance Analyst do?
- A. Increase the limit halfway between the current level and the requested value
- B. Focus on the Business Transactions exceeding the limit and determine why
- C. Increase the limit to the requested value
- D. Do nothing because the limit is not important during configuration
Answer: B
Explanation:
The Performance Analyst should first investigate the Business Transactions exceeding the configured limit and determine why so many unique transactions are being registered. Business Transaction limits protect the Controller from excessive metric creation, unnecessary cardinality, and degraded monitoring performance.
A high transaction count is often caused by overly granular transaction naming, dynamic URL segments, request parameters, identifiers, or automatic discovery rules that create a separate Business Transaction for each variation. The analyst should review All Other Traffic, transaction detection rules, naming rules, and the entry points generating excessive registrations. Low-value traffic such as health checks, static resources, or framework-generated requests can be excluded, while related requests can be grouped or split more deliberately through Custom Match Rules.
Increasing the limit without correcting the underlying detection behavior may only postpone the problem and increase Controller resource consumption. The limit should be raised only after the transaction model has been validated and a genuine business requirement remains.
Relevant CAAPA Study Guide topics include Business Transaction Limits, All Other Traffic, Transaction Detection Rules, Custom Match Rules, Exclude Rules, Transaction Naming, and Metric Cardinality Management.
NEW QUESTION # 49
A Performance Analyst is creating a custom baseline and attempting to tag it to a widget in a dashboard.
Which statement is true?
- A. The custom baseline can be created but not tagged to a widget in a dashboard.
- B. The custom baseline can be created and tagged to a widget in a dashboard.
- C. The custom baseline cannot be created or tagged to a widget in a dashboard.
- D. Custom baselines are not supported in AppDynamics.
Answer: A
Explanation:
AppDynamics supports the creation of custom baselines, allowing a Performance Analyst to define expected metric behavior over a selected historical period and recurring time pattern. Custom baselines are useful when the standard daily, weekly, or trend-based baselines do not accurately represent the application's operating schedule, seasonal demand, or business cycle.
However, a custom baseline cannot be directly tagged or bound to an individual dashboard widget. Dashboard widgets can visualize metrics and, depending on the widget type, may display standard comparison or baseline-related information, but they do not provide a mechanism for associating a specifically named custom baseline with that widget.
Custom baselines are primarily applied in monitoring and evaluation contexts such as health-rule conditions, where current metric values can be compared against expected behavior using defined baseline criteria and standard deviations. Therefore, the baseline itself can be created and used for performance evaluation, but the analyst's attempt to attach it directly to a dashboard widget is unsupported.
Relevant CAAPA Study Guide topics include Dynamic Baselines, Custom Baseline Configuration, Health Rule Conditions, Baseline Evaluation, Metric Visualization, and Custom Dashboard Widget Limitations.
NEW QUESTION # 50
Business users of an e-commerce site want to see the running aggregate checkout value stored in the Java class Checkout. How would a Performance Analyst capture this data?
- A. Create an HTTP data collector
- B. Create a dashboard widget to total Business Transactions
- C. Export the data hourly with a REST call
- D. Create a method invocation data collector
Answer: D
Explanation:
A method invocation data collector is used because the required business value exists inside the Java application's Checkout class rather than in the HTTP request.
The Performance Analyst configures the collector against the appropriate class and method, then identifies the value through a method argument, return value, object field, or getter chain. AppDynamics captures that checkout value when the configured method executes and associates it with the corresponding Business Transaction data. The collected value can subsequently be used for business analysis and aggregation, allowing stakeholders to report total or running checkout value over a selected time period.
A dashboard widget can visualize or aggregate data that AppDynamics already collects, but it cannot independently extract a value from Java code. An HTTP data collector is appropriate only when the required value is contained in request parameters, headers, cookies, session attributes, or other HTTP data. A REST export retrieves existing Controller data and therefore does not solve the initial instrumentation requirement.
Relevant CAAPA Study Guide topics include Method Invocation Data Collectors, Java Class and Method Instrumentation, Getter Chains, Business Data Collection, Transaction Analytics, and Custom Dashboard Visualization.
NEW QUESTION # 51
Which format is used to archive dashboard metadata?
- A. Dashboard metadata can be archived as JSON.
- B. Dashboard metadata can be archived as a PDF.
- C. Dashboard metadata can be archived as an XLSX.
- D. Dashboard metadata can be archived as a CSV.
Answer: A
Explanation:
AppDynamics dashboard metadata is archived in JSON format. JSON preserves the dashboard's structural and configuration information, including widget definitions, layout, metric references, display settings, data sources, labels, and other properties required to reconstruct the dashboard.
This format is appropriate because dashboard metadata is hierarchical configuration data rather than a flat report. A JSON archive can retain nested relationships among dashboard objects and can be exported, stored in source control, transferred between compatible Controller environments, or used as part of backup and migration procedures.
PDF is intended for rendering a visual report and does not preserve editable dashboard configuration. CSV and XLSX are tabular formats suitable for exporting metric or report data, but they cannot accurately represent the complete object structure and layout of a custom dashboard.
Therefore, when the objective is to archive the dashboard definition itself rather than merely capture its displayed output, JSON is the correct format.
Relevant CAAPA Study Guide topics include Custom Dashboards, Dashboard Import and Export, Metadata Archiving, JSON Configuration, Controller Migration, and Dashboard Backup Procedures.
NEW QUESTION # 52
What must a Performance Analyst first configure in order to monitor end-to-end latency performance metrics in AppDynamics?
- A. slow end-point identity markers
- B. additional demarcator methods
- C. define the end-to-end latency transaction
- D. endpoints for asynchronous transactions
Answer: C
Explanation:
To monitor end-to-end latency performance metrics, a Performance Analyst must first define the end-to-end latency transaction. This involves configuring the business transactions to include the necessary entry and exit points that capture the complete flow of the transaction, thereby enabling the measurement of the total latency.
References:
AppDynamics documentation on Business Transactions:
https://docs.appdynamics.com/latest/en/application-monitoring/business-transactions
NEW QUESTION # 53
Which option should a Performance Analyst use in an environment where virtual machines are routinely created and destroyed?
- A. -Dappdynamics.agent.auto.node.prefix and -Dappdynamics.cron.vm
- B. -Dappdynamics.http.proxyHost and -Dappdynamics.http.proxyUser
- C. -Dappdynamics.agent.reuse.nodeName and -Dappdynamics.agent.reuse.nodeName.prefix
- D. -Dappdynamics.agent.node.metainfo and -Dappdynamics.agent.nodeName
Answer: C
Explanation:
In an elastic environment where virtual machines are frequently provisioned and terminated, the Performance Analyst should enable node-name reuse by using -Dappdynamics.agent.reuse.nodeName together with - Dappdynamics.agent.reuse.nodeName.prefix.
The reuse setting allows an Application Agent to register against an available historical node identity rather than continually creating a new node record each time a replacement virtual machine starts. The prefix groups reusable node names for a particular tier, service, or deployment pool, ensuring that agents select node identities from the correct logical set. This prevents excessive node proliferation in the Controller and preserves cleaner historical monitoring for short-lived infrastructure.
A typical configuration enables reuse and supplies a stable prefix, for example:
-Dappdynamics.agent.reuse.nodeName=true
-Dappdynamics.agent.reuse.nodeName.prefix=checkout-node
Proxy properties only control Controller connectivity through an HTTP proxy. Node metadata and a fixed node name do not provide controlled reuse across an automatically scaling pool.
Relevant CAAPA Study Guide topics include Dynamic and Elastic Environments, Node Name Reuse, Application Agent Registration, Tier and Node Configuration, and Controller Node Management.
NEW QUESTION # 54
What is the Node limit of the maximum Service Endpoints per node?
- A. 0
- B. 1
- C. 2
- D. 3
Answer: B
Explanation:
AppDynamics imposes a limit on the number of Service Endpoints that can be registered per node to ensure manageable performance and overhead. The limit per node is set to 100 Service Endpoints, which is a balance between providing detailed monitoring and maintaining application performance.
References:
AppDynamics documentation on Service Endpoints:
https://docs.appdynamics.com/latest/en/application-monitoring/monitor-service-endpoints
NEW QUESTION # 55
......
Cisco 500-420 exam is intended for individuals who have a basic understanding of application performance management, including application monitoring, troubleshooting, and tuning. 500-420 exam validates your ability to install, configure, and manage Cisco AppDynamics, and provides a foundation for implementing more advanced APM practices.
Cisco 500-420 exam consists of 55-65 multiple-choice questions and can be taken online or at a testing center. 500-420 exam is timed, and candidates have 90 minutes to complete it. To pass the exam, candidates must score at least 70%. 500-420 exam fee is $300.
Practice 500-420 Questions With Certification guide Q&A from Training Expert TrainingQuiz: https://www.trainingquiz.com/500-420-practice-quiz.html
Free Cisco 500-420 Test Practice Test Questions Exam Dumps: https://drive.google.com/open?id=1uj8Ks2O16XlOQWoDwTXAO8sFyBzFUk8Z
