500-420 Exam Dumps : Cisco AppDynamics Associate Performance Analyst

When configuring an Information Point in AppDynamics, you can add match conditions to refine what gets measured. Match conditions based on a regex applied to the method allow you to specify which methods to include based on a regular expression pattern. Matching based on the invoked object allows you to specify which objects ' methods are included, filtering the data according to the object type or instance. These conditions help in pinpointing specific methods or objects for which you want to collect runtime information.

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.

AppDynamics supports scheduled delivery of Application Health, Controller Audit, and Custom Dashboard reports.

An Application Health report summarizes the operational condition of monitored applications over a selected reporting period. It can include health-rule violations, Business Transaction performance, errors, response-time behavior, and application availability, making it suitable for recurring operational reviews.

A Controller Audit report provides a record of administrative and configuration activity performed in the Controller. It is useful for governance, security review, compliance verification, and tracking changes made by users or administrators.

A Custom Dashboard report captures the widgets and visualizations configured on a selected custom dashboard. It can be generated periodically and emailed to stakeholders who need recurring application, infrastructure, or business-performance summaries without manually opening the Controller.

Ad Hoc Data describes manually selected or temporary analysis rather than a standard schedulable report type. Error Trends may appear as a dashboard visualization or metric analysis, but it is not a distinct scheduled-report category. Tier List is an application inventory view rather than a report designed for periodic email delivery.

Relevant CAAPA Study Guide topics include Reports, Report Scheduling, Email Distribution, Application Health Reports, Controller Audit Reports, Custom Dashboards, and Role-Based Reporting.