Free 500-425 Exam Braindumps (page: 5)

Page 5 of 16

The App Server agent configuration GUI sets the configuration for which two agent properties? (Choose two.)

  1. Auto-naming
  2. Capture-raw-sql
  3. Node-name
  4. Max-business-transactions per node
  5. use-encrypted-credentials

Answer(s): C,D

Explanation:

The App Server agent configuration GUI allows you to set the configuration for the following agent properties:

Node-name: This property defines the name of the node that appears in the Controller UI. You can use the GUI to change the node name or use auto-naming rules based on environment variables or system properties.

Max-business-transactions per node: This property sets the maximum number of business transactions that can be registered on a node. If the number of business transactions exceeds this limit, the agent stops registering new business transactions and reports them as "All Other Traffic". You can use the GUI to increase or decrease this limit.


Reference:

1: Node Naming 2: Configure Business Transaction Limits



A customer complains that their dashboard is broken They tell you that every time they change the time range using the time picker, the data on several of their dashboard widgets do not change to match the new time range What is happening in this situation?

  1. the dashboard is too large and needs to be smaller
  2. the widgets are the wrong type for the dashboard
  3. the widgets are set to use their own time range
  4. the data in those widgets is old and needs to be updated

Answer(s): C

Explanation:

According to the Time Range Comparisons document., you can use the Compare Time Range feature in Dash Studio to compare two time periods on a widget. However, this feature also means that the widget may not use the global time range set for the entire dashboard by default. Instead, the widget may use its own time range (denoted as T1) and a second time range (denoted as T2) for comparison. Therefore, if the customer changes the time range using the time picker, the data on the widget may not change accordingly, unless they also update the widget's time range settings. To fix this problem, the customer can either disable the Compare Time Range feature or adjust the widget's time range to match the global time range.


Reference:

Time Range Comparisons



If you clear the "Mark Business Transaction as error" checkbox under Configuration > Instrumentation > Error Detection, which two statements are true? (Choose two)

  1. The transaction is included in Response Time metrics.
  2. The transaction is added to error count metrics
  3. The transaction does not add to error count metrics.
  4. The transaction does not add to call count metrics.

Answer(s): A,B

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.


Reference:

Error Detection: Mark Business Transaction as Error - AppDynamics

Business Transaction - AppDynamics

Error Detection - AppDynamics



To capture business data for Transaction Analytics what must be configured first?

  1. a Custom Metric
  2. a Data Collector
  3. a Health Rule
  4. an Information Point

Answer(s): B

Explanation:

To capture business data for Transaction Analytics, you must first configure a data collector. A data collector is a configuration that specifies what data to capture from a business transaction and how to store it in 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. Once you have configured a data collector, you can use it to enrich the transaction analytics data with business context and enable advanced queries and visualizations https://docs.appdynamics.com/accounts/en/cisco-appdynamics-saas-deployment-user- management/manage-custom-roles-for-cisco-appdynamics/transaction-analytics-permissions



Page 5 of 16



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

Jora commented on July 08, 2024
I am looking for take this exam with the help of these questions
Anonymous
upvote