The Appian ACD101 Questions & Practice Test are Available On-Demand
Valid ACD101 Exam Dumps Ensure you a HIGH SCORE
NEW QUESTION # 29
Which two scenarios are ideal for using Appian Portals? (Choose two.)
- A. A user needs to submit support requests when they are using their mobile device in areas with bad network coverage.
- B. An employee who does not have an account wants to register for their company's vehicle fleet a management system.
- C. A retail customer wants to conduct a public survey for their recently launched product.
- D. A manager wants to obtain a view of their team's performance.
Answer: 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
NEW QUESTION # 30
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?
- A. Set all process variables as parameters.
- B. Enable activity chaining.
- C. Run the script task as "synchronous."
Answer: B
NEW QUESTION # 31
How can you prevent users from accessing Tempo?
- A. Change the default User Start Page.
- B. Remove the users from the Tempo Users system group.
- C. Ensure the user is in the Application Users group, which by default does not have access to Tempo.
Answer: B
Explanation:
To prevent users from accessing Tempo, you should remove them from the Tempo Users system group. This group controls access to the Tempo interface in Appian. By removing users from this group, they will no longer have the necessary permissions to access Tempo features and content.
Reference: Appian Documentation - System Groups and User Access
NEW QUESTION # 32
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.
* An alert Is sent to the process initiator.
* 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.
* No alerts are sent.
* These nodes are included in the num_problem_tasks process metric in process reports.
Answer: 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
NEW QUESTION # 33
How can you add test data into your rule inputs while editing an interface object?
- A. Select the Performance tab and set test values.
- B. Select the Gear icon, select Properties, and set test values.
- C. Select the Test button and set test values.
Answer: C
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
NEW QUESTION # 34
A user needs to navigate from a record summary to an external URL.
Which interface component can be used to support this goal?
- A. Record Link
- B. Button
- C. Card Layout with a link
Answer: B
Explanation:
In Appian, to navigate from a record summary to an external URL, you can use a Button component configured with a 'Link' action. This approach allows you to define a URL that the button will navigate to when clicked. The Button component offers flexibility in terms of design and functionality, making it suitable for such navigation purposes within Appian interfaces. You can specify the URL directly in the Button's properties, allowing for dynamic link generation based on record data if needed.
Reference:
Appian Documentation: Designing Interfaces (This section provides comprehensive details on using various interface components, including buttons, to achieve specific user interaction goals within Appian.) Appian Documentation: Buttons (This page specifically focuses on the Button component, detailing its properties, usage, and how to configure it for different actions, including navigating to an external URL.)
NEW QUESTION # 35
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.
Answer:
Explanation:
Reference:
Appian Documentation: Data Modeling in Appian
NEW QUESTION # 36
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:
Which a!refreshVariable configuration should be added so that local!usernameLastModified stores the correct timestamp?
- A. refreshOnVarChange: local!username
- B. refreshAlways: true
- C. refreshInterval: 0
Answer: A
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.
Reference:
Appian Documentation: a!refreshVariable Function
NEW QUESTION # 37
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 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). - B. 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. 1. Write to Multiple Data Store Entities smart service (Writing to the ACME_invoiceItem table and ACME_invoice table).
Answer: B
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
NEW QUESTION # 38
You are creating a new customer onboarding application. Documents are required from customers for verification and onboarding purposes. You need to store these documents within Appian.
Which two areas in Appian should you configure? (Choose two.)
- A. Feed
- B. Folder
- C. Decision Object
- D. Knowledge Center
Answer: B,D
Explanation:
In Appian, to store documents such as those required for customer onboarding, you should configure a Knowledge Center and within that, Folders. The Knowledge Center in Appian serves as the top-level container for storing and organizing documents and folders. Folders within a Knowledge Center provide a way to categorize and manage access to documents, making them an essential part of document management in Appian applications. Decision Objects and Feeds are not related to document storage.
Reference: Appian Documentation - Knowledge Centers and Folders
NEW QUESTION # 39
What is an Appian best practice for calling interface rules on your interface?
- A. Use keyword syntax.
- B. Always use consistent ordering of rule parameters.
- C. Call the interface rule on a rule input.
Answer: B
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
NEW QUESTION # 40
Your customer wants to change the name of a field of an existing Custom Data Type (CDT) to match a renamed database field.
The CDT is backed by a database entity, whose data store has the Automatically Update Database Schema option disabled. The old column name was BIRTHDATE and the new column name is DATE_OF_BIRTH.
How should you proceed?
- A. Rename the field in the record type in Appian to automatically update the CDT field.
- B. Rename the field in the CDT in Appian. Verify and publish the data store.
- C. Download the CDT as XSD, make the appropriate changes, and re-upload the XSD. Verify and publish the data store.
Answer: B
Explanation:
When a field name in an existing Custom Data Type (CDT) needs to be changed to match a renamed database field, and the Automatically Update Database Schema option is disabled, the correct approach is to rename the field in the CDT within Appian. After renaming the field in the CDT to match the new database column name (from BIRTHDATE to DATE_OF_BIRTH in this case), you should verify the changes and publish the data store to reflect the updates. This approach ensures that the Appian data model remains in sync with the underlying database schema.
Reference: Appian Documentation - Data Types and Data Stores
NEW QUESTION # 41
Which code snippet calls the interface APP_RecordDashboard while following best practices for passing in values for "recordId" and "firstName"?
- A.
- B.
- C.
Answer: C
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.
Reference:
Appian Documentation: Passing Parameters to Interfaces
NEW QUESTION # 42
You are creating a new interface object to display a pie chart.
The data for the chart is stored in a local variable in the parent interface object which references your child interface.
In terms of performance, what is the most efficient method to access the data required for the pie chart?
- A. Query the data separately in the child interface to avoid passing it from the parent interface.
- B. Create a rule input on the child interface and pass the local variable data from the parent interface.
- C. Reference the local variable directly from the child Interface using a process report.
Answer: B
Explanation:
The most efficient method to access data for a pie chart in a child interface is to create a rule input on the child interface and pass the local variable data from the parent interface. This method avoids redundant data queries and takes advantage of Appian's pass-by-reference mechanism, which does not duplicate data in memory when passing it to the child interface.
Reference: Appian Documentation - Interface Design
NEW QUESTION # 43
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?
- A. The process report that drives the runtime database does not have security set properly.
- B. The button was not configured to submit the form.
- C. The user was not in the user group configured for the process model security.
Answer: B
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
NEW QUESTION # 44
Review the following expression rule:
ri!name is defined as "Maria".
ri!directory is defined as the following:
What is the expected output?
- A. 0
- B. Maria
- C. 1
Answer: C
Explanation:
Given that ri!name is defined as "Maria" and ri!directory contains two a!map() structures, one of which includes the name "Maria," the expression wherecontains(ri!name, index(ri!directory, "name")) will evaluate as follows: The index() function will return a list of values from ri!directory for the key "name," which will be {"Maria", "Steven"}. The wherecontains() function will then check where "Maria" is found within this list. Since "Maria" is the first element, the function will return a list of indices where "Maria" is found, in this case, {1}. Appian lists are 1-indexed, so the first position is represented by 1, not 0.
Reference: Appian Expression Language Documentation - Functions
NEW QUESTION # 45
Which step can be critical in passing information from a form back to a process model?
- A. Configure inputs on the Data tab of a User Input Task.
- B. Configure the Data Management tab.
- C. Configure the activity class parameters of a Write to Data Store Entity node, a
Answer: A
Explanation:
The critical step in passing information from a form back to a process model is to configure inputs on the Data tab of a User Input Task. When you create a User Input Task, it includes a form for users to interact with. The data entered into this form can be mapped to process variables via the Data tab configuration. This ensures that the information collected in the form is available to the process for further use.
Reference: Appian Documentation - User Input Tasks
NEW QUESTION # 46
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?
- 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
NEW QUESTION # 47
You need to create a record type with data sync enabled.
What are the supported data sources?
- A. Salesforce, Process Models, Database
- B. Web Services, Process Reports, Database
- C. Web Services, Salesforce, Database
Answer: A
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
NEW QUESTION # 48
When applying a default filter to a record type, what is a true statement for excluded data?
- A. The data does not show up in the record list, but end-users can clear the filter condition to view the data.
- B. The data does not show up in the record list, but can be accessed by end-users using a direct link to a record view.
- C. The data does not show up in the record list. End-users are unable to clear the filter condition to view the data.
Answer: A
Explanation:
When a default filter is applied to a record type in Appian, the data excluded by that filter does not appear in the default record list. However, end-users with appropriate permissions can modify or clear the filter conditions to view the excluded data. This behavior allows for a flexible and user-driven data exploration experience within Appian record lists.
Reference: Appian Documentation - Record Lists and Filters
NEW QUESTION # 49
Which option best describes the primary purpose of the interface design object?
- A. Provides a method for an Appian application to interact with an external application or service.
- B. Provides a method for an Appian application to interact with a database.
- C. Provides a method for end users to interact with an Appian application.
Answer: C
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
NEW QUESTION # 50
Review the following code snippet:
index({"a", "b", "c"}, 1, "x")
Which value is returned?
- A. a
- B. c
- C. b
- D. x
Answer: D
Explanation:
The index() function in Appian is used to replace an element at a specified index in a list. In the code snippet index({"a", "b", "c"}, 1, "x"), the function is called to replace the element at index 1 of the list {"a", "b", "c"} with the string "x". Since Appian lists are 1-indexed, this means that the first element "a" will be replaced by "x". However, since the function is used to modify a list and not to return a value, if this function is used as is without being part of a larger expression that outputs the list, it would not return any of the listed values.
Reference: Appian Expression Language Documentation - Functions
NEW QUESTION # 51
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?
- A. The data store entity and an input of type ACME_video.
- B. The data store and an input corresponding to each field of the ACME_video CDT.
- C. The data store and an input of type ACME_video.
Answer: A
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.
Reference: Appian Documentation - Write to Data Store Entity Smart Service
NEW QUESTION # 52
......
ACD101 Exam Practice Questions prepared by Appian Professionals: https://examtorrent.testkingpdf.com/ACD101-testking-pdf-torrent.html
