Week End Sale Special Limited Time 70% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code = drift75

Home
Appian
Associate Developer
ACD101
Appian Associate Developer Questions and Answers

Pass the Appian Associate Developer ACD101 Questions and answers with ExamsMirror

Practice at least 50% of the questions to maximize your chances of passing.

Exam ACD101 Premium Access

View all detail and faqs for the ACD101 exam

Go to Exam

845 Students Passed

96% Average Score

98% Same Questions

Viewing page 3 out of 4 pages

Viewing questions 21-30 out of questions

Questions # 21:

Which code snippet calls the interface APP_RecordDashboard while following best practices for passing in values for " recordId " and " firstName " ?

Question # 21

Options:

Option A

Option B

Option C

Answer

Explanation

The best practice in Appian for passing values into an interface is to use named parameters, which is demonstrated by Option B. Named parameters make the code more readable and maintainable by clearly specifying which parameter each value is being passed to. In this case, the recordId and firstName parameters are clearly being assigned the values 1 and " Kyle " respectively.

References

Appian Documentation: Passing Parameters to Interfaces

Questions # 22:

You need to start a process using an email trigger.

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

Options:

Go to File > Properties > Alerts. Configure the Custom Alert settings.

Go to File > Properties Set the proper Process Display Name

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

Answer

Questions # 23:

A user wants to view a bulleted list of information on an interface.

Which component should you use?

Options:

paragraphField

textField

richTextDisplayField

Answer

Questions # 24:

Which Appian feature helps you access enterprise data quickly, define easily leveraged relationships, and establish custom fields based on available information?

Options:

Task Management

Process Analytics

Record types with data sync enabled

Answer

Questions # 25:

Which set of out-of-the-box features is only available when data sync is enabled on a record type?

Options:

Generate record actions

Define record type object security

Add custom record fields

Define record type relationships

Add custom record fields

Configure record-level security

Define record type relationships

Add hidden record fields

Configure record-level security

Answer

Explanation

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.

[References: Appian Documentation - Record Type Features and Data Sync]

Questions # 26:

You are configuring a local variable on an interface to store the date and time that the username field was last modified. The local variables are currently configured as follows:

Question # 26

Which a!refreshVariable configuration should be added so that local!usernameLastModified stores the correct timestamp?

Options:

refreshInterval: 0

refreshOnVarChange: local!username

refreshAlways: true

Answer

Explanation

The a!refreshVariable function should be configured to refresh when the local!username variable changes. This is achieved by setting the refreshOnVarChange parameter to local!username, which will update the local!usernameLastModified variable with the current timestamp whenever local!username is modified.

References

Appian Documentation: a!refreshVariable Function

Questions # 27:

You configured a Custom Data Type (CDT), ACME_video. You need to set up a node in your process model to write a new video as a row in the CDT ' s corresponding database table.

Which set of inputs must you configure on your Write to Data Store smart service node?

Options:

The data store and an input corresponding to each field of the ACME_video CDT.

The data store entity and an input of type ACME_video.

The data store and an input of type ACME_video.

Answer

Explanation

When configuring a Write to Data Store Entity smart service node to write a new row to a CDT ' s corresponding database table, you must specify the data store entity where the CDT is stored. Additionally, you need to provide an input of the type that matches the CDT, in this case, an input of type ACME_video, which will contain the data to be written to the database.

[References: Appian Documentation - Write to Data Store Entity Smart Service]

Questions # 28:

Which variable type is used to store data used within a single node of a process model?

Options:

Rule Inputs

Process Variables

Activity Class Parameters

Answer

Questions # 29:

What is the out-of-the-box behavior that indicates a text input field is required?

Options:

The size of the label font increases to show significance.

An asterisk (*) appears at the end of the label to notify the user that the field must have a rule.

The label font of the field goes from normal text to bold in order to draw attention.

Answer

Questions # 30:

Review the following expression rule:

union(ri!fruit, ri!vegetables)

The rule inputs are configured as text arrays.

What is the expected output?

Options:

All items in ri!fruit followed by items in ri!vegetables, including duplicate values.

Only items that are in both ri!fruit and ri!vegetables.

All items in ri!fruit and ri!vegetables combined, with duplicates removed.

Answer

Explanation

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.

[References: Appian Documentation - Expression Functions]

Viewing page 3 out of 4 pages

Viewing questions 21-30 out of questions