CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Cisco®
  5. 500-420

Free 500-420 Exam Braindumps (page: 5)

Page 4 of 17
PDF with 64 Questions

A Business Transaction was registered and displayed on the Business Transaction Dashboard. It has continuous load on it. After an hour the Business Transaction stopped being displayed in the Business Transaction Dashboard.
Which action stopped the display of the Business Transaction?

  1. The Business Transaction Lock Down was enabled an hour ago.
  2. The Business Transaction had been deleted an hour ago from the Business Transaction Dashboard.
  3. The Business Transaction Custom Match Rule was deleted an hour ago.
  4. The Business Transaction had been excluded an hour ago from the Business Transaction Dashboard.

Answer(s): C

Explanation:

If a Business Transaction stops being displayed on the Business Transaction Dashboard after continuous load, it could be due to the deletion of the Business Transaction Custom Match Rule. Custom Match Rules in AppDynamics are used to define custom business transactions based on specific criteria. If such a rule is deleted, transactions that were previously identified and displayed based on that rule may no longer be recognized as distinct business transactions, leading to their disappearance from the dashboard.


Reference:

AppDynamics documentation on Business Transactions: Provides insights on configuring and managing business transactions, including the use of custom match rules.



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

  1. Server tab under "Tiers and Nodes"
  2. JMX tab under "Tiers and Nodes"
  3. Memory tab under Tier and Nodes"
  4. Metrics Browser

Answer(s): B,D

Explanation:

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. The JMX 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.


Reference:

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.



Which type of Data Collector will capture code data such as method arguments, variables, and return values?

  1. Method Invocation Data Collector
  2. Servlet Container Collector
  3. Transaction Data Collector
  4. URI Data Collector

Answer(s): A

Explanation:

The "Method Invocation Data Collector" is specifically designed to capture code-level data such as method arguments, variables, and return values. This type of data collector enables deep visibility into the execution of methods within transactions, providing valuable insights into the application's behavior and performance. This detailed level of monitoring is essential for diagnosing complex issues and understanding the inner workings of business transactions.


Reference:

AppDynamics documentation on Data Collectors: Details the types of data collectors available, including Method Invocation Data Collectors, and how they can be used to capture detailed code- level data.



When using the REST interlace where would a Performance Analyst go to see all of the captured endpoints by service?

  1. Navigate to the Metric Browser then to the specific metric. Copy the REST URL from the Metric Browser and then use a wildcard query to get the metrics for other SEPs.
  2. Navigate to the Applications browser then drill down the requested endpoint with the available Dashboard & Metrics indicators then selected the desired metric.
  3. Navigate to the Metric Browser then to the Consumed Endpoints location. Drill down in the metric browser on the specific endpoint to call out its services.
  4. Access the MySQL database and find all the endpoints in an app. where can drill down to the tier and transactions using the endpoints. Select the appropriate REST feature enabled by the service endpoint.

Answer(s): C

Explanation:

To view all captured endpoints by service using the REST interface in AppDynamics, a Performance Analyst would navigate to the Metric Browser and proceed to the "Consumed Endpoints" section. From there, drilling down on specific endpoints within the Metric Browser allows the analyst to explore the services associated with each endpoint. This method enables detailed analysis of endpoint metrics, facilitating the monitoring and optimization of service performance.


Reference:

AppDynamics documentation on Metric Browser: Guides on navigating the Metric Browser to access and analyze various application metrics, including those related to endpoints and services. AppDynamics documentation on REST API: Provides information on how to utilize the REST API for retrieving metrics, including endpoint data.






Post your Comments and Discuss Cisco® 500-420 exam with other Community members:

500-420 Discussions & Posts