Cisco AppDynamics 500-420 Questions & Answers

• Question 31:

  A Performance Analyst is experiencing difficulty with the transaction response time on a node. The Performance Analyst attempts to create a health rule monitoring the business transactions' performance on that node. Which set of data should the Performance Analyst select when creating the health rule?

  A. Node health

  B. Service endpoints

  C. Error Rates

  D. Transaction performance

  Correct Answer: D

  When a Performance Analyst is faced with issues related to transaction response times on a specific node, focusing on the "Transaction performance" data is most relevant. This is because transaction performance metrics provide direct

  insights into the business transactions' speed, response times, and execution times, which are critical for identifying and troubleshooting performance issues. By selecting "Transaction performance" when creating a health rule, the analyst

  can monitor specific metrics such as average response time, slow transaction count, and very slow transaction count, which are directly related to the performance of business transactions on the node in question.

  References:

  AppDynamics documentation on Health Rules: This section explains how to create and configure health rules to monitor application performance metrics, including transaction performance.

  AppDynamics documentation on Business Transactions: Provides details on how AppDynamics identifies and monitors business transactions, which are key to understanding application performance.

• Question 32:

  With what frequency are widgets updated during a war room scenario?

  A. Near real-time

  B. Every 5 minutes

  C. Every 10 minutes

  D. Every 60 minutes

  Correct Answer: A

  During a war room scenario, which is a real-time troubleshooting session, widgets in AppDynamics dashboards update in near real-time. This allows teams to observe the immediate impact of changes and identify issues as they occur.

  References:

  AppDynamics documentation on War Rooms:

• Question 33:

  A Performance Analyst has enabled Development Level Monitoring for an application. For a default configuration, in which scenario will Development Level Monitoring get automatically disabled?

  A. A maximum of 500 calls per minute limit is exceeded, and Maximum heap utilization percentage goes above 90%

  B. A maximum of 1500 calls per minute limit is exceeded, and Maximum heap utilization percentage goes above 90%

  C. A maximum of 1000 calls per minute limit is exceeded, and Maximum heap utilization percentage goes above 95%

  D. A maximum of 2000 calls per minute limit is exceeded, and Maximum heap utilization percentage goes above 95%

  Correct Answer: A

  Development Level Monitoring in AppDynamics is designed for use in a lower volume, non-production environment. For a default configuration, Development Level Monitoring will get automatically disabled if the monitored environment

  exceeds a threshold, typically a maximum of 1000 calls per minute, and the Maximum heap utilization percentage goes above 95%. These thresholds are in place to prevent excessive overhead in a production environment where such

  detailed monitoring could impact performance.

  References:

  AppDynamics documentation on Agent Configuration: Provides information on configuration settings for monitoring levels, including when Development Level Monitoring is automatically disabled due to exceeding thresholds.

• Question 34:

  Within the configuration setting for Slow Transactions, under the "Configure Diagnostic Session Duration and Collection Rate" option, what is the default value pair for the setting "Collect up to ____snapshots per minute for _____ minutes"?

  A. 2,2

  B. 5,5

  C. 10, 10

  D. 4,4

  Correct Answer: C

  The default value pair for the setting "Collect up to ____ snapshots per minute for _____ minutes" in the configuration for Slow Transactions is 10, 10. This means that by default, the system is set to collect up to 10 snapshots per minute for a

  duration of 10 minutes during a diagnostic session.

  References:

  AppDynamics documentation on Transaction Snapshots: Outlines the default settings for diagnostic session duration and collection rates, including the collection of snapshots.

• Question 35:

  Which health rule violation event will be triggered when a Performance Analyst modifies the existing health rule that is already in critical violation?

  A. Health Rule Violation Ended-Critical

  B. Health Rule Violation Started-Critical

  C. Health Rule Violation Canceled-Critical

  D. Health Rule Violation Continues-Critical

  Correct Answer: D

  When a Performance Analyst modifies an existing health rule that is already in a state of critical violation, the event that is typically triggered is "Health Rule Violation Continues-Critical." This event indicates that, despite the modification, the

  health rule is still being violated at a critical level. The system recognizes that the conditions for the health rule violation are still being met and continues to alert accordingly.

  References:

  AppDynamics documentation on Health Rules and Events: Explains the different types of health rule events and the conditions under which they are triggered.

• Question 36:

  Which two views can a Controller-level custom dashboard provide? (Choose two.)

  A. Show a single view of only historical data.

  B. Aggregate and compare data from only a single application on the same Controller

  C. Aggregate and compare data from different applications on the same Controller

  D. A customized view of applications, servers, and database performance data

  Correct Answer: CD

  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.

• Question 37:

  Which built-in scheduled report Includes load, response time, and error graphs?

  A. Dashboard Report

  B. All Application Summary

  C. Application Health Report

  D. User Experience: Browser Apps

  Correct Answer: C

  The "Application Health Report" is a built-in scheduled report in AppDynamics that includes vital metrics such as load, response time, and error graphs. This report provides a comprehensive overview of the application's health and

  performance, making it an essential tool for Performance Analysts to regularly review and share with stakeholders to ensure the application meets performance standards and user expectations.

  References:

  AppDynamics documentation on Reporting: Covers the types of reports available within AppDynamics, including the Application Health Report, detailing its contents and how to schedule and customize it.

  AppDynamics documentation on Application Performance Management: Provides an overview of key performance indicators and metrics critical for assessing application health, many of which are included in the Application Health Report.

• Question 38:

  A team of developers deploys new Java servlet code that should create new business transactions in AppDynamics. After applying load on the new code function, there are no new Business Transactions on the Business Transaction Dashboard.

  Which two options should the developers check in AppDynamics to make sure the Business Transactions can be discovered? [Choose two.)

  A. The metric browser to see if the new transactions appear under Business Transaction Performance.

  B. The tier with the new code does not have any rules excluding it.

  C. Auto discovery for service endpoints is turned on.

  D. There is a health rule created to check for transaction performance.

  E. Auto Discovery for servlet is turned on for Java agents.

  Correct Answer: BE

  When new business transactions are not appearing on the Business Transaction Dashboard after deploying new code, developers should verify that there are no exclusion rules in place on the tier where the new code was deployed. Additionally, it is crucial to ensure that the Auto Discovery feature for servlets is enabled for Java agents, as this allows AppDynamics to automatically detect and name business transactions based on incoming requests to servlets. Both of these checks are necessary to ensure that new business transactions can be discovered and monitored.References:AppDynamics documentation on Business Transaction detection and Java Agent configuration.

• Question 39:

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

  A. Server tab under "Tiers and Nodes"

  B. JMX tab under "Tiers and Nodes"

  C. Memory tab under Tier and Nodes"

  D. Metrics Browser

  Correct Answer: BD

  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. TheJMX 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.

  References:

  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.

• Question 40:

  What are two types of Data CollectorsinAppDynamics APM? (Choose two.)

  A. SQL data collectors

  B. HTTP data collectors

  C. Remote Service invocation data collectors

  D. Method invocation data collectors

  Correct Answer: AD

  In AppDynamics Application Performance Management (APM), two types of Data Collectors are SQL data collectors and Method invocation data collectors. SQL data collectors capture and record detailed information about SQL queries

  executed by the application, helping identify slow or inefficient database operations. Method invocation data collectors capture information about specific method calls within the application code, including execution times and parameters,

  providing deep insights into code-level performance.

  References:

  AppDynamics documentation on Data Collectors: Provides detailed information on configuring SQL and Method invocation data collectors for in-depth application monitoring.