Cisco 500-420 Online Practice Questions and Exam Preparation

Cisco 500-420 Online Questions & Answers

• Question 1:

  Refer to the exhibit.

  

  When looking at the Transaction Score for a specific transaction, how are errors in the transaction identified?

  A. Set the time range and drill down into the snapshots in the Error tab.
  B. Set the time range and examine the Slow Response Times tab.
  C. Set the time range and examine the dashboard for errors.
  D. Set the time range and drill down into the snapshots in the Events tab.
  A. Set the time range and drill down into the snapshots in the Error tab.

  ---

  explanation:

  Explanation/Reference:

  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:

• Question 2:

  Which statement is correct regarding controller-level and tier/node-level dashboards?

  A. The Performance Analyst can associate a controller-level dashboard with a tier or node through the My Dashboards tab
  B. From the controller-level dashboards list the Performance Analyst can access any tier/node-level dashboards outside the application in which they were created.
  C. Controller-level and tier/node-level dashboards are two separate sets. The Performance Analyst cannot cross-reference between these dashboards.
  D. Controller-level and tier/node-level dashboards are not scoped to be separate entities.
  C. Controller-level and tier/node-level dashboards are two separate sets. The Performance Analyst cannot cross-reference between these dashboards.

  ---

  explanation:

  Explanation/Reference:

  Controller-level and tier/node-level dashboards in AppDynamics are treated as separate entities. They are scoped differently, with controller-level dashboards providing a global view across the entire AppDynamics domain, and tier/node-level

  dashboards being specific to particular tiers or nodes within an application. Performance Analysts do not have the ability to cross-reference directly between these two sets of dashboards within the AppDynamics UI.

  References:

  AppDynamics documentation on Dashboards:

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

• Question 3:

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

  A. total free RAM
  B. network/firewall rules
  C. current CPU load average
  D. free license count
  B. network/firewall rules
  D. free license count

  ---

  explanation:

  Explanation/Reference:

  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 thatthere are available licenses for the agent to register. Insufficient licenses or network communication barriers can prevent successful agent registration.

  References:

  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.

• Question 4:

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

  A. Ad Hoc Data
  B. Application Health
  C. Error Trends
  D. Custom Dashboard
  E. Controller Audit
  F. Tier List
  B. Application Health
  C. Error Trends
  D. Custom Dashboard

  ---

  explanation:

  Explanation/Reference:

  AppDynamics allows for several reports to be scheduled for periodic generation and sent to email recipients. Among these, Application Health, Error Trends, and CustomDashboards are types of reports that can be automatically generated

  and delivered, providing regular insights into the application's performance and issues.

  References:

  AppDynamics documentation on Reports:

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

• Question 5:

  The performance impact on the_______would lead a Performance Analyst to limit the duration and frequency of automatic diagnostic sessions.

  A. Application
  B. Controller
  C. Network
  D. Operating System
  A. Application

  ---

  explanation:

  Explanation/Reference:

  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

• Question 6:

  Which tab within the Application Dashboard displays performance trends for each of Snapshots, Average Response Time, and Events within one central view?

  A. Application Flow Map
  B. Dashboard
  C. Events
  D. Transaction Score
  E. Network Dashboard
  D. Transaction Score

  ---

  explanation:

  Explanation/Reference:

  The Transaction Score tab within the Application Dashboard is designed to display performance trends across various metrics including Snapshots, Average Response Time, and Events. It gives a comprehensive view of the transaction

  performance, providing a score that reflects the health and reliability of transactions over time.

  References:

  AppDynamics documentation on Application Dashboard:

• Question 7:

  A Performance Analyst needs to send a summary report of specific events every two hours. Which feature can enable this automated report summary?

  A. Email Templates
  B. HTTP Request Templates
  C. Email Digests
  D. Email / SMS Configuration
  C. Email Digests

  ---

  explanation:

  Explanation/Reference:

  To send a summary report of specific events every two hours, a Performance Analyst can use the "Email Digests" feature in AppDynamics. This feature allows for the automated aggregation and delivery of pertinent event information at

  predefined intervals, ensuring stakeholders remain informed about the application's performance and significant events without the need for constant manual monitoring.

  References:

  AppDynamics documentation on Alerting and Notifications: Details the configuration of email notifications and digests for events and alerts, including scheduling and content customization options.

  AppDynamics documentation on Reports: Provides information on various reporting features, including the setup of automated email digests.

• Question 8:

  Which item supplements business transaction and transaction analytics data with application data?

  A. Demarcation collectors
  B. Netflow data
  C. Data collectors
  D. Endpoint sensors
  C. Data collectors

  ---

  explanation:

  Explanation/Reference:

  Data collectors in AppDynamics supplement business transaction and transaction analytics data with application data by capturing additional information during transaction execution. This can include method arguments, return values, and

  invocation context, which enriches the transaction data with more detailed application-level insights. This capability is crucial for in-depth performance analysis and troubleshooting, providing a more comprehensive view of application

  behavior.

  References:

  AppDynamics documentation on Data Collectors: Explains how to configure data collectors to capture and display detailed application data within business transactions.

• Question 9:

  What are two examples of backend calls? (Choose two.)

  A. a request coming from a browser
  B. a tier-to-tier request
  C. an asynchronous request
  D. a remote services call
  B. a tier-to-tier request
  D. a remote services call

  ---

  explanation:

  Explanation/Reference:

  Backend calls in AppDynamics are the interactions that an application component has with external components or services. These can include calls to databases, remote service calls, and interactions between different tiers of an application.

  A tier-to-tier request refers to any internal call that happens between different tiers (or nodes) within the same application. For example, a web tier calling an API service tier within the same application ecosystem. A remote services call is an

  external call from an application to a service that resides outside of the application's environment, like a call to an external web service, REST API, or a third-party service provider.

  References:

  AppDynamics documentation on Backend Detection:

  https://docs.appdynamics.com/21.6/en/application-monitoring/identify-backends

• Question 10:

  Which two functions does the Business Transaction Discovery Feature allow a user to perform? (Choose two.)

  A. Identify servers on which to install an AppDynamics application agent
  B. Identify new Business transactions in the Business Transaction Dashboard
  C. Identify PHP Business Transactions and preview them
  D. Identify potential Business Transactions and preview them
  E. Identify entry points from uninstrumented code
  B. Identify new Business transactions in the Business Transaction Dashboard
  D. Identify potential Business Transactions and preview them

  ---

  explanation:

  Explanation/Reference:

  The Business Transaction Discovery feature in AppDynamics allows users to identify new and potential business transactions directly within the Business Transaction Dashboard. This feature aids in the continuous monitoring and adaptation

  of the application's transaction tracking to changing business needs, ensuring comprehensive visibility. Users can also preview these identified transactions, assessing their relevance and impact on the application's performance before

  deciding to monitor them as official business transactions.

  References:

  AppDynamics documentation on Business Transaction Monitoring: Discusses how to manage and monitor business transactions, including the discovery and preview of new or potential transactions.

  AppDynamics documentation on Business Transaction Dashboard: Explains the functionalities and features of the Business Transaction Dashboard, including transaction discovery.