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

In AppDynamics, metrics from different applications can indeed be cross-referenced on a single dashboard. This allows for a more holistic view of an organization ' s application ecosystem, facilitating the comparison and correlation of performance metrics across different applications within the same AppDynamics controller.

AppDynamics provides two applicable rule types when defining transaction detection behavior: Exclude Rules and Custom Match Rules.

A Custom Match Rule explicitly identifies application requests that should be detected as Business Transactions. The rule can match requests by entry point, class and method, URL, servlet, framework-specific attributes, headers, parameters, or other request data. It can also control transaction naming and splitting, allowing related requests to be grouped or separated according to operational requirements.

An Exclude Rule prevents matching requests from being discovered or registered as Business Transactions. This is useful for suppressing low-value traffic such as health checks, static-resource requests, polling calls, or framework-generated activity that would otherwise consume Business Transaction limits and add unnecessary metric noise.

An Automatic Discovery Rule is not created as a separate rule type in this context; automatic discovery is the agent’s default transaction-identification behavior. A Health Rule evaluates monitored metrics and triggers policy actions, while an Include Rule is not a transaction detection rule category.

Relevant CAAPA topics include Business Transaction Detection, Custom Match Rules, Exclude Rules, Entry-Point Matching, Automatic Discovery, and Business Transaction Registration Limits.

The custom exclude rule prevents the servlet request from being registered and monitored as a Business Transaction, while the Service Endpoint custom match rule independently instruments the matching URI as a Service Endpoint. AppDynamics therefore continues to collect Service Endpoint metrics, including average response time, calls per minute, and errors, allowing the analyst to monitor the service’s performance without consuming a Business Transaction registration.

The excluded request does not produce normal Business Transaction snapshots, so the analyst cannot rely on snapshot call graphs to inspect the Service Endpoint or its downstream exit calls. Exit-point visibility is normally obtained through Business Transaction snapshots and call graphs.

EUM correlation also depends on the server-side request being represented as a correlated Business Transaction. A standalone Service Endpoint does not replace that Business Transaction correlation path and therefore cannot provide equivalent browser or mobile EUM linkage.

Relevant CAAPA Study Guide topics include Service Endpoint Detection, Custom Service Endpoint Match Rules, Business Transaction Exclude Rules, Service Endpoint Metrics, Transaction Snapshots, Exit Calls, and EUM Correlation.