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: 2)

Page 2 of 17
PDF with 64 Questions

A Performance Analyst is experiencing difficulty with the transaction response time on a node. The Performance Analyst attempts to create a health rule monitoring the business transactions' performance on that node.
Which set of data should the Performance Analyst select when creating the health rule?

  1. Node health
  2. Service endpoints
  3. Error Rates
  4. Transaction performance

Answer(s): D

Explanation:

When a Performance Analyst is faced with issues related to transaction response times on a specific node, focusing on the "Transaction performance" data is most relevant. This is because transaction performance metrics provide direct insights into the business transactions' speed, response times, and execution times, which are critical for identifying and troubleshooting performance issues. By selecting "Transaction performance" when creating a health rule, the analyst can monitor specific metrics such as average response time, slow transaction count, and very slow transaction count, which are directly related to the performance of business transactions on the node in question.


Reference:

AppDynamics documentation on Health Rules: This section explains how to create and configure health rules to monitor application performance metrics, including transaction performance. AppDynamics documentation on Business Transactions: Provides details on how AppDynamics identifies and monitors business transactions, which are key to understanding application performance.



Developers and operations personnel complain the Controller tracks many irrelevant Java classes and methods. How does a Performance Analyst exclude this unhelpful information?

  1. Configuration > Baselines and create a new dynamic baseline
  2. Edit the mbeans-server.xml file to delete the irrelevant methods
  3. Configuration > Instrumentation > Call Graph Settings and exclude irrelevant packages
  4. Edit the controller-info.xml file to exclude irrelevant methods

Answer(s): C

Explanation:

To streamline the monitoring process and enhance the relevance of collected data, AppDynamics allows Performance Analysts to exclude certain Java classes and methods from instrumentation. This is done through the "Configuration > Instrumentation > Call Graph Settings" menu, where irrelevant packages and classes can be specified for exclusion. This approach prevents the AppDynamics agent from tracking unnecessary or irrelevant methods, thus reducing overhead and focusing on the most critical aspects of application performance.


Reference:

AppDynamics documentation on Call Graph Settings: This section details how to configure call graph settings, including the exclusion of specific classes and methods from instrumentation, to optimize performance monitoring.



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

  1. Primary table name
  2. Database hostname/IP address
  3. System table name
  4. Database Type
  5. Port number

Answer(s): B,D

Explanation:

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.


Reference:

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



Which two Key Performance Indicators (KPIs) accurately provide insight into server level resource consumption? (Choose two.)

  1. Calls per Minute
  2. Availability
  3. Average Response Time
  4. Application Restarts
  5. CPU %Busy
  6. Memory Used%

Answer(s): E,F

Explanation:

Key Performance Indicators (KPIs) such as "CPU %Busy" and "Memory Used%" are critical for providing insights into server-level resource consumption. "CPU %Busy" indicates the percentage of time the CPU is actively working on processes, reflecting the server's processing workload. "Memory Used%" shows the proportion of memory utilized, indicating how much of the server's RAM is being consumed by applications and processes. These KPIs are essential for understanding and managing server performance and resource allocation.


Reference:

AppDynamics documentation on Server Monitoring: Includes information on monitoring server-level metrics, including CPU and memory utilization, to assess resource consumption.






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