Appian Exam ACD101 Topic 3 Question 35 Discussion

Actual exam question for Appian's ACD101 exam

Question #: 35
Topic #: 3

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?

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

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

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

Show Suggested Answer

Suggested Answer: C

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.

Appian Documentation: Relational Databases

by Royal at May 02, 2025, 02:49 PM

Limited Time Offer

25%

Off

Get Premium ACD101 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Margurite

2 days ago

This seems straightforward, I think I can handle it. The key is to understand the relationship between the two custom data types and how the primary keys are generated.

upvoted 0 times

...

Jose

4 months ago

Wait, we're using Custom Data Types? I thought this was a standard database problem. Now I'm even more confused!

upvoted 0 times

...

4 months ago

I like option B. Updating the foreign keys separately makes the process more robust and maintainable.

upvoted 0 times

Hillary

3 months ago

I think option B is the way to go for a smoother process.

upvoted 0 times

...

Christa

3 months ago

I agree, separating the foreign key updates can prevent errors in the long run.

upvoted 0 times

...

Karma

4 months ago

Option B sounds like a good choice. It helps keep things organized.

upvoted 0 times

...

5 months ago

I think option A is the best choice because it writes to both tables at once.

upvoted 0 times

...