Appian ACD101 Appian Certified Associate Developer Exam Practice Test

Answer : C

To achieve the behavior where users see only 'active' vehicle records by default but can also view all records when needed, you should configure a user filter for the status field on the Vehicle record list. This user filter should have a default value set to 'active', which will filter the list to only show active records initially. However, users will still have the option to adjust the filter to see all records, thus accommodating occasional auditing requests. Reference: Appian Documentation - Record List Filters and User Filters

Answer : A

Robotic Process Automation (RPA) is the Appian feature designed to automate repetitive manual tasks, especially in scenarios where interacting with systems without APIs is necessary. RPA bots can mimic human actions, such as navigating through system interfaces, extracting data, and entering information, effectively bridging the gap between digital processes and systems that lack API integrations. This capability is particularly useful for integrating legacy systems into modern workflows, streamlining operations that would otherwise require manual intervention. Reference:

Appian Documentation on RPA: Explains how RPA can be leveraged within Appian to automate tasks, providing examples and best practices for implementing RPA bots in business processes.

Answer : C

The union() function in Appian combines the elements of two or more arrays into a single array, removing any duplicate values. Given that the rule inputs ri!fruit and ri!vegetables are configured as text arrays, the expected output of union(ri!fruit, ri!vegetables) would be an array containing all unique items from both ri!fruit and ri!vegetables, with any duplicates removed. This function is useful for combining lists without repetition, ensuring a clean, unique set of elements. Reference: Appian Documentation - Expression Functions

Answer : A

In Appian, the data type of a local variable is inferred from the value it is set to. Unlike some other programming languages where the data type must be explicitly declared, Appian determines the data type automatically based on the initial value assigned to the local variable. Local variables in Appian are quite flexible and can store various types of data, including complex data types, not just primitive ones. Reference: Appian Documentation - Local Variables

Answer : C

Data sync enables additional features for record types in Appian. With data sync enabled, you can define relationships between different record types, add fields to a record type that do not appear in the source database (hidden fields), and configure record-level security to control access to individual records based on user roles or other criteria. These features are part of the enhanced functionality provided by data sync to ensure efficient data management and security within Appian applications. Reference: Appian Documentation - Record Type Features and Data Sync

Answer : C

To control the visibility of a record action based on certain user conditions or expressions, the security settings of the record action itself must be configured. This involves defining conditions or expressions within the record action's security settings that evaluate whether a user meets the criteria to see and interact with the action. This method allows for dynamic control over the accessibility of actions based on user roles, specific attributes, or other contextual factors, ensuring that only authorized users can see and execute the action under specified conditions. Reference:

Appian Documentation on Record Actions: Details how to configure and secure record actions, including visibility and permissions, to tailor the user experience within record views.

Answer : B

In Appian, when dealing with a record type that has data sync enabled and is backed by a database table, changes to the structure of the underlying data model, such as removing a field, should be carefully managed. The correct approach involves deleting the unused field from the Custom Data Type (CDT) that defines the structure of the data for the record type. Following this change, a full resynchronization of the record type is necessary to ensure that the changes in the CDT are reflected in the record type and its associated data in Appian. This process ensures data integrity and consistency across the application and the database. Reference:

Appian Documentation on Data Management: Provides guidelines on managing data structures, including CDTs and record types, within Appian applications.