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

The supported programming-language options are Go, C/C++, and C#. AppDynamics provides monitoring capabilities for applications built with these languages through language-specific agents, supported runtime instrumentation, or application-monitoring SDKs.

C# is monitored through the AppDynamics .NET Agent, which instruments supported .NET and .NET Framework applications to discover Business Transactions, collect call graphs, monitor exceptions, and correlate downstream service calls. C/C++ applications can be monitored using the AppDynamics C/C++ SDK and associated application instrumentation capabilities, enabling custom Business Transaction definition, exit-call tracking, and distributed transaction correlation. Go applications are supported through AppDynamics monitoring components designed for Go-based services, allowing transaction visibility and correlation within distributed application environments.

Perl is not listed as a standard AppDynamics APM language-agent platform. React is a JavaScript user-interface library rather than a programming language; browser-side React applications are typically observed through Browser Real User Monitoring. iOS Family describes a mobile platform, not a programming language, and is addressed through Mobile Real User Monitoring.

Relevant CAAPA topics include Application Agent Platforms, .NET Agent, C/C++ SDK, Go Application Monitoring, Business Transaction Instrumentation, and Real User Monitoring.

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.