Appian Certified Associate Developer ACD101 Exam Practice Test

Answer : A

In Appian, to navigate from a record summary to an external URL, you can use a Button component configured with a 'Link' action. This approach allows you to define a URL that the button will navigate to when clicked. The Button component offers flexibility in terms of design and functionality, making it suitable for such navigation purposes within Appian interfaces. You can specify the URL directly in the Button's properties, allowing for dynamic link generation based on record data if needed. Reference:

Appian Documentation: Designing Interfaces (This section provides comprehensive details on using various interface components, including buttons, to achieve specific user interaction goals within Appian.)

Appian Documentation: Buttons (This page specifically focuses on the Button component, detailing its properties, usage, and how to configure it for different actions, including navigating to an external URL.)

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

Answer : C

For a pizza ordering form where you do not want the radio button selection labels to be truncated, the Stacked layout is the most appropriate. This layout will list the options vertically, giving each one adequate space and preventing truncation, which is particularly useful when the labels include longer text, such as a list of toppings. Reference: Appian Documentation - Interface Components

Answer : A, C

In Appian, to store documents such as those required for customer onboarding, you should configure a Knowledge Center and within that, Folders. The Knowledge Center in Appian serves as the top-level container for storing and organizing documents and folders. Folders within a Knowledge Center provide a way to categorize and manage access to documents, making them an essential part of document management in Appian applications. Decision Objects and Feeds are not related to document storage. Reference: Appian Documentation - Knowledge Centers and Folders

Answer : A, B

When creating a new application in Appian and opting to generate groups and folders for organization and security, Appian automatically creates specific groups to facilitate application development and management. The default groups include 'Administrators' and 'Designers' with the application prefix, in this case, ACM. The ACM Administrators group is intended for users who will have full control over the application, including configuration and deployment aspects. The ACM Designers group is designated for users primarily involved in the design and development of the application, granting them necessary permissions to create and modify application components without full administrative privileges. Reference:

Appian Documentation on Application Design: Offers insights into best practices for structuring and securing Appian applications, including the use of groups for effective application management.

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