View Full Appian ACD201 Exam Dumps and Practice Test Dumps.

Question 201. What is the PRIMARY purpose of user filters on an Appian record list?

1. To modify record-level security dynamically
2. To allow application users to refine which records are displayed
3. To permanently delete records that do not meet selected criteria
4. To change the data source used by the record type

Correct Answer: 2. To allow application users to refine which records are displayed

Explanation:

User filters provide an interactive way for application users to narrow the records displayed in a record list or records-powered grid. Developers can configure filters based on record fields or related record fields, allowing users to select values such as status, region, category, or date ranges. User filters affect the displayed result set rather than changing the underlying record data or its security configuration. Multiple user filters can also be applied together, making it easier for users to locate relevant information in large datasets. Properly designed filters improve usability while keeping filtering logic close to the record type.

Question 202. Two different user filters are applied to a record list at the same time. How does Appian generally combine them?

1. The second filter completely replaces the first
2. Appian randomly chooses which filter to evaluate
3. Records matching either filter are always returned
4. Records must satisfy the criteria of all applied user filters

Correct Answer: 4. Records must satisfy the criteria of all applied user filters

Explanation:

When multiple user filters are active on an Appian record list, the filters are combined so that returned records must satisfy the criteria of each filter. For example, if users select an Open status filter and specify a particular submitted-date range, the resulting list contains records that satisfy both requirements. Within an individual list filter, however, multiple selected options can normally behave differently by allowing records that match any of those selected choices. Understanding the distinction between combining separate filters and selecting several options inside one filter is important when developers design predictable record-list filtering experiences.

Question 203. A record list needs a user filter whose available options are generated dynamically from application data. Which approach is MOST appropriate?

1. Configure the user filter using an expression
2. Hard-code every possible value in the record-list description
3. Create a process model for every filter option
4. Use a site visibility expression instead

Correct Answer: 1. Configure the user filter using an expression

Explanation:

Expression-based user filters are appropriate when the available options must be generated dynamically. Appian allows developers to construct user filters using functions such as a!recordFilterList() or a!recordFilterDateRange(). The expression can retrieve or reference values from records, variables, constants, or other sources. Guided configuration is convenient when a small, static collection of options is sufficient, while expression configuration provides greater flexibility for changing or data-driven values. Appian also recommends considering an expression rule for complex filter expressions so the logic can benefit from versioning, reuse, and testing independently of the record type configuration.

Question 204. What is a record list action typically used for?

1. To modify the security of every record simultaneously
2. To replace the Summary view of an existing record
3. To initiate functionality such as creating a new record from the record list
4. To permanently disable record search

Correct Answer: 3. To initiate functionality such as creating a new record from the record list

Explanation:

A record list action is exposed in the context of the overall record list rather than a specific existing record. A common example is a Create action that allows a user to add a new employee, customer, case, or other business entity. This differs from a related action, which operates in the context of a particular record, such as updating or deleting one employee. Record lists can provide search, filters, and actions together in one drillable experience, allowing users to find information and initiate relevant business processes without navigating to unrelated interfaces.

Question 205. Which scenario is BEST suited to an Appian related action rather than a record list action?

1. Creating a brand-new customer without selecting an existing customer
2. Opening a general application dashboard
3. Displaying the entire customer record list
4. Updating the contact information for one selected customer record

Correct Answer: 4. Updating the contact information for one selected customer record

Explanation:

Related actions are associated with a particular record instance. When a user opens a specific customer, employee, order, or case, related actions can provide operations that apply to that exact record, such as Update, Close, Approve, or Delete. A record list action is instead associated with the list as a whole and commonly supports operations such as creating a new record. Using the correct action type creates a clearer user experience because record-specific operations appear in the context of the selected business entity while broader actions remain available from the record list.

Question 206. A record list must allow users to filter by a start date and end date. Which user-filter type should be configured?

1. Date range user filter
2. Security user filter
3. Process user filter
4. Relationship-only filter

