Cisco AppDynamics Associate Performance Analyst 500-420 CAAPA Exam Questions

Answer : D

The Performance Analyst should open the Business Transactions view and enable Show Trends. This presents historical behavior for individual Business Transactions, making it possible to identify which transactions experienced a decline in calls per minute and when the change began. The analyst can compare workload patterns across transactions and correlate the decrease with changes in response time, errors, transaction activity, or application usage.

The Top Business Transactions by Load widget emphasizes the highest-volume transactions for the selected period, but it may not clearly expose transactions whose volume has sharply declined. Plotting application-level Calls/min in the Metric Browser confirms that total workload decreased but does not immediately identify the affected Business Transactions. The Application Flow Map focuses on tier and dependency relationships, while Transaction Score summarizes transaction performance classifications rather than workload trends.

The Show Trends capability is therefore the most direct method for examining historical transaction behavior and isolating the Business Transactions responsible for the workload change.

Relevant CAAPA Study Guide topics include Business Transaction Monitoring, Show Trends, Calls per Minute, Workload Analysis, Historical Comparison, and Application Performance Troubleshooting.

Answer : C

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.

Answer : C, F

Memory Used% and CPU %Busy are the two KPIs that directly measure server-level resource consumption.

Memory Used% represents the proportion of physical memory currently consumed on the monitored server. A sustained high value can indicate memory pressure, excessive process allocation, insufficient capacity, or conditions that may lead to paging and degraded application performance.

CPU %Busy measures the percentage of processor capacity actively being used. It is a primary indicator of compute-resource utilization and helps identify CPU saturation, processing bottlenecks, or insufficient server capacity. Persistent high CPU utilization may correlate with increased response time, transaction queuing, and reduced throughput.

The remaining options describe availability, application behavior, or transaction performance rather than direct infrastructure-resource consumption. Calls per Minute measures workload volume, Average Response Time measures transaction latency, Availability indicates whether a system or service is reachable, and Application Restarts records lifecycle events.

Relevant CAAPA Study Guide topics include Server Visibility, Infrastructure Monitoring, Hardware Resource Metrics, CPU Utilization, Memory Utilization, and Correlating Server Health with Application Performance.

Answer : A

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.

Answer : B, D, F

The three KPIs that most directly quantify customer experience are Business Transactions 94th Percentile Response Time, End User Response Time, and Business Transactions Errors per Minute.

The 94th percentile response time indicates how long the majority of Business Transaction executions take while reducing the masking effect of averages. It reveals whether a meaningful portion of customers is experiencing slow checkout, search, cart, or order-processing operations.

End User Response Time measures the customer-observed time required for a browser or mobile interaction to complete. It includes client-side processing, network latency, content loading, and server response, making it the most direct representation of perceived application performance.

Business Transactions Errors per Minute quantifies failed application operations. A rising error rate can represent unsuccessful logins, payment failures, rejected orders, or other outcomes that directly impair the customer journey.

Network incoming errors, Machine Agent availability, and CPU utilization are valuable infrastructure indicators, but they measure supporting-system health rather than customer experience itself.

Relevant CAAPA Study Guide topics include End User Monitoring, Business Transaction Performance, Percentile Response Time, Error Monitoring, Customer Experience KPIs, and Application Performance Correlation.

Answer : A

By default, an active health rule violation displayed on the Health Rules Violations page is updated at 30-minute intervals after the initial violation event is triggered. AppDynamics first evaluates the health-rule condition against the configured critical or warning criteria. When the condition remains true for the configured evaluation and wait period, the Controller opens a health rule violation event.

While that violation remains active, AppDynamics periodically updates its displayed status and associated event information. The default continuation-update interval is 30 minutes. The violation is subsequently closed when the monitored metric no longer satisfies the violation criteria for the required duration.

The wait time after violation determines how long a condition must persist before AppDynamics opens the violation; it does not define the ongoing update frequency. The page is also not limited to updating only when a new violation starts, nor must an existing violation close before updated information can be recorded.

Relevant CAAPA Study Guide topics include Health Rule Evaluation, Warning and Critical Conditions, Wait Time After Violation, Health Rule Violation Events, Violation Lifecycle, and Controller Event Updates.

Answer : D

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.