Summer Certification Limited Time 70% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code = getmirror

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 2 out of 2 pages

Viewing questions 11-20 out of questions

Questions # 11:

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?

Options:

Download the CDT asXSD, make the appropriate changes, and re-upload the XSD. Verify and publish the data store.

Rename the field in the record type in Appian to automatically update the CDT field.

Rename the field in the CDT in Appian. Verify and publish the data store.

Answer

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.References:Appian Documentation - Data Types and Data Stores

Questions # 12:

Where can an Appian Developer connect with and share their expertise with other Appian Developers?

Options:

Appian Learning Paths via Appian Academy

Appian Knowledge Base

Appian Community discussions

Answer

Explanation

Appian Community discussions provide a platform for Appian Developers to connect with, share expertise, and learn from each other. The community is a vibrant space where developers can ask questions, share solutions, and discuss best practices related to Appian development. While Appian Learning Paths via Appian Academy and Appian Knowledge Base are valuable resources for learning and troubleshooting, the Community discussions specifically facilitate peer-to-peer interaction and knowledge sharing among developers.References:Appian Community Website

Questions # 13:

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.)

Options:

Knowledge Center

Decision Object

Folder

Feed

Answer

A, C

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.References:Appian Documentation - Knowledge Centers and Folders

Questions # 14:

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?

Options:

1. Write to Multiple Data Store Entities smart service (Writing to the ACME_invoiceItem table and ACME_invoice table).

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).

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).

Answer

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.References

Appian Documentation: Relational Databases

Questions # 15:

You need to pass data into a process from other parts of your Appian application.

Which configuration is required in your process model?

Options:

Toggle the Parameter field to 'True" on the configuration of a process variable.

Create process variables on the Data Management tab of Process Model Properties.

Add an interface as a Process Start Form.

Answer

Explanation

To pass data into a process from other parts of an Appian application, you need to configure process variables. This is done on the Data Management tab within the Process Model Properties. Here, you can define process variables that can receive data from external sources, such as interfaces, other processes, or direct user input, when the process is started. These variables serve as placeholders for the data that will be used throughout the execution of the process.References:Appian Documentation - Process Model Properties

Questions # 16:

You receive the following error message after creating a dropdown field:

Question # 16

What could be the problem?

Options:

The choiceLabels and choiceValues datatypes do not match.

The choiceValues has too few values.

The choiceLabels have too few labels.

Answer

Explanation

The error message indicates that the choiceValues array is not the same length as the choiceLabels array. In this scenario, there are more labels than values, which means the choiceValues array needs additional values to match the number of labels.References

Appian Documentation: Dropdown Field

Questions # 17:

How can you prevent users from accessing Tempo?

Options:

Remove the users from the Tempo Users system group.

Change the default User Start Page.

Ensure the user is in the Application Users group, which by default does not have access to Tempo.

Answer

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.References:Appian Documentation - System Groups and User Access

Viewing page 2 out of 2 pages

Viewing questions 11-20 out of questions