Questions for the ACD101 were updated on : Nov 21 ,2025
What is the Production environment used for?
C
Explanation:
The Production environment in Appian is used for allowing business users to use the final version of
the application. This environment is where fully developed, tested, and approved applications are
deployed for end-user interaction. It is the live environment that supports actual business
operations, ensuring that users have access to stable and reliable application functionalities for their
day-to-day tasks.
Reference:
Appian Documentation: Application Environments
You want to add a script task in between two User Input Tasks assigned to the same user.
What needs to be configured so that the user sees the second form immediately after submitting the
first?
B
Explanation:
To ensure that the user sees the second form immediately after submitting the first, when adding a
script task between two User Input Tasks assigned to the same user, it is essential to enable activity
chaining. Activity chaining in Appian allows for the seamless transition between user tasks within a
process, eliminating unnecessary delays and enhancing the user experience by immediately
presenting the subsequent task.
Reference:
Appian Documentation: Activity Chaining in Processes
You received a support ticket where the user claims that nothing happens when they click the button
to complete a task. You confirm that the user is assigned to the task.
What is a possible reason for this problem?
C
Explanation:
If a user claims that nothing happens when they click a button to complete a task, a possible reason
could be that the button was not configured to submit the form. This configuration is essential for
triggering the form submission action, which in turn can complete the task or initiate further
processes. Without this setup, clicking the button will not result in any action.
Reference:
Appian Documentation: Configuring Buttons in Interfaces
Which option best describes the primary purpose of the interface design object?
B
Explanation:
The primary purpose of the interface design object in Appian is to provide a method for end users to
interact with an Appian application. Interfaces are the user-facing components that allow for the
input, display, and manipulation of data within the application, facilitating user engagement and task
completion.
Reference:
Appian Documentation: Interface Design
You are running a process instance and an error occurs on an unattended node.
What happens to your process when this error occurs?
A.
• The process is not paused.
• Parallel paths in the process continue to proceed.
• An alert is sent to the appropriate recipients (usually admins).
• These nodes are not included in the num_problem_tasks process metric in process reports.
B.
• The process is paused.
• Parallel paths in the process are stopped.
• No alerts are sent.
• These nodes are included in the num_problem_tasks process metric in process reports.
C. • The process is paused.
• Parallel paths in the process are stopped.
• An alert Is sent to the process initiator.
• These nodes are included in the num_problem_tasks process metric in process reports.
A
Explanation:
When an error occurs on an unattended node in a running process instance:
The process is not paused, allowing other parallel paths to continue.
An alert is typically sent to appropriate recipients, such as administrators, to notify them of the issue.
These nodes are not counted in the num_problem_tasks process metric, which is used in process
reports to track problematic tasks.
This behavior ensures that the rest of the process can continue as intended while alerting
administrators to intervene and address the error.
Reference:
Appian Documentation: Error Handling in Processes
What is an Appian best practice for calling interface rules on your interface?
C
Explanation:
An Appian best practice for calling interface rules within your interfaces is to always use a consistent
ordering of rule parameters. This practice enhances the readability and maintainability of your
interfaces, ensuring that other developers can understand and modify the interface more easily.
Reference:
Appian Documentation: Designing Interfaces
Which two groups can be set within Application Properties? (Choose two.)
A, C
Explanation:
Within Application Properties in Appian, you can set two groups: Administrators Groups and Users
Groups. The Administrators Group is responsible for managing and configuring the application, while
the Users Group is designated for end-users who interact with the application's functionalities.
Reference:
Appian Documentation: Application Properties
How can you add test data into your rule inputs while editing an interface object?
B
Explanation:
While editing an interface object in Appian, you can add test data into your rule inputs by selecting
the Test button. This feature allows you to simulate how the interface would behave with specific
inputs, facilitating a more efficient and accurate design and debugging process.
Reference:
Appian Documentation: Testing Interfaces
You need to create a record type with data sync enabled.
What are the supported data sources?
C
Explanation:
Appian's data sync feature supports synchronization from three primary data sources: Salesforce,
Process Models, and Databases. This allows for the creation of record types that can efficiently access
and manipulate data from these sources, leveraging Appian's capabilities to provide real-time
insights and interactions with external systems and internal processes.
Reference:
Appian Documentation: Creating Record Types
You need to be able to define record type relationships.
What is a required prerequisite in Appian?
A
Explanation:
To define record type relationships in Appian, it's required that the record types have data sync
enabled. This is necessary to ensure that the data is readily available in Appian for the relationships
to be established and maintained.
Reference:
Appian Documentation: Record Type Relationships
An interface references an expression rule.
What are the relationships between these objects?
B
Explanation:
In Appian, when an interface references an expression rule, the interface is considered a dependent
because it depends on the expression rule to function correctly. Conversely, the expression rule is a
precedent because the interface relies on it.
Reference:
Appian Documentation: Managing Application Contents
After selecting a record, a user wants to initiate an activity in the context of that selected record.
You start by creating the process model that implements this activity.
What should you do next?
C
Explanation:
a record related action. This allows the action to be performed in the context of a specific record,
making it straightforward for users to initiate processes directly from the record view.
Reference:
Appian Documentation: Record Related Actions
You have two Custom Data Types (CDT): ACME_invoice and ACME_invoiceItem that have a flat
relationship.
The invoice item table has a field that is a foreign key to the invoice table. You are leveraging the
database to automatically generate their primary keys.
How should you structure the process model to add a new invoice and the new invoice items to the
system?
A.
1. Write to Multiple Data Store Entities smart service (Writing to the ACME_invoiceItem table and
ACME_invoice table).
B. 1. Write to Data Store Entity smart service (Writing to the ACME_invoiceItem table).
2. Script Task to update foreign keys.
3. Write to Data Store Entity smart service (Writing to the ACME_invoice table).
C.
1. Write to Data Store Entity smart service (Writing to the ACME_invoice table).
2. Script Task to update foreign keys.
3. Write to Data Store Entity smart service (Writing to the ACME_invoiceItem table).
C
Explanation:
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.
Reference:
Appian Documentation: Relational Databases
Which two scenarios are ideal for using Appian Portals? (Choose two.)
B, C
Explanation:
Appian Portals are designed for scenarios where users who do not have an Appian account need to
interact with Appian applications. This makes them ideal for public-facing applications such as
surveys (Option B) or for allowing external users to initiate processes like registrations (Option C).
They are not intended for internal use by employees (Option A) or for scenarios requiring offline
capabilities (Option D).
Reference:
Appian Documentation: Appian Portals
You are working on a process model "VIM Update Vehicle."
You want to call another process "VIM Get Service Date" that accepts pv!vehicleId as a process
parameter and sets a value for pv!serviceDate. The next node in VIM Update Vehicle depends on the
value of pv!serviceDate.
Which node should you use to execute "VIM Get Service Date" from VIM Update Vehicle?
C
Explanation:
When a process model depends on the value of a variable being set by another process, a
synchronous subprocess should be used. This ensures that the calling process (VIM Update Vehicle)
will wait for the subprocess (VIM Get Service Date) to complete and set the necessary pv!serviceDate
value before continuing. The subprocess node should be configured with input and output variables
to pass the pv!vehicleId and receive the pv!serviceDate.
Reference:
Appian Documentation: Subprocess Node