Question 8 - Appian ACD201 Real Exam Questions [March 2026 Update]

Q: 8

DRAG DROP You're executing a performance test of the client's application. You notice that server-side resources are at high-to-critical operating levels. What should you do to troubleshoot this issue? Note: To answer, move all steps from the Options list to the Answer List area and arrange them in the correct order.

Drag & Drop

Enable JavaScript to use the Drag & Drop feature.

Validate the test scenario by validating test script behavior matches performance acceptance criteria.
Analyze the performance of the application by reviewing system resources, application logs, and process reports.
Validate that non-test loads are not occurring in the environment during the test, by looking for other users logged in, active processes not run by test, et cetera.
Investigate if the system has cascading errors or unexpected process flows.
Analyze system resources and perform sizing exercise to validate if more resources or configuration changes are required.

Correct Answer:

Answer Area Bucket 1: C. Validate that non-test loads are not occurring in the environment during the test, by looking for other users logged in, active processes not run by test, et cetera. Bucket 2: A. Validate the test scenario by validating test script behavior matches performance acceptance criteria. Bucket 3: D. Investigate if the system has cascading errors or unexpected process flows. Bucket 4: B. Analyze the performance of the application by reviewing system resources, application logs, and process reports. Bucket 5: E. Analyze system resources and perform sizing exercise to validate if more resources or configuration changes are required.

Explanation

The troubleshooting workflow follows a logical process of elimination, moving from external factors to internal application analysis:

Environment Sanity (Isolation): First, ensure the resource spike isn't caused by external interference (e.g., antivirus scans, background backups, or rogue users). If the environment isn't isolated, further analysis is moot.
Test Validity (The Input): Next, verify the test script itself. An incorrect script (e.g., zero "think time" or infinite loops) can artificially saturate resources. This rules out "self-inflicted" issues.
Functional Health (The Errors): Check for "cascading errors." System failures (like infinite retry loops on failed connections) often manifest as high CPU/Memory usage. This identifies if the load is a symptom of a functional bug.
Deep Analysis (The Bottleneck): Once external factors, scripts, and obvious errors are ruled out, analyze specific logs and counters to identify inefficient code or processes consuming the resources.
Capacity Planning (The Resolution): Finally, if the application is functioning correctly and efficiently but still hits limits, conduct a sizing exercise to determine if hardware scaling (adding resources) is the necessary solution.

References

Microsoft Patterns & Practices, Performance Testing Guidance for Web Applications, "Chapter 17: Analyzing Performance Testing Data." This guide outlines the hierarchy of isolating bottlenecks, prioritizing environment validation and test integrity before code analysis.

ISTQB, Advanced Level Syllabus - Performance Testing, Section 4.2 "Performance Test Analysis," which mandates validating the test environment and data integrity prior to drawing conclusions about system performance.

Meier, J.D., et al., Performance Testing Guidance for Web Applications, Microsoft Corporation, 2007. (Specifically regarding the methodology of "Detecting Bottlenecks" and determining if issues are infrastructure or application-related).

Premium Access Includes

FLASH OFFER

avail 10% DISCOUNT on YOUR PURCHASE