A fully updated 2024 500-425 Exam Dumps exam guide from training expert TrainingDumps
Provides complete coverage of every objective on exam and exam preparation 500-425
Cisco 500-425 exam covers a wide range of topics, including application deployment, configuration, and monitoring using the Cisco AppDynamics platform. 500-425 exam also tests candidates' abilities to troubleshoot application performance issues and identify areas for improvement. Cisco AppDynamics Associate Administrator certification is recognized globally and offers a competitive advantage to professionals looking to advance their careers in the IT industry.
Cisco 500-425 is a certification exam that tests an individual's expertise in AppDynamics administration. 500-425 exam validates the skills and knowledge required to configure, manage, and deploy AppDynamics applications in a production environment. Cisco AppDynamics Associate Administrator certification equips professionals with the skills needed to monitor application performance, diagnose and troubleshoot issues, and optimize application performance. Cisco AppDynamics Associate Administrator certification is designed for individuals who wish to demonstrate their proficiency in AppDynamics administration and enhance their career prospects in the IT industry.
Cisco 500-425 exam, also known as the Cisco AppDynamics Associate Administrator exam, is a certification exam that tests a candidate's knowledge and skills in managing and administering AppDynamics environments. AppDynamics is a widely-used application performance monitoring tool that helps businesses to monitor and analyze the performance of their applications and infrastructure. 500-425 exam is designed for professionals who are looking to demonstrate their expertise in AppDynamics administration and management.
NEW QUESTION # 11
Which two statements about Health Rules are true? (Choose two.)
- A. It remediates a problem
- B. It changes the status of a KPI
- C. Status changes are represented as an event
- D. It sends an email
Answer: B,C
Explanation:
Explanation
Health Rules are the rules that define the normal or expected behavior of your application, such as the response time, error rate, or CPU utilization of a business transaction, tier, node, or backend. You can create health rules to monitor the performance and availability of your application and its components. When a health rule is violated, it changes the status of the corresponding key performance indicator (KPI) from normal to warning or critical, depending on the severity of the violation. The status change is also represented as an event in the AppDynamics Controller UI, which can trigger alerts, policies, and actions. You can view the health rule events in the Events tab of the application dashboard, or in the Health tab of the entity dashboard.
https://developer.cisco.com/docs/appdynamics/health-rules/
https://university.appdynamics.com/certifications/associate-administrator
NEW QUESTION # 12
By default, which two Sensitive Data Filters substring does the Java Agent enable? (Choose two.)
- A. substring "key"
- B. substring "password"
- C. substring "ssn"
- D. substring "account"
- E. substring "credit card"
Answer: A,B
Explanation:
Explanation
By default, the Java Agent enables two Sensitive Data Filters substring: substring "key" and substring
"password". These filters prevent the agent from capturing and sending any data that contains these substrings to the Controller, such as query parameters, HTTP headers, cookies, environment variables, or system properties. This helps to protect sensitive information from being exposed in the Controller UI or reports. You can also add more filters or modify the existing ones by editing the agent configuration file1 References: 1: Filter Sensitive Data
NEW QUESTION # 13
The applications and servers are running normally What are two important reasons for the engineer to view and analyze server performancedata at this time? (Choose two.)
- A. Graphs and charts collected at this time are useful for showing application owners the stability of their application
- B. Collecting Server metric performance during normal operations helps determine code problems
- C. Visualizing application performance during normal operations helps identify when the application performance is abnormal.
- D. Collecting the errors during this period will identify memory problems in the application.
Answer: A,C
Explanation:
Explanation
Server performance data is the information that AppDynamics collects and reports about the health and availability of the servers that host your applications and their components. Server performance data includes metrics such as CPU utilization, memory usage, disk I/O, network traffic, and so on. You can use server performance data to monitor and troubleshoot the performance issues of your servers and applications.
According to the Server Visibility - AppDynamics, the following two reasons are important for the engineer to view and analyze server performance data at this time:
Visualizing application performance during normal operations helps identify when the application performance is abnormal: This means that by comparing the current server performance data with the historical or baseline data, you can detect any anomalies or deviations that may indicate a potential problem or degradation of your application performance. For example, you can use the Server Dashboard to see the current and historical trends of the server metrics, and use the Anomaly Detection feature to identify any outliers or unusual patterns.
Graphs and charts collected at this time are useful for showing application owners the stability of their application: This means that by using the graphical and visual representations of the server performance data, you can communicate and demonstrate the reliability and efficiency of your application to the stakeholders and customers. For example, you can use the Server Health Report to generate a summary of the server health status, availability, and performance over a specified time period, and share it with the application owners.
Therefore, A (Visualizing application performance during normal operations helps identify when the application performance is abnormal) and B (Graphs and charts collected at this time are useful for showing application owners the stability of their application) are two important reasons for the engineer to view and analyze server performance data at this time. References:
Server Visibility - AppDynamics
Cisco AppDynamics Associate Administrator Certification
Server Monitoring - AppDynamics
NEW QUESTION # 14
Which three types of performance degradation analysis are used with Business Transaction metrics? (Choose three.)
- A. Scalability Analysis
- B. JMX Analysis
- C. Remote Services Analysis
- D. Correlation Analysis
- E. Compare Releases
Answer: C,D,E
Explanation:
Explanation
Business Transaction metrics are the key performance indicators that measure the health and performance of your applications. They include metrics such as average response time, calls per minute, errors per minute, and so on. You can use various types of performance degradation analysis to identify and troubleshoot the root causes of performance issues using Business Transaction metrics.
According to the Troubleshoot Business Transactions - AppDynamics, the following types of performance degradation analysis are used with Business Transaction metrics:
Correlation Analysis: This type of analysis helps you to find the correlation between different metrics and events that may affect the performance of your Business Transactions. For example, you can use the correlation analysis to see how the response time of a Business Transaction is related to the CPU utilization of a node, or how the error rate of a Business Transaction is related to the number of slow database calls.
Remote Services Analysis: This type of analysis helps you to understand how the performance of your Business Transactions is impacted by the calls to remote services, such as databases, web services, message queues, and so on. For example, you can use the remote services analysis to see the response time, call count, error count, and wait time of each remote service call, and drill down to the details of each call.
Compare Releases: This type of analysis helps you to compare the performance of your Business Transactions across different releases of your application. For example, you can use the compare releases analysis to see how the response time, error rate, and throughput of your Business Transactions have changed after a new deployment, and identify any performance regressions or improvements.
Therefore, A (Correlation Analysis), B (Remote Services Analysis), and E (Compare Releases) are three types of performance degradation analysis that are used with Business Transaction metrics. References:
Troubleshoot Business Transactions - AppDynamics
Business Transaction - AppDynamics
Cisco AppDynamics Associate Performance Analyst Certification
NEW QUESTION # 15
Which three databases are supported by Database Visibility? (Choose three.)
- A. Cassandra
- B. DB2
- C. MongoDB
- D. PostgreSQL
- E. Derby
Answer: A,C,D
Explanation:
Explanation
According to the Database Visibility Supported Environments document1, Database Visibility can monitor the following databases: PostgreSQL, Cassandra, MongoDB, MySQL, SQL Server, Oracle, Sybase ASE, Sybase IQ, and Couchbase. Therefore, the correct answer is A, B, and D. Derby and DB2 are not supported by Database Visibility. References:
Database Visibility Supported Environments
NEW QUESTION # 16
Which two options can be excluded using error configuration? (Choose two.)
- A. Database error return codes
- B. JavaScript errors
- C. Uncaught exceptions
- D. HTTP errors
Answer: A,B
Explanation:
Explanation
Error configuration is a feature in AppDynamics that allows you to exclude certain types of errors and exceptions from being reported on the dashboard. You can use error configuration to filter out noise and focus on the most relevant and actionable issues.
According to the Error Configuration - AppDynamics, the following types of errors and exceptions can be excluded using error configuration:
Database error return codes: These are codes that indicate a problem with the database server, such as
0x80004005 (access denied) or 0x8000005E (access violation). You can exclude these errors from being reported on the dashboard by adding them to the error configuration list.
JavaScript errors: These are errors that occur in the browser due to invalid or malformed JavaScript code, such as syntax errors or reference errors. You can exclude these errors from being reported on the dashboard by adding them to the error configuration list.
Therefore, A (Database error return codes) and C (JavaScript errors) are two options that can be excluded using error configuration. References:
Error Configuration - AppDynamics
Cisco AppDynamics Associate Administrator Certification
[Create and Manage Error and Exception Configurations - AppDynamics]
NEW QUESTION # 17
What kind of problems are detected with Infrastructure monitoring?(Choose One)
- A. slow method calls
- B. garbage collection problems
- C. blocked threads
- D. thread pool problems
- E. process level problems
Answer: E
Explanation:
Explanation
Infrastructure monitoring is the feature in AppDynamics that allows you to monitor and troubleshoot the health and availability of the servers that host your applications and their components. Infrastructure monitoring includes metrics such as CPU utilization, memory usage, disk I/O, network traffic, and so on. You can use infrastructure monitoring to detect and resolve the problems that affect the performance and reliability of your servers and applications.
According to the Server Visibility - AppDynamics, the following kind of problem is detected with infrastructure monitoring:
Process level problems: These are the problems that occur at the process level of the server, such as high CPU consumption, memory leaks, excessive disk I/O, or network congestion. You can use infrastructure monitoring to identify the processes that are consuming the most resources, and drill down to the details of each process, such as the command line, the environment variables, the open files, the threads, and the sockets. You can also use infrastructure monitoring to correlate the process level problems with the application performance problems, such as slow response time, high error rate, or low throughput.
Therefore, E (process level problems) is the correct answer. References:
Server Visibility - AppDynamics
Cisco AppDynamics Associate Administrator Certification
Server Monitoring - AppDynamics
NEW QUESTION # 18
When troubleshooting an application using AppDynamics. which order would help narrow down a code problem with a specific business transaction the fastest?
- A. Review Exceptions > Look at Errors > Use Compare Releases
- B. Review tier and node metrics > Check Database Calls and metrics > Review Application Dashboard
- C. Review Application Dashboard > Lookat Events > Check Service Endpoints
- D. Review Application Dashboard > Check transaction scorecard > Check Transactions snapshots for problems
Answer: D
Explanation:
Explanation
When troubleshooting an application using AppDynamics, the fastest way to narrow down a code problem with a specific business transaction is to follow this order:
Review Application Dashboard: This is the first step to get an overview of the health and performance of your application and its components. You can see the key metrics, such as response time, throughput, error rate, and load, for each tier, node, and business transaction. You can also see the health rule violations, events, and alerts that indicate any issues or anomalies in your application.
Check transaction scorecard: This is the second step to drill down to the details of a specific business transaction that you want to troubleshoot. You can see the transaction scorecard by clicking on the business transaction name on the application dashboard. The transaction scorecard shows the metrics, such as average response time, calls per minute, errors per minute, and slow calls, for the selected business transaction. You can also see the breakdown of the response time by tier, node, and remote service, and the distribution of the response time by percentile.
Check transaction snapshots for problems: This is the third step to identify the root cause of the code problem for the selected business transaction. You can see the transaction snapshots by clicking on the View Snapshots button on the transaction scorecard. Transaction snapshots are the detailed records of the execution of a business transaction, including the call graph, the exit calls, the errors, the exceptions, the logs, the HTTP parameters, the cookies, the session attributes, and the custom data. You can use the transaction snapshots to analyze the code execution, the database queries, the web service calls, the message queues, the errors, and the exceptions that affect the performance of the business transaction.
Therefore, A (Review Application Dashboard > Check transaction scorecard > Check Transactions snapshots for problems) is the correct answer. References:
Cisco AppDynamics Associate Administrator Certification
Troubleshoot Business Transactions - AppDynamics
Business Transaction - AppDynamics
Transaction Snapshots - AppDynamics
NEW QUESTION # 19
Which two would be marked as an exception in AppDynamics? (Choose two)
- A. a handled exception after the business transaction terminates
- B. a custom-configured error method and error message
- C. any message that is logged with a severity of Error or Fatal
- D. HTTP errors that do not occur in the context of a Business Transaction
Answer: B,C
Explanation:
Explanation
An exception in AppDynamics is a code-level event that indicates a problem or abnormality in the execution of a business transaction. AppDynamics captures and presents information on exceptions in the monitored environment, and allows you to configure the rules and criteria for detecting and reporting exceptions.
According to the Errors and Exceptions - AppDynamics, the following two types of events would be marked as an exception in AppDynamics:
A custom-configured error method and error message: This is a type of event that you can define as an exception based on a specific method and message that indicate an error condition in your application code. You can configure the error detection rules to mark a business transaction as an error and capture the exception information when such a method and message are encountered. For example, you can configure a rule to mark a business transaction as an error and capture the exception when the method com.example.MyClass.myMethod returns the message Invalid input.
Any message that is logged with a severity of Error or Fatal: This is a type of event that AppDynamics automatically detects as an exception based on the log messages that are generated by your application code. AppDynamics scans the log messages for the keywords Error or Fatal, and marks the business transaction as an error and captures the exception information when such a message is found. For example, AppDynamics will mark a business transaction as an error and capture the exception when the log message contains Error: Null pointer exception.
Therefore, B (a custom-configured error method and error message) and C (any message that is logged with a severity of Error or Fatal) are two types of events that would be marked as an exception in AppDynamics.
References:
Cisco AppDynamics Associate Administrator Certification
Errors and Exceptions - AppDynamics
Error Detection - AppDynamics
NEW QUESTION # 20
Which two actions would trigger a health rule violation canceled warning event or a health rule violation canceled critical event? (Choose two.)
- A. Disable the health rule
- B. Mark the health rule as canceled
- C. Remove the health rule from a policy
- D. Add a new condition to the health rule.
Answer: A,D
Explanation:
Explanation
A health rule violation canceled warning event or a health rule violation canceled critical event is generated when the health rule processor can no longer accurately assert that the health rule violation continues to violate or that it has ended1. This can happen when the health rule is edited or disabled, among other reasons1. Adding a new condition to the health rule or disabling the health rule are two actions that would trigger a health rule violation canceled event, as they would change the evaluation criteria or stop the evaluation altogether1. Marking the health rule as canceled or removing the health rule from a policy are not valid actions, as they do not affect the health rule configuration or status
https://docs.appdynamics.com/appd/22.x/22.1/en/appdynamics-essentials/alert-and-respond/troubleshoot-health-
NEW QUESTION # 21
What is used to capture application data in a single Business Transaction?
- A. Information Point
- B. Data Collector
- C. Windows Performance Counters
- D. MX Rules
Answer: B
Explanation:
Explanation
A data collector is used to capture application data in a single business transaction. A data collector is a configuration that specifies what data to capture from a business transaction and how to store it in the AppDynamics Controller or the analytics platform. You can capture data from HTTP requests, method invocations, custom fields, or information points. You can also apply filters and transformations to the captured data. The captured data can be used for various purposes, such as adding context to business transactions, creating custom metrics, triggering health rules, enriching transaction analytics, or creating business journeys.https://university.appdynamics.com/certifications/associate-administrator
https://docs.appdynamics.com/appd/22.x/latest/en/application-monitoring/business-transactions
NEW QUESTION # 22
Your organization has defined a set of health rules that accurately represent the business functions of its applications. Which two ways should you help the organization see the current status of health rules and events of the business process? (Choose two.)
- A. Create a dashboard with health and events widgets displayed.
- B. Set up a policy to send an email or text when a health rule status changes.
- C. Leave the mam applications page open for all to see
- D. Create a report that runs every night and sends out the status.
Answer: A,B
Explanation:
Explanation
Health rules are the criteria that AppDynamics uses to evaluate the performance and availability of your applications and their components. Health rules can trigger alerts and actions when the conditions are violated or cleared. Events are the occurrences that AppDynamics records when something significant happens in your monitored environment, such as a health rule violation, a policy execution, a deployment, or a custom event.
According to the Health Rules - AppDynamics, the following two ways can help you see the current status of health rules and events of the business process:
Set up a policy to send an email or text when a health rule status changes: This way, you can get notified in real time when a health rule condition is met or cleared, and take appropriate actions to resolve or prevent issues. You can configure policies to send emails, texts, or other notifications to specific recipients or groups, and include relevant information such as the health rule name, the affected entity, the severity level, and the time range.
Create a dashboard with health and events widgets displayed: This way, you can visualize the health and performance of your applications and their components in a single view, and drill down to the details of each health rule or event. You can create custom dashboards with various widgets that show the health status, the event list, the event summary, the event correlation, and the event timeline of your applications and their components.
Therefore, A (Set up a policy to send an email or text when a health rule status changes) and D (Create a dashboard with health and events widgets displayed) are two ways that can help you see the current status of health rules and events of the business process. References:
Cisco AppDynamics Associate Administrator Certification
Health Rules - AppDynamics
[Policies and Actions - AppDynamics]
[Events - AppDynamics]
[Custom Dashboards - AppDynamics]
NEW QUESTION # 23
What are two situations where the UniqueHostID agent property is recommended to be used? (Choose two.)
- A. when the machine agent is with an app agent on different machines
- B. when the machine agent is with an app agent on the same machine
- C. when the machine agent is on multiple machines
- D. when the machine agent is with multiple app agents on the same machine
Answer: B,D
Explanation:
Explanation
The UniqueHostID agent property is recommended to be used when the machine agent is with multiple app agents on the same machine or when the machine agent is with an app agent on the same machine. This property allows you to specify a unique identifier for the host machine that overrides the default hostname resolution. This helps to avoid conflicts or confusion when multiple agents are running on the same host or when the hostname is not consistent across different agents1 References: 1: How are you able to associate the machine agent with application
NEW QUESTION # 24
Which two stats are available in Database Visibility? (Choose two.)
- A. Top 10 Connections by Application
- B. Top 10 Query Wait States
- C. Average Number of Slow Connections
- D. Time Spent in Database
- E. Top Leaked Connections
Answer: C,E
Explanation:
Explanation
Database Visibility provides metrics on the performance of your database and helps troubleshoot performance-related issues. Database Visibility consists of four main components: Database Agent, Collector, Controller, and Events Service (on-premises only). The Database Agent is a standalone Java program that collects performance metrics about your database instances and database servers. The Collector is the process that runs within the Database Agent to collect performance metrics about your database instances and database servers. The Controller is the central interface where you can see all your database instances and database server performance metrics. The Events Service stores high volumes of metric data.
According to the Overview of Database Visibility, the following types of information are sent to the Controller:
Database-level metrics, such as the number of queries processed and other database statistics Names and attributes of all sessions, clients, queries, and other objects on the monitored system The following types of information are sent to the Events Service:
Time that each query spends at each wait state
Individual query statistics for databases that support it
Information about individual execution plans in databases that support it Therefore, B (Average Number of Slow Connections) and C (Top Leaked Connections) are two stats that are available in Database Visibility. References:
Cisco AppDynamics Associate Administrator Certification
Overview of Database Visibility - AppDynamics
Database Visibility - AppDynamics
NEW QUESTION # 25
A customer needs to understand how establishing standards for naming Applications. Tiers, and Nodes can help them determine the root of a problem when users are working with AppDynamics or receive an alert Which three statements about establishing naming conventions are true? (Choose three.)
- A. Application Tier and Node values can be configured in the application agent startup script
- B. Nodes that reside on the same Tier but on different machines (hosts) can have duplicate Node names.
- C. Nodes that reside on different Tiers and different machines (hosts) can have duplicate Node names.
- D. Node names must be unique across the entire business application
- E. Application Tier and Node values can be configured in the controller-info.xml file
Answer: A,D,E
Explanation:
Explanation
According to the Tiers and Nodes document1, establishing standards for naming applications, tiers, and nodes can help you identify and organize the components of your monitored environment, as well as troubleshoot performance issues and health rule violations. Some of the statements about establishing naming conventions are true:
Application Tier and Node values can be configured in the application agent startup script: This is true for Java agents, as you can pass values to the agent that will be used as the application, tier, and node name for the system. For example, you can use the -Dappdynamics.agent.applicationName,
-Dappdynamics.agent.tierName, and -Dappdynamics.agent.nodeName properties to specify the names in the JVM startup script2.
Node names must be unique across the entire business application: This is true, as node names are used to identify the individual instances of the application components that are monitored by AppDynamics. Having duplicate node names can cause confusion and errors in the data collection and reporting. Therefore, you should use a naming convention that ensures uniqueness and clarity for each node1.
Application Tier and Node values can be configured in the controller-info.xml file: This is true for Java agents, as you can also configure the names in the controller-info.xml file, which is located in the
<agent_home>/conf directory. The controller-info.xml file contains the properties that define the agent identity and connection to the Controller. You can use the <application-name>, <tier-name>, and
<node-name> elements to specify the names in the file2.
Some of the statements about establishing naming conventions are false:
Nodes that reside on different Tiers and different machines (hosts) can have duplicate Node name:
This is false, as node names must be unique across the entire business application, regardless of the tier or the host they belong to. Having duplicate node names can cause confusion and errors in the data collection and reporting. Therefore, you should use a naming convention that ensures uniqueness and clarity for each node1.
Nodes that reside on the same Tier but on different machines (hosts) can have duplicate Node names: This is also false, as node names must be unique across the entire business application, regardless of the tier or the host they belong to. Having duplicate node names can cause confusion and errors in the data collection and reporting. Therefore, you should use a naming convention that ensures uniqueness and clarity for each node1.
References:
Tiers and Nodes
Name Business Applications, Tiers, and Nodes
NEW QUESTION # 26
What are three advantages of the custom dashboard feature? (Choose three.)
- A. It finds the line of code having a performance issue
- B. It makes drill down across tiers seamless
- C. It turns data sharing on/off on the fly.
- D. It monitors metrics of interest.
- E. It schedules dashboard as a report
Answer: B,D,E
Explanation:
Explanation
The custom dashboard feature in AppDynamics allows you to display a specific set of metrics and data points on one screen. You can use custom dashboards to present selected metrics for a user who only needs a relatively narrow or focused view of the data. You can also share custom dashboards with other users and stakeholders.
According to the [Custom Dashboards - AppDynamics], some of the advantages of the custom dashboard feature are:
It makes drill down across tiers seamless: You can use the grid layout type to create a flexible layout that is easy to rearrange on the canvas. The grid layout also scales in size when viewed on mobile devices. You can also use the absolute layout type to control width and height and the exact placement of widgets on the canvas.
It monitors metrics of interest: You can add widgets from various categories, such as application, server, database, performance, events, and so on. You can also customize the widget properties panel to configure the widget settings, such as title, description, color scheme, time range, auto-refresh interval, and so on.
It schedules dashboard as a report: You can export your custom dashboard as a PDF or HTML report that you can send by email or save as a file. You can also schedule your custom dashboard to run periodically using cron expressions.
Therefore, A (It makes drill down across tiers seamless), C (It monitors metrics of interest), and E (It schedules dashboard as a report) are three advantages of the custom dashboard feature. References:
[Custom Dashboards - AppDynamics]
[Create and Manage Custom Dashboards and Templates - AppDynamics]
Custom Dashboard Permissions - docs.appdynamics.com
NEW QUESTION # 27
What gives administrators the ability to test and debug policy execution?
- A. Policy Test Bench
- B. Event Simulation Tool
- C. Alert Simulation Environment
- D. Action and Policy Execution Tool
Answer: A
Explanation:
Explanation
The Policy Test Bench gives administrators the ability to test and debug policy execution. It allows you to simulate events and see how the policies and actions respond to them. You can also view the policy execution logs and troubleshoot any issues1 References: 1: Policy Test Bench
NEW QUESTION # 28
Users are saying they are experiencing occasional slow response lime. You suspect a database issue and want to find snapshots showing slow database responsetimes Which two statements describe how to locate snapshots showing the slow database response? (Choose two.)
- A. Go to the dashboard for the database and select slowest database calls.
- B. From the flow map, right-click the database icon and select view snapshots.
- C. Go to the list of snapshots and apply a filter based on slow database response
- D. Go to the list of snapshots and select analyze for a group of snapshots.
Answer: B,C
Explanation:
Explanation
Snapshots are the detailed records of the execution of a business transaction, including the call stack, the exit points, the errors, and the metrics. To locate snapshots showing slow database response, you can use the following methods:
Go to the list of snapshots and apply a filter based on slow database response: You can access the list of snapshots from the Business Transaction Dashboard or the Tier Dashboard. You can then apply a filter to show only the snapshots that have a slow database response time, which is the time spent by the business transaction in calling the database. You can specify the minimum and maximum values for the slow database response time, or use the predefined options such as slower than 1 second, slower than 5 seconds, etc. You can also combine this filter with other filters, such as time range, business transaction name, tier name, node name, etc. to narrow down the results1.
From the flow map, right-click the database icon and select view snapshots: You can access the flow map from the Application Dashboard, the Business Transaction Dashboard, or the Tier Dashboard. The flow map shows the graphical representation of the flow of the business transactions, including the tiers, the nodes, the backends, and the remote services. You can right-click on any database icon on the flow map and select view snapshots to see the list of snapshots that have called that database. You can then sort or filter the snapshots by the database response time column to find the slowest ones2.
The other options are not valid methods to locate snapshots showing slow database response. Going to the dashboard for the database and selecting slowest database calls will show the metrics and the flow map for the database, but not the snapshots. Going to the list of snapshots and selecting analyze for a group of snapshots will show the summary and the comparison of the selected snapshots, but not the database response time.
https://community.appdynamics.com/t5/Share-a-tip/Snapshots-and-identifying-intermittent-issues/td-p/42896
NEW QUESTION # 29
If you clear the "Mark Business Transaction as error" checkbox under Configuration > Instrumentation > Error Detection, which two statements are true? (Choose two)
- A. The transaction is included in Response Time metrics.
- B. The transaction is added to error count metrics
- C. The transaction does not add to error count metrics.
- D. The transaction does not add to call count metrics.
Answer: A,B
Explanation:
Explanation
The Mark Business Transaction as Error checkbox under Configuration > Instrumentation > Error Detection allows you to control whether a business transaction is reported as an error or not. If you clear this checkbox, the business transaction will not be marked as an error and will not affect the error count metrics.
According to the Error Detection: Mark Business Transaction as Error - AppDynamics, the following statements are true when you clear this checkbox:
The transaction is included in Response Time metrics: This means that the transaction will still contribute to the response time metric, which measures the average time it takes for a request to be completed by AppDynamics. However, it will not affect other response time metrics, such as First Response Time or Average Time to First Byte.
The transaction is added to error count metrics: This means that the transaction will still count towards the error count metric, which measures the number of transactions that have failed due to errors.
However, it will not affect other error count metrics, such as Error Rate or Error Percentage.
Therefore, A (The transaction is included in Response Time metrics) and B (The transaction is added to error count metrics) are true. References:
Error Detection: Mark Business Transaction as Error - AppDynamics
Business Transaction - AppDynamics
Error Detection - AppDynamics
NEW QUESTION # 30
......
Tested Material Used To 500-425: https://www.trainingdumps.com/500-425_exam-valid-dumps.html
Steps Necessary To Pass The 500-425 Exam: https://drive.google.com/open?id=1H1Zixpl2pPvXu3GqEmsCgxg1Ja2rWLZd
