Appian ACD200 - Questions & Answers

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 request 1.
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 service 2. 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 user 3. 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.

The question is about approving or rejecting an incoming deployment. The following roles allow you to do so: Specified Reviewer Group: This is a group that can be specified by the application administrator when creating a deployment package. Members of this group can approve or reject the deployment package in the target environment. System Administrators: This is a group that has full access and control over all applications and system settings in Appian. Members of this group can approve or reject any deployment package in any environment. Application Administrators Group: This is a group that has full access and control over a specific application in Appian. Members of this group can approve or reject any deployment package for their application in any environment. The following roles do not allow you to approve or reject an incoming deployment: Application Viewers: This is a group that has read-only access to a specific application in Appian.
Members of this group cannot approve or reject any deployment package for their application in any environment. Application Editors: This is a group that has edit access to a specific application in Appian.
Members of this group can create and export deployment packages for their application in any environment, but they cannot approve or reject them.
References:
Deploying Applications
Application Roles

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

The two statements about the a!queryEntity() function that are true are: The entity value must be given as a constant of type Data Store Entity. This is because the entity value specifies which data store entity (table or view) to query from. The value must be a constant that references an existing data store entity in Appian Designer. You cannot use a variable or an expression for this value. Setting the fetchTotalCount parameter to False can improve the performance of the rule. This is because setting this parameter to False tells Appian not to calculate the total number of records that match the query criteria, which can be an expensive operation for large data sets. By default, this parameter is set to True, which means Appian will return the total count along with the query results.
References:
a!queryEntity() Function