Controller-level and tier/node-level dashboards in AppDynamics are treated as separate entities. They are scoped differently, with controller-level dashboards providing a global view across the entire AppDynamics domain, and tier/node-level dashboards being specific to particular tiers or nodes within an application. Performance Analysts do not have the ability to cross-reference directly between these two sets of dashboards within the AppDynamics UI.

To plot Host CPU and GC (Garbage Collection) Time Spent in a single view, the " JMX tab under ' Tiers and Nodes ' " and the " Metrics Browser " are the appropriate methods. The JMX tab provides access to Java Management Extensions (JMX) metrics, including those related to GC time. The Metrics Browser allows for the customization and aggregation of various metrics, including Host CPU usage and GC metrics, enabling a combined view of these critical performance indicators.

When an existing health rule is modified while it has an active critical violation, AppDynamics generates a Health Rule Violation Canceled – Critical event. Editing the health rule changes the definition under which the current violation was originally evaluated. The Controller therefore cancels the active violation rather than continuing to evaluate it against a configuration that no longer matches its originating criteria.

A Continues – Critical event is generated when the same active violation remains in the critical state during subsequent evaluation and update intervals without a configuration change. A Started – Critical event indicates that a new critical violation has opened. An Ended – Critical event occurs when the monitored condition returns to an acceptable state according to the unchanged health-rule criteria.

After the rule is modified, AppDynamics evaluates the revised conditions as a new monitoring definition. If those revised criteria are subsequently breached, a new violation-start event can be generated.

Relevant CAAPA Study Guide topics include Health Rule Violation Lifecycle, Critical and Warning Events, Rule Modification Behavior, Violation Cancellation, Evaluation Criteria, and Policy Event Triggers.

The Performance Analyst should configure an HTTP Request action. This action enables AppDynamics to invoke a third-party event management system’s API when a policy is triggered by a health rule violation or another supported event.

The HTTP Request action can be configured with the target endpoint URL, HTTP method, authentication information, request headers, and an event payload. AppDynamics variables can be inserted into the payload so the external system receives useful alert context, such as the application name, affected Business Transaction, tier, node, health rule, severity, event time, and violation details. The event management platform can then route the incident to Level 1 support according to its own escalation and assignment workflow.

Send an Email and Send an SMS are direct notification mechanisms and do not use the third-party system’s API. Remediation is intended to execute corrective actions, scripts, or operational responses rather than transmit an alert to an external event-management endpoint.

Relevant CAAPA Study Guide topics include Health Rules, Policies, Actions, HTTP Request Actions, Third-Party Integrations, Event Payload Templates, and Alert Escalation Workflows.

The Metric Browser provides the authoritative metric hierarchy and can generate the REST URL corresponding to a selected Service Endpoint metric. A Performance Analyst first navigates to a representative Service Endpoint and metric, then copies the generated REST URL. The metric path in that URL can be modified with supported wildcard expressions to return matching metrics for all captured Service Endpoints or services within the application.

This method avoids manually constructing an unfamiliar metric path and ensures that the application identifier, metric hierarchy, time-range parameters, and REST endpoint syntax are correct. Wildcards allow the analyst to query multiple Service Endpoint names, tiers, or metric branches in one request.

Direct access to the Controller’s underlying database is unsupported and bypasses the Controller API model. The Applications browser is useful for interactive analysis but does not itself provide the most direct REST-query construction workflow. “Consumed Endpoints” is not the required location for enumerating all Service Endpoint metrics through the REST interface.

Relevant CAAPA Study Guide topics include Metric Browser, Service Endpoint Metrics, Metric Data REST API, Metric Paths, Wildcard Queries, and REST URL Generation.

An AppDynamics Information Point can collect String values as custom data. Information Points instrument selected application methods so that analysts can monitor method-level performance and capture business context without defining the method as a complete Business Transaction.

Custom data is typically extracted from a method argument, return value, object field, or getter chain. The resulting String value can provide contextual information such as an order category, customer type, transaction status, product identifier, or processing state. This data is associated with the monitored method execution and can support detailed troubleshooting and business-level analysis.

Numeric values such as integers or floating-point numbers are generally treated as candidates for custom metrics, where AppDynamics can aggregate and report values over time. Boolean values are not the designated custom-data type for this Information Point configuration. The distinction is therefore between textual custom data, represented as a String, and numerical measurements intended for metric aggregation.

Relevant CAAPA Study Guide topics include Information Points, Method-Level Monitoring, Getter Chains, Custom Data Collection, Custom Metrics, Method Arguments, Return Values, and Business Context Capture.

The " Application Health Report " is a built-in scheduled report in AppDynamics that includes vital metrics such as load, response time, and error graphs. This report provides a comprehensive overview of the application ' s health and performance, making it an essential tool for Performance Analysts to regularly review and share with stakeholders to ensure the application meets performance standards and user expectations.

During a war room scenario, which is a real-time troubleshooting session, widgets in AppDynamics dashboards update in near real-time. This allows teams to observe the immediate impact of changes and identify issues as they occur.

The correct action is Make an HTTP Request. AppDynamics uses HTTP Request actions to send event information to external systems that expose a REST API, webhook, or other HTTP-based integration endpoint. A Performance Analyst can configure the destination URL, HTTP method, headers, authentication, and request body, then include AppDynamics event variables in the payload.

This allows a health rule violation, policy trigger, or other supported event to be posted directly into a third-party collaboration platform. The external tool can then display the alert in a channel, notify an operations team, or initiate its own workflow.

Create or Update a JIRA Ticket is intended specifically for issue-tracking integration rather than general collaboration-platform messaging. Take a thread dump is a diagnostic action used to capture application thread activity. Run a script or executable on problematic nodes is a remediation action and does not directly post an event to an external collaboration service.

Relevant CAAPA Study Guide topics include Policies, Alert Actions, HTTP Request Actions, Webhook Integrations, Event Templates, Health Rule Violations, and Third-Party Notification Workflows.

Periodic Transaction Snapshot thresholds can be configured at the Application level and overridden for an individual Business Transaction.

The application-level configuration establishes the default periodic snapshot behavior for all Business Transactions within the monitored application. This provides a consistent collection policy, including how frequently normal transaction snapshots are captured for ongoing diagnostic visibility.

For a particularly important or high-risk Business Transaction, the Performance Analyst can define transaction-specific settings. The individual-transaction configuration overrides the application default, allowing more frequent or specialized snapshot collection for critical operations such as checkout, payment authorization, login, or order submission.

Periodic snapshot thresholds are not configured directly at the node or tier level. Nodes inherit the transaction-monitoring configuration associated with their application and Business Transactions. Service Endpoints generate their own performance metrics, but they do not use the Business Transaction periodic snapshot threshold model independently.

This hierarchy enables broad application-wide governance while still allowing targeted diagnostic depth for selected transactions. Relevant CAAPA Study Guide topics include Transaction Snapshot Collection, Periodic Snapshots, Application-Level Snapshot Configuration, Business Transaction Overrides, Diagnostic Sessions, and Snapshot Collection Thresholds.