ACD200 Online Practice Questions and Answers

Correct Answer: BC

The question is about the recommendations for Appian environment to address the performance risk of a large increase in users. The following are two recommendations for this purpose: Add more process execution engines. This means adding more servers or nodes that can execute process instances in parallel, which can improve the scalability and availability of Appian. This can help handle the increased workload and demand from more users without affecting the response time or reliability of Appian. Add more application server memory. This means increasing the amount of memory allocated to each server or node that runs Appian components, such as web servers, engines, or analytics servers. This can help improve the performance and stability of Appian by reducing memory pressure and garbage collection. The following are not recommendations for Appian environment to address the performance risk of a large increase in users: Add more design engines. This means adding more servers or nodes that can execute expression rules or interface components in parallel, which can improve the performance and scalability of Appian. However, this is not directly related to the number of users, but rather to the complexity and frequency of expression rules or interface components in the application. Switch from a records-centric to a process-centric design. This means changing the application design to focus more on process models and tasks, rather than records and reports. This does not affect the Appian environment, but rather the application logic and functionality. This may or may not improve the performance of the application, depending on the requirements and use cases. References: Process Execution Engines Memory Recommendations Design Engines Records-Centric vs Process-Centric Design

Correct Answer: B

The xsd:key element is not supported within an Appian CDT. This element is used to define a key constraint for an element or a group of elements. Appian does not support key constraints in CDTs, as they are not relevant for data storage or manipulation. Instead, Appian uses primary keys and foreign keys to enforce uniqueness and referential integrity in CDTs. These keys are specified using the @Id and @JoinColumn JPA annotations, respectively. References: Supported XSD Elements and JPA Annotations

Correct Answer: BC

Two places to get information on process model memory usage are: Process monitoring tab. The process monitoring tab is a feature in the Appian Designer that allows you to monitor and manage the performance and status of process models and instances. You can use the process monitoring tab to view various metrics and statistics about your processes, such as memory usage, execution time, node count, error count, etc. You can also filter, sort, and export the data for further analysis. The process monitoring tab can help you identify which processes have the highest memory footprint and potential performance issues. Appian Health Check report. The Appian Health Check report is a tool that provides insights into application design patterns and performance risks in your environment. The report covers four areas of your environment: design, user experience, infrastructure, and configuration. The report also includes graphs highlighting historical trends, such as user activity, average response times, and resource utilization. The Appian Health Check report can help you identify which processes have the highest memory consumption and suggestions for mitigating them. References: Process Monitoring Tab, Understanding the Health Check Report

Correct Answer: B

The requirement is to find a list of expression rules that are causing performance issues, or have caused performance issues in the last 30 days. The best way to do this is to access the Rule Performance tab in the Administration Console, as it provides a dashboard that shows the execution time, frequency, and impact of expression rules in a given time period. You can filter the rules by application, rule type, or execution time, and sort them by various metrics. You can also drill down into each rule to see the details of its executions and test cases. The other options are not as effective or convenient for this purpose, as they either do not provide enough information, require manual inspection, or are not related to expression rules. References: Rule Performance

Correct Answer: A

The performance log that should be used to see the mean evaluation time of a slow-performing expression rule every hour is expressions_details.csv. This log records information about how expression rules are performing in the system,

such as the number of evaluations, the total time, the mean total time, and the standard deviation of the total time. The log is written to once every hour, and it provides fine-grain aggregation by type of expression rule. The mean total time

column shows the average time it took to evaluate an expression rule in milliseconds. Therefore, the correct answer is A.

References:

Expression Performance Logs

Performance Best Practices

Correct Answer: D

The most efficient method to insert the deleted row of a table into a history table for audit purposes is Trigger. This is because a trigger is a database object that automatically executes a specified SQL statement when a certain event occurs on a table or view. A trigger can be defined to run before or after a delete operation on a table, and can access the deleted row using a special table called deleted. A trigger can perform the insertion of the deleted row into the history table without any additional logic or overhead from Appian. References: Triggers

Correct Answer: ABC

The question is about choosing the right plug-in for a requirement that can only be achieved by using a plug-in. The following are three primary considerations in choosing the right plug-in: What are the compatible Appian versions? This is important because some plug- ins may not work with older or newer versions of Appian due to changes in APIs or features. You should check the plug-in documentation or release notes to see which Appian versions are supported by the plug-in. Is the plug-in Cloud-approved? This is important because some plug-ins may not be allowed in Appian Cloud environments due to security or performance reasons. You should check the Appian Cloud Approved Plug-ins list to see which plug-ins are approved for use in Appian Cloud. What are the limitations of the plug-in? This is important because some plug-ins may have known issues or limitations that could affect your requirement or use case. You should check the plug-in documentation or forums to see if there are any reported bugs or limitations for the plug-in. The following are not primary considerations in choosing the right plug-in: What is the size of the plug-in? This is not a major factor, as plug-ins are usually small in size and do not affect the performance or storage of Appian significantly. However, you should still follow the best practices for managing plug-ins and avoid installing unnecessary or unused plug-ins. Who is the plug-in author? This is not a decisive factor, as plug-ins can be authored by Appian, third-party vendors, or community members. However, you should still consider the reputation and reliability of the plug-in author and check their support and update policies. References: Plug-ins Appian Cloud Approved Plug-ins

Correct Answer: BD

Two things that can be done to increase the performance of a poorly- performing process model that has a lot of nodes and is mainly used to do background updates are: Remove all activity chaining. Activity chaining is a feature that allows a process to move from one node to another without waiting for a commit point. This can improve the performance of some processes, but it can also cause memory issues and data inconsistency if used excessively or incorrectly. Removing activity chaining can reduce the memory consumption and ensure data integrity of the process model. Refactor some nodes into subprocesses when possible. Subprocesses are processes that are called from within another process model. Refactoring some nodes into subprocesses can simplify the main process model and improve its readability and maintainability. It can also reduce the memory usage and execution time of the main process model, as subprocesses are executed in parallel and have their own memory allocation. References: Activity Chaining, Subprocess Node, Process Model Best Practices

Correct Answer: C

The correct representation of Appian best practices for using pie charts is to use pie charts to show proportional data. Pie charts are generally used to show how individual parts contribute to a whole, such as percentages or fractions. Pie charts should only be used to represent data that can be placed into distinct categories and should not consist of more than 6 slices. Pie charts should also include value and category labels for each slice, and sort the data values in ascending or descending order. References: Pie Chart Component, Charts UX Design Guide

Correct Answer: C

The likely cause for a task on a newly-launched process in Production being slow to respond to user input is having too many SAIL components on the task. SAIL components are the UI elements that make up an interface in Appian. Having too many SAIL components on a task can negatively impact the performance and user experience of the interface, as it increases the rendering time and complexity of the interface. It can also cause browser compatibility issues or memory leaks. It is recommended to limit the number of SAIL components on a task to less than 100, and to use grids, collapsible layouts, or tabs to organize and display data efficiently. References: SAIL Components Overview, SAIL Performance Tips