Cisco Updated 500-420 Exam Questions and Answers by hashim

When a Performance Analyst observes a significant decrease in an application ' s workload (calls/min), reviewing the " Top Business Transactions by Load " in the Application Dashboard can provide valuable insights. This feature allows the analyst to quickly identify which business transactions have experienced the most significant changes in load, potentially pinpointing the root cause of the overall workload decrease. It offers a focused view of the application ' s performance, highlighting areas that may require further investigation or immediate action.

By default, AppDynamics allows a maximum of 200 registered Business Transactions per application and 50 Business Transactions per node.

The application-level limit controls the total number of unique Business Transactions that can be registered across all tiers and nodes belonging to the application. The node-level limit restricts how many transactions a single Application Agent can independently discover and register. These safeguards prevent uncontrolled Business Transaction growth, excessive metric creation, and unnecessary Controller resource consumption.

When either limit is reached, newly discovered requests are not registered as individual Business Transactions. Instead, they are typically grouped into an All Other Traffic category for the affected tier or entry-point type. Important transactions can still be prioritized by creating Custom Match Rules, excluding low-value traffic, refining transaction naming, or adjusting registration limits where operationally justified.

The application limit is not 100 or 300 by default, and the node limit is not 75 or 200.

Relevant CAAPA Study Guide topics include Business Transaction Registration Limits, Application and Node Limits, All Other Traffic, Automatic Transaction Discovery, Custom Match Rules, Exclude Rules, and Business Transaction Lock Down.

The Performance Analyst should enable Split Transaction using request data. This capability allows a single Custom Match rule to dynamically divide one base transaction into multiple business transactions according to values contained in the incoming HTTP request. For example, the rule can identify the base transaction as menu and append a request-derived value such as salads or entree, producing distinct transactions named menu.salads and menu.entree.

This approach avoids maintaining separate match rules for every menu category and scales automatically as additional request values are introduced.

An HTTP Request Data Collector captures request attributes for visibility within transaction snapshots but does not itself split or rename business transactions. A Method Invocation Data Collector captures method parameters, return values, or invoked-object data and is also unrelated to transaction splitting. Split Transaction using JSON is appropriate only when the required discriminator must specifically be extracted from a JSON payload.

Relevant CAAPA topics include Business Transaction Detection, Custom Match Rules, Transaction Naming, Request-Based Splitting, and Data Collectors.

The Performance Analyst should navigate to Configuration > Instrumentation > Call Graph Settings and configure package exclusions. Call Graph Settings control which Java packages, classes, and methods the Application Agent includes when constructing call graphs for transaction snapshots.

Excluding irrelevant package prefixes removes low-value framework, utility, generated-code, or third-party method detail from captured call graphs. This reduces diagnostic noise, makes transaction snapshots easier for developers to interpret, and can lower instrumentation and data-collection overhead. Exclusions should be applied carefully so that application-owned packages and methods required for root-cause analysis remain visible.

The controller-info.xml file contains Java Agent registration and Controller connectivity settings, such as the Controller address, account information, application, tier, and node identity. It is not the appropriate location for call-graph package exclusions. Baselines evaluate normal metric behavior and have no effect on instrumented classes or methods. The mbeans-server.xml file concerns JMX or MBean-related monitoring rather than Java call-graph filtering.

Relevant CAAPA Study Guide topics include Instrumentation Configuration, Call Graph Settings, Package Exclusions, Java Agent Overhead Management, Transaction Snapshots, and Code-Level Visibility.