Appian ACD101 Appian Certified Associate Developer Exam Practice Test

Answer : C

When dealing with related data types where one has a foreign key to another, you must first create the record in the primary table (ACME_invoice) and then use the generated primary key to create related records in the secondary table (ACME_invoiceItem). This is why you first write to the ACME_invoice table, then update the foreign keys in a Script Task, and finally write to the ACME_invoiceItem table.

Appian Documentation: Relational Databases

Answer : A

To start a process using an email trigger, you need to configure the process model to listen for an email event. This is done by going to File > Properties > Alerts in the process model properties dialog and configuring the Custom Alert settings. Here you can specify the email address that will trigger the process when an email is sent to it. Reference: Appian Documentation - Configuring Alerts in Process Models

Answer : B

The best practice for naming variables in Appian is to use clear and descriptive names that convey the purpose or content of the variable. Therefore, local!applicantHeight is the best option as it precisely describes the value contained by the variable, which is the height of an applicant. This naming convention aids in readability and maintainability of the code, making it easier for developers to understand and modify the code in the future. Reference: Appian Best Practices - Expression Writing and Naming Conventions

Answer : C

Based on the default behavior for task assignments in Appian, when a User Input Task is assigned to a group, any one member of the group can accept the

task. Once accepted, the task becomes locked to that user, and they are responsible for completing it. This prevents multiple users from working on the same task simultaneously and ensures clear accountability. Reference: Appian Documentation - Task Assignments and User Input Tasks

Answer : B

When configuring a Related Action for an entity-backed record type, the proper domain prefix to reference the record data passed into the Process Model as context for the Record Action is pv!. This prefix stands for process variables, which are used to pass data into and out of a process model. In the context of a Related Action, pv! would be used to reference the specific process variables that are configured to receive the record data. Reference: Appian Documentation - Process Variables and Record Types

Answer : C

Given that ri!name is defined as 'Maria' and ri!directory contains two a!map() structures, one of which includes the name 'Maria,' the expression wherecontains(ri!name, index(ri!directory, 'name')) will evaluate as follows: The index() function will return a list of values from ri!directory for the key 'name,' which will be {'Maria', 'Steven'}. The wherecontains() function will then check where 'Maria' is found within this list. Since 'Maria' is the first element, the function will return a list of indices where 'Maria' is found, in this case, {1}. Appian lists are 1-indexed, so the first position is represented by 1, not 0. Reference: Appian Expression Language Documentation - Functions

Answer : C

The critical step in passing information from a form back to a process model is to configure inputs on the Data tab of a User Input Task. When you create a User Input Task, it includes a form for users to interact with. The data entered into this form can be mapped to process variables via the Data tab configuration. This ensures that the information collected in the form is available to the process for further use. Reference: Appian Documentation - User Input Tasks