Correct Answer: 1. Date range user filter

Explanation:

A date range user filter is designed for record-list filtering based on dates. Users can specify both a beginning and ending date, or use an open-ended range with only one boundary. For example, a Customer Since filter might show customers added after a particular date, while a Submitted Date filter could restrict support cases to a selected period. Developers can also configure default From and To dates when appropriate. This is preferable to creating unrelated process or security logic because date range filters are purpose-built for allowing users to interactively refine record-list results using temporal criteria.

Question 207. Appian automatically generates a user filter after a developer creates which type of record relationship?

1. One-to-one only
2. Many-to-one
3. Many-to-many directly
4. No relationships can generate filters

Correct Answer: 2. Many-to-one

Explanation:

When a new many-to-one relationship is defined, Appian can automatically generate a list user filter based on that relationship. The filter uses the related field that participates in the relationship and can populate filter options from values on the related record type. This feature accelerates configuration because many business applications naturally need filters based on related reference information such as department, category, status type, or region. Developers can retain, modify, or replace the generated filter depending on the application’s requirements. Understanding automatically generated capabilities can reduce unnecessary custom configuration and keep record-list design consistent with the underlying data model.

Question 208. What is a group type used for in Appian?

1. To determine which process model version executes
2. To define record-level security rules
3. To classify groups into categories and optionally define additional information required for groups of that type
4. To replace parent-child group relationships

Correct Answer: 3. To classify groups into categories and optionally define additional information required for groups of that type

Explanation:

Group types provide a way to classify Appian groups into meaningful categories. An organization might define group types for departments, project teams, business units, or another logical organizational structure. A group type can also define additional attributes that should be collected when new groups of that type are created. This makes group administration more structured than treating every group as an unrelated custom group. Group types do not replace group membership or parent-child structures; rather, they provide metadata and classification that can help applications manage groups consistently across larger implementations.

Question 209. Which statement correctly describes Appian group membership?

1. Users can become members directly, indirectly through subgroups, or through membership rules
2. Groups may contain only individual users
3. A group can never be a member of another group
4. Membership rules are supported only for system administrators

Correct Answer: 1. Users can become members directly, indirectly through subgroups, or through membership rules

Explanation:

Appian supports several ways for a user to become a group member. A user may be added directly, become an indirect member because they belong to a subgroup that is itself contained within another group, or qualify through a configured membership rule. This flexibility lets organizations model security and organizational structures without manually managing every user-to-group assignment. Groups themselves can also participate in hierarchical structures. Senior developers should understand the distinction between direct and indirect membership when troubleshooting permissions because a user may receive access through a nested group even when they do not appear as a direct member.

Question 210. What restriction applies to the parent relationship of an Appian group?

1. A group can have unlimited direct parents
2. Parent groups are permitted only for system groups
3. A parent must always have an Automatic membership policy
4. A group can have at most one parent, and recursive parent relationships are not allowed

Correct Answer: 4. A group can have at most one parent, and recursive parent relationships are not allowed

Explanation:

Appian allows a group to have at most one designated parent. The hierarchy also cannot be recursive. For example, if Group A is the parent of Group B and Group B is the parent of Group C, Group C cannot then become the parent of Group A. This prevents circular group structures that would make membership and security evaluation ambiguous. A parent can still have multiple child groups, making hierarchical organizational models possible. Developers designing group structures should establish clear parent-child relationships and avoid using group nesting without understanding how indirect membership affects application permissions and group-based logic.

Question 211. Which membership policy allows a user to join a group using the Join Group smart service?

1. Restricted only
2. Automatic
3. Exclusive only
4. Administrator-only

Correct Answer: 2. Automatic

Explanation:

