Appian Exam ACD101 Topic 1 Question 18 Discussion

Actual exam question for Appian's ACD101 exam

Question #: 18
Topic #: 1

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 Brandon at Aug 02, 2024, 06:16 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Carlene

5 months ago

Options A and B both seem viable, but I can't help but wonder if there's a hidden joke about the ACME company. You know, the one from the Coyote and Roadrunner cartoons?

upvoted 0 times

...

5 months ago

Hmm, I don't know. Option A looks like it might be the easiest way to handle this. Why do we need to separate the writes? Seems like unnecessary complexity.

upvoted 0 times

Joseph

4 months ago

Separating the writes can help with data integrity and organization.

upvoted 0 times

...

Pansy

4 months ago

Option A looks like the best choice. It simplifies the process.

upvoted 0 times

...

Huey

5 months ago

I'm with Alayna on this one. Option B is the way to go. Separating the writes and updating the foreign keys in between is the best approach.

upvoted 0 times

...

Alberto

5 months ago

I personally prefer option C because it first writes to the invoice table before the invoice item table.

upvoted 0 times

...

5 months ago

I think option A is the best choice because it writes to both data store entities in one step.

upvoted 0 times

...