Cisco Updated 500-420 Exam Questions and Answers by boden

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.

The Performance Analyst should use Compare Against Baseline. This flow-map function provides an immediate comparison between current application behavior and the established historical baseline for the selected time range. It helps identify whether response time, load, call volume, or dependency behavior has deviated from what AppDynamics considers normal.

In the exhibit, the yellow downstream applications indicate a warning state, even though the blue flow lines suggest that the current calls themselves are not showing an obvious critical condition. Comparing the current flow map against baseline allows the analyst to determine whether those downstream dependencies are performing worse than their customary levels and whether the tier’s dependency pattern has changed.

Correlation Analysis is intended to identify statistical relationships among metrics rather than provide a direct historical flow-map comparison. Health Rule Violations show triggered conditions but do not provide the fastest visual comparison with prior performance. Metric Browser Baselines can expose baseline values for individual metrics, but require more manual investigation.

Relevant CAAPA topics include Application Flow Maps, Dynamic Baselines, Compare Against Baseline, Dependency Analysis, and Health-State Interpretation.