The Join Group smart service allows a user to add themselves to a group when that group uses the Automatic membership policy. It cannot be used to directly join groups configured with more restrictive membership policies. This distinction lets organizations control whether membership can be self-service or requires administrative involvement. A developer using dynamic group membership in an application should verify both the smart-service configuration and the target group’s membership policy. If those policies do not align, the operation will not behave as expected even if the user otherwise has access to the surrounding application functionality.

Question 212. A new group should permit administrators of that group to create child groups beneath it. Which setting is relevant?

1. Record inheritance
2. High privacy only
3. Delegated creation
4. Activity chaining

Correct Answer: 3. Delegated creation

Explanation:

Delegated creation controls whether administrators of a group can create additional groups with that group as the parent. This is useful in organizations where central administrators want to delegate management of part of the group hierarchy to departmental or application administrators without granting broader administrative rights. When creating a group programmatically, the delegatedCreation setting can be configured along with properties such as group type, parent, membership policy, privacy, and security type. Delegated group creation should be governed carefully because group hierarchy and membership can influence permissions throughout applications that use group-based security.

Question 213. In Appian interface design mode, what is the Live View primarily used for?

1. To preview and directly work with the interface being designed
2. To manage database indexes
3. To configure group membership policies
4. To inspect deployment packages

Correct Answer: 1. To preview and interact with the interface during design

Explanation:

Design mode provides a visual environment for creating Appian interfaces. Its main areas include the palette, Live View, and configuration panel. The palette provides components, patterns, and Design Library items, while the Live View shows the interface as it is being built. Developers can work visually with components and immediately see the impact of configuration changes. This shortens the feedback cycle for layout and usability decisions compared with editing expressions without a visual preview. Expression mode remains available for developers who need more precise or advanced expression control, and teams can use both approaches as appropriate.

Question 214. What is the difference between an Appian design guidance recommendation and a warning?

1. Recommendations prevent an object from being saved, while warnings never matter
2. Both are automatically removed after deployment
3. Recommendations apply only to sites, while warnings apply only to interfaces
4. Recommendations may be dismissed when not relevant, whereas warnings should be addressed and cannot be dismissed**

Correct Answer: 4. Recommendations may be dismissed when not relevant, whereas warnings should be addressed and cannot be dismissed

Explanation:

Appian design guidance identifies patterns that may affect maintainability, performance, reliability, or adherence to platform best practices. Recommendations provide guidance that developers can review and, when justified, dismiss if the recommendation does not apply to the particular design. Warnings are more serious and cannot be dismissed; Appian advises developers to address them because they can cause complications when the object’s logic executes. Design guidance does not replace testing or code review, but it provides useful automated feedback during development. Senior developers should treat unresolved warnings as actionable technical issues rather than ignoring them simply because an object can still be saved.

Question 215. Why does Appian recommend passing rule inputs by keyword when one interface calls another interface or expression rule?

1. It automatically grants access to the called rule
2. It makes the call clearer and less dependent on the positional order of rule inputs
3. It forces every rule input to become Text
4. It prevents the called rule from being versioned

Correct Answer: 2. It makes the call clearer and less dependent on the positional order of rule inputs

Explanation:

Passing rule inputs by keyword makes an expression easier to understand because each supplied value is explicitly associated with its intended input. It also reduces dependence on the physical order in which inputs are defined. This is valuable as reusable interfaces and expression rules evolve over time because positional calls can become harder to maintain or more error-prone when inputs change. Appian recommends keyword syntax as a maintainability best practice when rules are called from interfaces. Clear input mappings are especially important in enterprise applications where reusable rules may have many callers and several developers may maintain them over the application’s lifecycle.

Question 216. What happens when an Appian interface object is saved after being modified?

1. The previous version is immediately deleted
2. All dependent process instances restart
3. A new interface version is created, and dependent objects normally use the latest version
4. The interface automatically becomes read-only

Correct Answer: 3. A new interface version is created, and dependent objects normally use the latest version

Explanation:

