500-420 Exam Dumps : Cisco AppDynamics Associate Performance Analyst (CAAPA)

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.

In AppDynamics, you can create health rules to monitor various metrics and set up actions based on the thresholds defined for these metrics. For monitoring Java container thread counts, you can set a health rule based on Node Health - specifically on thread pools - to trigger when the thread count exceeds a specific value. The Notification Action can then be configured to send an email to the development team whenever this threshold is breached.

AppDynamics supports the creation of custom baselines, allowing a Performance Analyst to define expected metric behavior over a selected historical period and recurring time pattern. Custom baselines are useful when the standard daily, weekly, or trend-based baselines do not accurately represent the application’s operating schedule, seasonal demand, or business cycle.

However, a custom baseline cannot be directly tagged or bound to an individual dashboard widget. Dashboard widgets can visualize metrics and, depending on the widget type, may display standard comparison or baseline-related information, but they do not provide a mechanism for associating a specifically named custom baseline with that widget.

Custom baselines are primarily applied in monitoring and evaluation contexts such as health-rule conditions, where current metric values can be compared against expected behavior using defined baseline criteria and standard deviations. Therefore, the baseline itself can be created and used for performance evaluation, but the analyst’s attempt to attach it directly to a dashboard widget is unsupported.

Relevant CAAPA Study Guide topics include Dynamic Baselines, Custom Baseline Configuration, Health Rule Conditions, Baseline Evaluation, Metric Visualization, and Custom Dashboard Widget Limitations.