Cisco AppDynamics 500-420 Questions & Answers

• Question 1:

  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. Elevated Response Time at 6/19/18

  B. Elevated Response Time at 6/25/18

  C. Lower than usual volume at 6/17/18

  D. Low volume at 6/15/18

  Correct Answer: A

  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

• Question 2:

  Which Application Dashboard view categorizes transactions by load, response time, errors, slow transactions, and stalled transactions in a single aggregated value for a specific time range?

  A. Transaction Snapshots

  B. Top Business Transactions

  C. Machine Snapshots

  D. Transaction Score

  Correct Answer: D

  The Transaction Score view in the Application Dashboard categorizes transactions by load, response time, errors, slow transactions, and stalled transactions. It provides an aggregated value for a specific time range, giving an at-a-glance

  indication of the health and performance of business transactions.

  References:

  AppDynamics documentation on Transaction Score:

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

• Question 3:

  A Performance Analyst has noticed a significant decrease in an application's workload (calls/min) and is trying to identify the root cause. Which option will give the Performance Analyst insight into the behavior of the affected Business Transactions?

  A. Review Business Transactions and enable Show Trends

  B. In Metric Browser Plot Calls/min for the Application

  C. Review Top Business Transactions by Load in the Application Dashboard

  D. Review the Transaction Score for the Application

  E. Review all elements in the Application Flow Map and identify variations in load

  Correct Answer: C

  When a Performance Analyst observes a significant decrease in an application's workload (calls/min), reviewing the "Top Business Transactions by Load" in the Application Dashboard can provide valuable insights. This feature allows the

  analyst to quickly identify which business transactions have experienced the most significant changes in load, potentially pinpointing the root cause of the overall workload decrease. It offers a focused view of the application's performance,

  highlighting areas that may require further investigation or immediate action.

  References:

  AppDynamics documentation on Application Dashboard: Describes the features and capabilities of the Application Dashboard, including how to view and analyze the top business transactions by load.

  AppDynamics documentation on Business Transactions: Details the importance of monitoring business transactions and how they can be used to understand application performance trends.

• Question 4:

  An AppDynamics deployment has Business Transaction Lock Down turned on. The company has just added an important service to its application and wants to track this service as a unique Business Transaction. What action is needed to achieve this?

  A. Use the Business Transaction Dashboard for the tier-specific All Other Traffic to register the Business Transaction

  B. Modify the Automatic Transaction Discovery rule to include the Web Service Name and Operation Name

  C. Use live preview to identify the Business Transaction and Register it from there

  D. Create a Custom Transaction Match Rule based on the Web Service Name and Operation Name

  Correct Answer: D

  When Business Transaction Lock Down is enabled in AppDynamics, no new business transactions will be automatically discovered to avoid uncontrolled growth in the number of business transactions. To track a new service as a unique Business Transaction, one needs to create a Custom Match Rule that specifies the criteria for identifying the business transaction. In this case, the Custom Match Rule should be based on the Web Service Name and Operation Name which are the distinguishing characteristics of the new service. This allows for the precise identification and monitoring of the service within the AppDynamics platform.References:AppDynamics documentation on Business Transaction configuration and Custom Match Rules.

• Question 5:

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

  A. Enable Development Level Monitoring

  B. Browse the Metric Browser for errors

  C. Review the various transaction snapshots to identify anomalies

  D. Carefully monitor the snapshots for errors

  Correct Answer: A

  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.

  References:

  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 6:

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

  A. Transaction Type

  B. Number of Calls

  C. Regular Expression

  D. Class/Method Filter

  Correct Answer: B

  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.

  References:

  AppDynamics documentation on Business Transactions: Discusses best practices for managing business transactions, including the automatic cleanup based on time and call volume thresholds.

• Question 7:

  When should URI Segments be used in Transaction Detection rules?

  A. When identifying business transactions using particular parts of the SMTP request

  B. When the application uses message-oriented technologies

  C. When the application is a Web-Oriented Technology

  D. When the agent names the business transaction for the Web service name plus the operation name

  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

• Question 8:

  What must a Performance Analyst first configure in order to monitor end-to-end latency performance metrics in AppDynamics?

  A. additional demarcator methods

  B. define the end-to-end latency transaction

  C. slow end-point identity markers

  D. endpoints for asynchronous transactions

  Correct Answer: B

  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

• Question 9:

  Which values can be used to identify a split exit point?

  A. Tetration application values

  B. dynamic application values

  C. static application values

  D. variable application values

  Correct Answer: C

  A split exit point in AppDynamics is identified using static application values. Static values provide a consistent and predictable way to categorize exit points, making it easier to aggregate and analyze similar types of interactions with external

  services or components.

  References:

  AppDynamics documentation on Exit Points: Provides insights into how exit points are defined and identified within AppDynamics, including the use of static values for split exit points.

• Question 10:

  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.agent.reuse.nodeName andDappdynamics.agent.reuse.nodeName.prefix

  C. Dappdynamics.http.proxyHost and-Dappdynamcs.http. proxy User

  D. Dappdynamics.agent.node.metainfo and-Dappdynamics.agent.nodeName

  Correct Answer: B

  In environments where virtual machines are frequently created and destroyed, using the agent configuration properties-Dappdynamics.agent.reuse.nodeNameandDappdynamics.agent.reuse.nodeName.prefixcan be beneficial. These settings allow AppDynamics agents to reuse node names for newly created instances, facilitating consistent monitoring and tracking across dynamic environments. This

  approach helps maintain clarity in application topology and ensures that performance data remains coherent even as the underlying infrastructure changes.

  References:

  AppDynamics documentation on Agent Configuration: Discusses advanced agent configuration options, including node name reuse, to accommodate dynamic environments such as those with frequently changing virtual machines.

  AppDynamics documentation on Infrastructure Monitoring: Offers insights into best practices for monitoring in dynamic and virtualized environments.