Appian ACD200 Exam Questions & Answers

Correct Answer: BCD

Activity chaining is a feature that allows users to complete multiple tasks in a row without returning to their task list. However, activity chaining can also have some drawbacks, such as increased memory consumption, longer transaction times,

and reduced user feedback. Therefore, some actions can be taken to make the process model more efficient, such as:

Shorten long process chains by combining transactions into the smallest number of nodes. This can reduce the memory footprint and the database load of the process model.

Avoid chaining system nodes like Integrations. These nodes can have unpredictable execution times and can cause timeouts or errors if chained. It is better to use asynchronous integrations or message events to decouple the process flow

from external systems.

Move transactions that can be done asynchronously outside of the chain. This can improve the responsiveness of the process model and allow parallel processing of independent tasks.

Therefore, the correct answers are B, C, and D.

References:

Activity Chaining

Performance Best Practices

Correct Answer: D

According to Appian best practices, the preferred style and size for the images to display the profile picture of each employee inside an employee grid are style: "AVATAR" and size: "SMALL". This is because the avatar style creates a circular image that is suitable for profile pictures, and the small size creates a 32x32 pixel image that fits well inside a grid cell. The standard style creates a rectangular image that may not look good for profile pictures, and the large size creates a 128x128 pixel image that may be too big for a grid cell. References: Image Component

Correct Answer: B

Creating a trigger on the database table to capture the audit trail to a table is the most efficient and has the least impact on the Appian application, because it avoids adding extra logic or calls to the Appian application, which could affect its performance and scalability. A trigger is a database object that automatically executes when a specified event occurs on a table or view. A trigger can be used to insert, update, or delete data from another table based on the changes made to the original table. References: [Triggers], [Audit Trail]