Free Questions for ACD101 by dumpssheet

Shared by Berg on 09-08-2024

For More Free Questions and Preparation Resources

Check the Links on Last Page

Question 1
Question Type: MultipleChoice

You need to add a new attribute to your database-backed synced Acme employee record.

What should you do?

Options:
A- Add the new field manually to the ACME_Employee database table and run a database script to resync the Acme employee record.

B- In the record data model, you add the new field in the ADD SOURCE FIELDS. Save the field with the Update Table checkbox active.

C- In the record data model, you add the new field with ADD RELATIONSHIPS. Save the newly created relationship and use the field.

Answer:
B

Explanation:
To add a new attribute to a database-backed synced record type, such as an Acme employee record, you should add the new field
under the 'Add Source Fields' section in the record data model configuration. When you save this new field with the 'Update Table'
checkbox selected, Appian will automatically update the underlying database table and resync the record type with the new field
 included. Reference: Appian Documentation - Modifying Record Data Models

Question 2
Question Type: MultipleChoice

You have two record types: ACME_Student and ACME_Class.

You need to add a many-to-many relationship between these two record types.

What should you do?

Options:
A- Create a new record type with data sync enabled, then add a one-to-many relationship from each record type (ACME_Student and
ACME_Class) to the new mapping record type.

B- This relationship cannot be modeled using record type relationships.

C- Add the relationship from either ACME_Student or ACME_Class, then select Many-to-Many under Relationship Type, and add the
corresponding keys.
 Answer:
A

Explanation:
To establish a many-to-many relationship between two record types in Appian, you should create a junction or mapping record type that
will handle the many-to-many association. This new record type should have two one-to-many relationships, one to each of the original
record types (ACME_Student and ACME_Class). This setup allows each student to be associated with multiple classes and each class
to be associated with multiple students. Reference: Appian Documentation - Record Type Relationships

Question 3
Question Type: MultipleChoice

What are three ways to trigger a process from a process model? (Choose three.)

Options:
A- Use a subprocess.
 B- Call a web API.

C- Use a!recordActionItem().

D- Use a Start Process smart service.

E- Run a!startProcess() from a script task.

Answer:
A, D, E

Explanation:
There are multiple ways to trigger a process from a process model in Appian:

A subprocess is a process model that is called from within another process model.

A Start Process smart service is a flow element that you can use within a process model to start another process.

The a!startProcess() function can be used within a script task to start a process programmatically. These methods allow a developer to
initiate a new process instance from an existing process. Reference: Appian Documentation - Process Model Triggers and Smart
Services

Question 4
Question Type: MultipleChoice

You need to start a process using an email trigger.

How should you configure this process model using the Process Model Properties dialog?

Options:
A- Go to File > Properties > Alerts. Configure the Custom Alert settings.

B- Go to File > Properties Set the proper Process Display Name

C- Go to File > Properties. Select the Public Events checkbox to allow anyone to fire triggers.

Answer:
A

Explanation:
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
Question 5
Question Type: MultipleChoice

You are using a local variable in an expression rule to describe the height of an applicant.

Which statement correctly describes the application of Appian best practices for naming your local variable?

Options:
A- local!hoaa - This employs the naming convention of abbreviating 'Height of an applicant' to minimize both the typing required by
developers and the length of code Appian is required to parse.

B- local!applicantHeight - This employs the naming convention of specifically describing the value contained by the variable.

C- local!x - This employs the naming convention of using algebraic variables for a value that may either change over time or be used by
future developers for other purposes.

Answer:
B
 Explanation:
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

Question 6
Question Type: MultipleChoice

You are configuring an employee onboarding User Input Task that will be assigned to the human resources group.

Based on the default behavior for task assignments, which statement is valid?

Options:
A- Multiple users can accept the task at the same time up until the point that the first user completes it.

B- For each user in the group, a task is generated and assigned to them to complete.

C- One user in the group can accept the task for themselves and complete it.
 Answer:
C

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

Question 7
Question Type: Hotspot

Match each Appian Design Object name to the most applicable use case.

Note: Each use case will be used once or not at all. To change your responses, you may deselect your response by clicking the blank
space at the top of the selection list.
 Explanation:

Appian Documentation: Data Types, Process Models, Constants

Question 8
Question Type: MultipleChoice

You are configuring a Related Action for an entity-backed record type.

What is the proper domain prefix to reference the record data that will be passed into the Process Model as context for the Record
Action?

Options:
A- ac!

B- pv!

C- rv!
 Answer:
B

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

Question 9
Question Type: Hotspot

Match each scenario to the correct relationship type in your data model design.

Note: Each relationship type will be used once. To change your responses, you may deselect your response by clicking the blank space
at the top of the selection list.
Explanation:

Appian Documentation: Data Modeling in Appian

To Get Premium Files for ACD101 Visit
https://www.p2pexams.com/products/acd101

For More Free Questions Visit

https://www.p2pexams.com/appian/pdf/acd101