Each time an interface is modified and saved, Appian creates a new version of that interface object. Objects that reference the interface normally use the newest saved version. Previous versions remain available in version history and can be reviewed or reverted when necessary. This behavior makes interface changes immediately relevant to dependent objects, which is particularly important for long-running process applications. Appian recommends planning carefully when an interface’s behavior needs to remain aligned with an older process version because simply modifying the shared interface could change what existing process instances display when users return to later tasks.

Question 217. What is a potential concern when significantly modifying an interface that is used by long-running process instances?

1. Older process instances may begin using the latest interface behavior even though they were created under an older process design
2. Every running process is automatically deleted
3. Appian prevents all interface changes while processes are active
4. The interface permanently loses its rule inputs

Correct Answer: 1. Older process instances may begin using the latest interface behavior even though they were created under an older process design

Explanation:

Interfaces are independently versioned objects, and callers normally use the latest version. This means a long-running process created months earlier can potentially display a newer interface definition when it later reaches a task that references the shared interface. If the new interface expects different data or implements changed business behavior, this can create compatibility problems. Appian recommends considering strategies such as creating a new interface object or adding controlled conditional behavior when old and new process versions must remain aligned with different interface implementations. Senior developers should therefore consider active process instances before making breaking changes to shared interfaces.

Question 218. What can an escalation configured on an attended Appian process node do after a specified delay?

1. Only archive the entire process
2. Trigger configured actions intended to address a delayed task or node
3. Change the application’s database schema
4. Automatically deploy a newer process version

Correct Answer: 2. Trigger configured actions intended to address a delayed task or node

Explanation:

Escalations are designed to handle delayed attended activities. A developer can configure an escalation timer and specify an action that should occur after the delay. Multiple escalation levels can also be defined to implement progressive handling of overdue work. This is useful for service-level requirements in which an unattended approval, review, or other assigned task should trigger follow-up behavior when it has not been completed on time. Escalations differ from timer exception flows: an exception can interrupt the activity and route the workflow elsewhere, while escalation functionality is specifically designed to take configured remedial actions for delayed attended nodes.

Question 219. A task has two configured escalation levels. When does the timer for the second escalation level begin?

1. Only after the first escalation level has triggered
2. At exactly the same moment as the first escalation timer
3. Only after the process completes
4. When the task is initially designed

Correct Answer: 1. Only after the first escalation level has triggered

Explanation:

Appian supports multiple levels of escalation on attended nodes. The timer for a later escalation level does not begin simultaneously with the timer for the first level. Instead, the second-level timer begins after the previous escalation level has triggered. This enables progressive escalation strategies—for example, notifying one supervisor after an initial delay and triggering a stronger response if the task remains unresolved for an additional period. Developers should account for this sequential timing when interpreting service-level requirements because a second-level delay represents time measured after the first escalation, rather than necessarily from the moment the original task was assigned.

Question 220. A senior developer is designing a large case-management application with many records, reusable interfaces, business groups, and time-sensitive user tasks. Which approach BEST supports maintainability and usability?

1. Hard-code all filtering and access logic independently in every interface
2. Avoid group structures and assign all access directly to individual users
3. Use record-list filters and actions appropriately, reusable interfaces with clear rule-input mappings, structured group management, and configured escalations for overdue work
4. Place every business function into one very large interface with no reusable components

Correct Answer: 3. Use record-list filters and actions appropriately, reusable interfaces with clear rule-input mappings, structured group management, and configured escalations for overdue work

Explanation:

A maintainable Appian solution uses platform capabilities according to their intended responsibilities. Record user filters help users locate relevant business data without duplicating filtering logic across screens, while record actions expose business operations in the correct context. Reusable interfaces reduce duplication, and explicit keyword-based rule-input mappings make those reusable components easier to maintain. Groups provide scalable identity and access structures compared with repeated user-specific configuration. Finally, escalations provide a controlled way to respond to delayed attended tasks. Combining these patterns produces an application that is easier to govern, troubleshoot, extend, and use than a design based on duplicated logic and manually managed exceptions.