500-420 Online Practice Questions and Answers

Correct Answer: C

URI Segments should be used in Transaction Detection rules when the application is web-oriented. Web-oriented applications often have meaningful information in the URIthat can identify different business transactions. URI Segments can

help in defining patterns that match specific parts of the URI to distinguish different transactions.

References:

AppDynamics documentation on Transaction Detection:

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

Correct Answer: A

To identify if automatic remediation actions have been taken for a health rule violation in AppDynamics, a Performance Analyst should expand the "Description" field of the health rule violation event. This section will provide details on the actions executed as part of the automatic remediation process. These details help analysts understand the steps taken by the system to mitigate the issue without manual intervention.References:AppDynamics documentation on Health Rule Violations and Automated Actions.

Correct Answer: C

To streamline the monitoring process and enhance the relevance of collected data, AppDynamics allows Performance Analysts to exclude certain Java classes and methods from instrumentation. This is done through the "Configuration >

Instrumentation > Call Graph Settings" menu, where irrelevant packages and classes can be specified for exclusion. This approach prevents the AppDynamics agent from tracking unnecessary or irrelevant methods, thus reducing overhead

and focusing on the most critical aspects of application performance.

References:

AppDynamics documentation on Call Graph Settings: This section details how to configure call graph settings, including the exclusion of specific classes and methods from instrumentation, to optimize performance monitoring.

Correct Answer: CD

Creating a Transaction Group using the 'Create Group' action in AppDynamics allows for the aggregation of data from multiple transactions under a single group, facilitating a consolidated view of similar transactions. This differs from defining

a Transaction Detection Rule, which typically focuses on identifying and categorizing individual transactions based on specific criteria. Transaction Groups do not change the names of incoming requests nor reduce the number of overall

business transactions; instead, they provide a method for organizing and analyzing related transactions collectively, offering a streamlined approach compared to individually configuring Transaction Detection Rules for each transaction.

References:

AppDynamics documentation on Business Transactions: Covers the concept of Transaction Groups and their role in organizing and analyzing transaction data, as well as the process for creating and managing Transaction Detection Rules.

Correct Answer: D

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.

Correct Answer: AB

When configuring an Information Point in AppDynamics, you can add match conditions to refine what gets measured. Match conditions based on a regex applied to the method allow you to specify which methods to include based on a regular

expression pattern. Matching based on the invoked object allows you to specify which objects' methods are included, filtering the data according to the object type or instance. These conditions help in pinpointing specific methods or objects

for which you want to collect runtime information.

References:

AppDynamics documentation on Information Points and Match Conditions.

Correct Answer: A

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

Correct Answer: AD

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.

Correct Answer: A

The primary concern for a Performance Analyst when considering the impact of automatic diagnostic sessions is the application itself. Intensive diagnostic sessions can be resource-heavy, potentially affecting the application's performance.

Therefore, it is often necessary to limit the duration and frequency of these sessions to ensure they do not negatively impact the application's end-user experience.

References:

AppDynamics documentation on Diagnostic Sessions:

https://docs.appdynamics.com/latest/en/troubleshoot/diagnostic-sessions

Correct Answer: A

Errors in a transaction are identified by examining the snapshots that capture the problematic transactions. By setting the appropriate time range, a Performance Analyst can drill down into the snapshots within the Error tab to identify and

analyze errors. These snapshots provide detailed diagnostic information, such as stack traces, slow SQL queries, and error logs, which are vital for pinpointing the root cause of transaction errors.

References:

AppDynamics documentation on Transaction Snapshots: