Cisco AppDynamics 500-420 Questions & Answers

• Question 41:

  A Performance Analyst has a third-party event management system API and wants to use the event management system to send alerts to Level 1.

  Which actions are available in the AppDynamics Actions Menu to set this up?

  A. Send an SMS

  B. HTTP Request

  C. Remediation

  D. Send an Email

  Correct Answer: B

  When integrating with a third-party event management system, the Performance Analyst can set up an HTTP Request action within AppDynamics. This allows for the creation of a custom HTTP request to the event management system's API, which can be configured to send alerts to Level 1 support or any other designated recipient.

• Question 42:

  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 can be cross referenced but cannot be combined in a single dashboard

  B. Metrics from different applications cannot be cross referenced or combined on an AppDynamics dashboard

  C. Metrics from different applications cannot be cross referenced on an AppDynamics dashboard

  D. Metrics from different applications can be cross referenced on an AppDynamics dashboard

  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.

• Question 43:

  What is the Node limit of the maximum Service Endpoints per node?

  A. 50

  B. 100

  C. 250

  D. 1000

  Correct Answer: B

  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

• Question 44:

  Which two match conditions can be added when you configure an Information Point? (Choose two.)

  A. Match based on a regex applied to the method

  B. Match based on the invoked object

  C. Match based on the Business Transaction

  D. Match based on the return value

  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.

• Question 45:

  Which three Key Performance Indicators (KPIs) are automatically collected when you create an Information Point without adding custom data? (Choose three.)

  A. Maximum Response Time

  B. CPU Time

  C. Minimum Response Time

  D. Response Time

  E. Errors per Minute

  F. Calls per Minute

  Correct Answer: DEF

  When an Information Point is created in AppDynamics without adding custom data, it automatically collects three key performance indicators (KPIs): Response Time, Errors per Minute, and Calls per Minute. Response Time measures the

  time taken to complete a transaction or operation, providing insights into application performance. Errors per Minute tracks the number of errors occurring within the scope of the Information Point, helping identify problematic areas. Calls per

  Minute counts the number of times the specified operation or transaction is invoked, indicating its usage frequency and potential impact on application performance.

  References:

  AppDynamics documentation on Information Points: Discusses the creation and configuration of Information Points, including the default metrics collected.

• Question 46:

  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. Usage Stats

  B. Sessions

  C. Pages and Ajax Requests

  D. Overview

  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

• Question 47:

  Which AppDynamics option will allow a Performance Analyst to compare and filter related servers using custom metadata within your environment?

  A. Server Tagging

  B. Server Visibility

  C. Standalone Machine Agent

  D. Dynamic Monitoring Mode

  Correct Answer: A

  Server Tagging in AppDynamics allows a Performance Analyst to compare and filter related servers by using custom metadata. This feature enables users to group and organize their servers based on criteria that make sense for their environment, such as role, location, environment type, or any other custom metadata.

  References: AppDynamics documentation on Server Tagging https://docs.appdynamics.com/latest/en/infrastructure-visibility/infrastructure-visibility-settings/server-tags

• Question 48:

  An E-commerce application is built using microservices architecture design with several components. In AppDynamics, how should the Transaction Detection rules be grouped logically?

  A. Use Automatic Discovery

  B. Use Scope

  C. Use Transaction Group

  D. Use Backend Detection

  Correct Answer: C

  For an e-commerce application built using a microservices architecture, logically grouping Transaction Detection rules can be effectively achieved through "Use Transaction Group." This approach allows for the organization of business

  transactions into meaningful groups that reflect the application's structure and the interactionsbetween its microservices. By grouping transactions, it becomes easier to monitor, analyze, and troubleshoot the application as a whole and its

  individual components, enhancing the visibility and management of the application's performance.

  References:

  AppDynamics documentation on Business Transactions: Provides insights on how to configure and manage business transactions, including grouping and monitoring strategies.

  AppDynamics documentation on Microservices Monitoring: Offers guidance on best practices for monitoring applications designed with microservices architecture, including transaction grouping.

• Question 49:

  In which two features of AppDynamics can Information Points metric data be used? (Choose two.)

  A. Alerting

  B. Analytics

  C. Flow Maps

  D. Custom Dashboards

  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.

• Question 50:

  Which three pieces of information are required when creating a new database collector? (Choose three.)

  A. Primary table name

  B. Database hostname/IP address

  C. System table name

  D. Database Type

  E. Port number

  Correct Answer: BD

  When creating a new database collector in AppDynamics, the essential pieces of information required include the "Database hostname/IP address," "Database Type," and "Port number." These details are crucial for establishing a connection

  to the database and ensuring accurate monitoring. The hostname/IP address identifies the server where the database is hosted, the Database Type specifies the database management system (e.g., MySQL, Oracle), and the Port number is

  necessary for network communication with the database server.

  References:

  AppDynamics documentation on Database Visibility: This section explains how to set up database collectors, including the required information for successful configuration.