Correct Answer: A

The best process model design for a case management application is to use a case record and a related action. This way, the process flow does not have to wait for the reviewer to complete the task, which can take up to 7 days. This

reduces the memory impact of the process, as well as the risk of process timeouts or errors. The case record also provides a better user experience, as the reviewer can access the case details and the related action from one place.

Therefore, the best answer is A.

References:

Case Management

Related Actions

Correct Answer: CDE

An integration that modifies data can be called from three locations: web API (POST, PUT, DELETE), process model, and SAIL saveInto parameter. These locations allow for sending data to an external system or service and receiving a

response. Web API (POST, PUT, DELETE) are HTTP methods that are typically used to create, update, or delete data on a server. An integration that modifies data can be exposed as a web API with one of these methods, allowing external

applications or systems to invoke it through an HTTP request1.

Process model is a graphical representation of a business workflow that consists of nodes and flows. An integration that modifies data can be called from a process model using either an integration node or a Call Integration smart service2.

This allows for orchestrating complex workflows that involve data manipulation across different systems or sources.

SAIL saveInto parameter is a property of a SAIL component that specifies an expression to be evaluated when the component is modified by the user3. An integration that modifies data can be called from an interface using the saveInto

parameter of a SAIL component. This allows for triggering data changes based on user actions or events on the interface.

Correct Answer: A

The most appropriate testing method to achieve this using Appian is Unit Testing. This is because unit testing allows you to test individual components of your application, such as forms, rules, or expressions, in isolation from other components or dependencies. Unit testing can help you verify that your Related Action works as expected for different users and data scenarios, as well as identify and fix any errors or bugs before deploying your application to production. References: Unit Testing

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: AC

An index is a data structure that allows for faster retrieval of data from a table based on one or more columns. Indexes increase the performance of read operations, such as select queries, by reducing the number of records that need to be scanned. However, indexes decrease the performance of write operations, such as insert, update, and delete queries, by requiring additional work to maintain the index structure and ensure its consistency with the table data. Therefore, indexes should be used judiciously and only on columns that are frequently used in queries and have high selectivity (i.e., low number of duplicate values).

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: ACD

Three possible reasons for high memory consumption of a process model are: Too many process variables. Process variables are used to store data that is needed throughout the process execution. However, having too many process variables can increase the memory usage of the process engine, especially if the variables store large or complex data types, such as documents or CDTs. It is recommended to use local variables whenever possible, and to delete or nullify process variables that are no longer needed. Nested CDTs with large numbers of fields. CDTs are custom data types that define the structure and validation of business data in Appian. CDTs can be nested within other CDTs to create complex data models. However, nesting CDTs with large numbers of fields can result in high memory consumption and performance degradation, as each field requires additional memory allocation and processing. It is recommended to limit the number of fields and nesting levels of CDTs, and to use references instead of embedding whenever possible. Too many nodes. Nodes are the graphical elements that represent the activities and events in a process model. Having too many nodes in a process model can increase the memory usage and complexity of the process execution. It can also make the process model harder to read and maintain. It is recommended to simplify the process model by using subprocesses, smart services, or expression rules to encapsulate common or reusable logic. References: Process Variables, Custom Data Types, Process Model Best Practices

Correct Answer: BC

The question is about troubleshooting slow response times on a SAIL interface. The following are two potential causes of the performance issues:

Multiple a!save operations: This means that the interface has multiple expressions that use a!save to store data in variables or update components. This can cause performance issues, as each a!save operation triggers a server round-trip

and refreshes all dependent components on the interface. You should minimize the use of a!save operations and use local variables or component parameters instead.

Configuration of refresh variables: This means that the interface has components that use refresh variables to control when they should be refreshed based on changes in other components or variables. This can cause performance issues,

as some components may be refreshed unnecessarily or too frequently due to incorrect or excessive refresh variables. You should optimize the refresh variables and use them only when needed.

The following are not likely causes of slow response times on a SAIL interface:

Multiple rule inputs: This means that the interface has expressions that use rule inputs to pass data or parameters to expression rules. This does not affect the performance of the interface, as rule inputs are evaluated on the server and do not

cause additional server round-trips or refreshes. Stacked button layout: This means that the interface has a layout component that arranges buttons in a vertical stack. This does not affect the performance of the interface, as it is a simple

layout component that does not require any server interaction or refresh logic.

References:

a!save()

Refresh Variables

Rule Inputs

Stacked Button Layout

Correct Answer: C

The instances of the process model that will be affected by modifying the automatic process clean-up settings are future and past instances of the process model. The automatic process clean-up settings allow you to specify how long completed or canceled processes should be kept before being archived or deleted. These settings apply to all instances of the process model, regardless of when they were started or completed. However, these settings do not affect any subprocesses that are part of the process model. Subprocesses have their own archival settings that can be configured separately. References: Automatic Process Clean-up Settings, Archiving Processes