Cisco Updated 500-420 Exam Questions and Answers by anais

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 default value pair for the setting " Collect up to ____ snapshots per minute for _____ minutes " in the configuration for Slow Transactions is 10, 10. This means that by default, the system is set to collect up to 10 snapshots per minute for a duration of 10 minutes during a diagnostic session.

When an Information Point is created, AppDynamics automatically collects three core method-level KPIs: Response Time, Errors per Minute, and Calls per Minute.

Response Time measures how long the configured class and method take to execute. This enables the Performance Analyst to identify degradation in a critical internal operation and compare current behavior with historical trends or baselines.

Errors per Minute records the rate at which executions of the Information Point encounter errors. This provides direct visibility into failures associated with the monitored method, even when that method is not itself a Business Transaction entry point.

Calls per Minute measures invocation frequency. It is useful for tracking operational activity such as cache access, pricing calculations, order processing, or calls to a business-critical internal service.

Minimum Response Time, Maximum Response Time, and CPU Time are not the three standard KPIs automatically generated for an Information Point in this context. Additional business values can be collected separately by configuring custom data or custom metrics.

Relevant CAAPA Study Guide topics include Information Points, Method-Level Monitoring, Calls per Minute, Response Time, Errors per Minute, Custom Data, Custom Metrics, and Baseline Comparison.

The Application Agent supports a default maximum of 50 Service Endpoints per entry point type. An entry point type represents the technology or execution mechanism through which the monitored request enters the application, such as a servlet, web service, message listener, or asynchronous processing framework.

This limit prevents excessive endpoint registration and metric creation at both the Agent and Controller layers. When Service Endpoint detection rules identify more endpoints than the configured threshold for a particular entry point type, the Agent restricts registration to the permitted maximum. The limit can be governed through the relevant Agent node-property configuration, but the standard tested value is 50.

The asynchronous-worker-thread options are too narrowly scoped and do not describe the general Service Endpoint registration limit. Likewise, 25 endpoints per entry point type is not the standard default Application Agent threshold.

This distinction is important because Service Endpoints generate independent performance metrics while remaining subordinate to the associated Business Transaction. Relevant CAAPA Study Guide topics include Service Endpoint Detection, Agent and Controller Limits, Entry Point Types, Agent Node Properties, Metric Registration, and Business Transaction Visibility.