Question 1

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

Accepted Answer

C

Explanation: 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 interactions between 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. Reference: 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 2

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

Accepted Answer

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. Reference: 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 3

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?

Accepted Answer

A

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. Reference: AppDynamics documentation on Browser RUM: https://docs.appdynamics.com/21.6/en/end-usermonitoring/browser-monitoring/browser-real-user-monitoring

Question 4

What does the Live Preview option in a Business Transaction Discovery Session allow a user to do?

Accepted Answer

A

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. Reference: AppDynamics documentation on Business Transaction Management: Includes information on Business Transaction Discovery Sessions and the use of Live Preview to validate Transaction Discovery Rules.

Question 5

A Performance Analyst is reviewing Business Transactions with an Application team. The Application
team would like to increase the Application Business Transaction limit because they need to have
visibility into all the different transactions. What should the Performance Analyst do?

Accepted Answer

D

Explanation: When an application team requests an increase in the Application Business Transaction limit for visibility purposes, it's crucial for the Performance Analyst to focus on the transactions that are currently exceeding the limit and understand why. This approach helps in identifying whether the limit is being reached due to genuinely essential transactions or if there are redundant, irrelevant, or improperly defined transactions contributing to the limit breach. By analyzing and rationalizing the transactions, the analyst can ensure that only valuable transactions are monitored, optimizing resource usage and maintaining effective observability without necessarily increasing the limit. Reference: AppDynamics documentation on Business Transaction Limits: Discusses the implications of business transaction limits and strategies for managing and optimizing these limits within AppDynamics. AppDynamics Best Practices Guide: Offers recommendations for configuring and managing business transactions, including handling limits and ensuring meaningful transaction monitoring.

Question 6

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

Accepted Answer

C

Explanation: 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. Reference: 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 7

Which two types of data are collected by Information Points? (Choose two.)

Accepted Answer

B, C

Explanation: Information Points in AppDynamics are designed to collect custom metrics that are specific to the business or code aspects of an application. They can capture Business Metric Data, which pertains to the performance metrics that directly impact business processes, and Code Metric Data, which relates to the performance of specific methods or segments of code within the application. This allows for targeted monitoring and analysis of areas significant to the business's objectives and technical performance. Reference: AppDynamics documentation on Information Points: Provides details on how to set up Information Points to collect custom business and code metrics for in-depth performance analysis.

Question 8

Which permission allows snapshot archiving?

Accepted Answer

C

Explanation: The permission to enable snapshot archiving in AppDynamics typically falls under advanced operational capabilities, such as those categorized under "Agent Advanced Operation." This permission allows users to archive transaction snapshots for long-term storage and analysis, which is essential for historical performance analysis and auditing purposes. Reference: AppDynamics documentation on Role-Based Access Control: Explains the different permissions and roles within AppDynamics, including those related to advanced agent operations and snapshot archiving.

Question 9

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

Accepted Answer

A, 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. Reference: 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 10

A Performance Analyst has opened a database collector view. Which tab should be clicked on next to find slow queries?

Accepted Answer

B

Explanation: When analyzing database performance in AppDynamics, the "Queries" tab within the database collector view is where a Performance Analyst should navigate to find slow queries. This tab presents a list of database queries executed by the application, highlighting those with long execution times, which are potential bottlenecks impacting application performance. Reference: AppDynamics documentation on Database Monitoring: Details the database collector feature, including how to use the Queries tab to identify and analyze slow database queries.

Question 11

A Performance Analyst has an urgent need to gather more data for an ongoing issue. What should the Performance Analyst do?

Accepted Answer

A

Explanation: If a Performance Analyst has an urgent need to gather more data for an ongoing issue, they should enable Development Level Monitoring. This monitoring level increases the amount of detailed diagnostic data collected by the agent, such as snapshots and transaction traces, which can provide deeper insights into the issue at hand. Reference: AppDynamics documentation on Monitoring Levels: Describes the different levels of monitoring available, including Development Level Monitoring and the types of data each level collects.

Question 12

Which three reports can be scheduled for periodic generation and delivery to email recipients? (Choose three.)

Accepted Answer

B, C, D

Explanation: AppDynamics allows for several reports to be scheduled for periodic generation and sent to email recipients. Among these, Application Health, Error Trends, and Custom Dashboards are types of reports that can be automatically generated and delivered, providing regular insights into the application's performance and issues. Reference: AppDynamics documentation on Reports: https://docs.appdynamics.com/latest/en/applicationmonitoring/reporting

Question 13

Refer to Exhibit. https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/500-420/page_34_img_1.jpg 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?

Accepted Answer

A

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. Reference: AppDynamics documentation on Transaction Score: https://docs.appdynamics.com/latest/en/application-monitoring/applicationdashboard/transaction-score

Question 14

Which option, in addition to "minutes since creation", would a Performance Analyst use while configuring Automatic Cleanup of stale Business Transactions?

Accepted Answer

B

Explanation: When configuring Automatic Cleanup of stale Business Transactions, the "minutes since creation" option is often paired with the "Number of Calls" metric. This setting ensures that business transactions that have not been called within a certain timeframe and have had a negligible number of calls are automatically cleaned up, helping to maintain an organized and relevant set of business transactions in the monitoring system. Reference: AppDynamics documentation on Business Transactions: Discusses best practices for managing business transactions, including the automatic cleanup based on time and call volume thresholds.

Question 15

Which two things should a Performance Analyst check if an agent has failed to register with the Controller after several minutes? (Choose two.)

Accepted Answer

B, D

Explanation: If an agent fails to register with the Controller, a Performance Analyst should check the network/firewall rules to ensure that the agent can communicate with the Controller over the network. Additionally, it is crucial to verify the free license count to confirm that there are available licenses for the agent to register. Insufficient licenses or network communication barriers can prevent successful agent registration. Reference: AppDynamics documentation on Agent Registration: Describes the prerequisites and troubleshooting steps for agent registration with the Controller. AppDynamics documentation on Licensing: Provides details on how the licensing model works, including how to check for available licenses.

Free Cisco 500-420 Actual Exam Questions