500-420 Exam Dumps - Cisco AppDynamics Certified Associate Questions and Answers

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.

URI Segments should be used in Transaction Detection rules when the application is web-oriented. Web-oriented applications often have meaningful information in the URI that can identify different business transactions. URI Segments can help in defining patterns that match specific parts of the URI to distinguish different transactions.

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.

A Scope is used to apply Transaction Detection Rules selectively to one or more tiers that perform the same or a related application function. Scoping allows a Performance Analyst to avoid applying a custom match rule or exclude rule across the entire application when the relevant entry point, framework, class, method, or request pattern exists only within particular tiers.

For example, several web-service tiers may use the same transaction naming convention or custom entry-point logic. The analyst can group those tiers within a scope and associate the transaction detection rule with that scope. This provides consistent detection behavior while preventing the rule from affecting unrelated application tiers.

Scopes are not primarily defined for individual nodes because nodes inherit transaction detection behavior from their tier-level configuration. They are also not used for backends, which are identified through exit-point and backend detection configuration. Transaction Detection Rule scopes remain within the context of a single monitored application and are not used to distribute one rule across multiple applications.

Relevant CAAPA Study Guide topics include Transaction Detection, Rule Scopes, Tier-Level Instrumentation, Custom Match Rules, Exclude Rules, Entry-Point Detection, and Application Agent Configuration.

The Business Transaction Discovery feature in AppDynamics allows users to identify new and potential business transactions directly within the Business Transaction Dashboard. This feature aids in the continuous monitoring and adaptation of the application ' s transaction tracking to changing business needs, ensuring comprehensive visibility. Users can also preview these identified transactions, assessing their relevance and impact on the application ' s performance before deciding to monitor them as official business transactions.

To permanently remove a Business Transaction, the analyst must first exclude it from transaction detection and then delete it from the Business Transaction list. Deleting the transaction alone removes its current registration and associated visibility from the Controller, but the Application Agent can rediscover and register it again when matching traffic is observed.

An exclusion rule prevents future requests matching the specified entry point or transaction criteria from being detected as that Business Transaction. After the exclusion is configured and applied, the existing Business Transaction can be deleted safely without being recreated by automatic discovery.

Business Transaction Automatic Cleanup removes stale or inactive transactions according to retention and cleanup criteria; it does not prevent an active transaction from being rediscovered. Merely deleting the transaction from the list is therefore temporary when matching requests continue. Modifying a detection rule may alter transaction classification, but the explicit and reliable method for permanent removal is to exclude the transaction before deleting its existing registration.

Relevant CAAPA Study Guide topics include Business Transaction Detection, Exclude Rules, Automatic Discovery, Business Transaction Registration, Transaction Cleanup, and Business Transaction Management.

The Performance Analyst should use Browser Apps. This area contains Browser Real User Monitoring data and presents application performance from the actual end user’s perspective. It provides detailed trend graphs for browser pages and AJAX requests, including metrics such as end-user response time, page load time, network time, server time, DOM processing time, resource-loading time, request volume, errors, and geographic or browser-related performance variations.

These measurements enable the analyst to determine whether a performance problem originates in the browser, network, content-delivery path, application server, or a downstream dependency. The graphs can also be filtered by time range, page, browser type, device, operating system, location, and other user-session dimensions.

Transaction Analytics is used for querying and analyzing transaction and business-event data. Remote Services focuses on backend dependencies and external service calls. Applications primarily provides server-side APM visibility into Business Transactions, tiers, nodes, and application flow.

Relevant CAAPA Study Guide topics include Browser Real User Monitoring, Browser Applications, End-User Response Time, Page and AJAX Performance, User Experience Analysis, and Client-Side Performance Trends.