MENU
An organization has decided to integrate with a third-party to scan incoming documents and capture the details in a table called [appian].[document]. Each document will form a new case in Appian to be displayed on a Record List.
The record needs to show data from both [appian].[document] and [appian].[caseData], which holds additional case information.
What is the most efficient way to achieve this?
Suggested Answer: C, D
Get Premium ACD200 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
49 comments · newest first
EL
Elli
9 months ago
Wait, why not just use a view instead of copying data?
ES
Estrella
9 months ago
A sounds like a lot of unnecessary data duplication.
DA
Daryl
9 months ago
I have a vague memory of SSIS packages being used for data integration, but I’m not confident if option B is the right choice here.
LA
Lashawnda
10 months ago
I practiced a similar question where we had to decide between triggers and stored procedures. I think D could work, but it might be less efficient than a view.
JO
Jolene
10 months ago
I'm not entirely sure, but I feel like creating a trigger could lead to data inconsistencies. Option A seems risky.
JU
Junita
10 months ago
Option C seems the most efficient, views are great for this!
IL
Iluminada
10 months ago
SSIS package? That feels like overkill for this task.
SH
Shannon
10 months ago
I disagree, D would give more control over the query.
LE
Leonor
11 months ago
I remember we discussed using views in class, and I think option C might be the best way to combine data without duplicating it.
TA
Tamar
11 months ago
This is a tricky one. I'm not sure if any of the options are really the "most efficient" way to do this. I might try to get some more information about the specific requirements and the expected volume of data before deciding. If it's a relatively small amount of data, maybe a stored procedure (option D) would be the simplest approach. But if the data is more complex or changes frequently, a view (option C) could be better. I'll need to think this through a bit more.
RO
Ronnie
11 months ago
Okay, let me think this through. I think the key here is to find the most efficient way to get the data from both tables into the record list. Option A with a trigger seems like it could work, but that might get messy if the data in the [appian].[document] table changes a lot. Option B with SSIS could work, but that feels a bit overkill for this use case. I'm leaning towards option C with the view - it seems like the cleanest and most maintainable solution.
RO
Ronald
11 months ago
Hmm, I'm a bit unsure about this one. I'm not super familiar with Appian, so I'm not sure if a view is the best approach. Maybe option D with a stored procedure would be better? That way I can encapsulate the logic in one place and make it easier to maintain.
OL
Olive
12 months ago
This seems like a pretty straightforward question. I'd probably go with option C and create a view between the two tables. That way, the data is always up-to-date and I don't have to worry about maintaining any triggers or scheduled jobs.
CH
Charisse
12 months ago
Option A with a trigger sounds like it could work, but I'm not sure if that's the most efficient approach. Triggers can sometimes cause performance issues, especially if the volume of documents is high. I'd probably lean more towards a view or a stored procedure.
MA
Maile
12 months ago
I think option D with a stored procedure could work well here. That way, we can encapsulate the logic for querying both tables and return a single result set. It might be a bit more work upfront, but it could make the record list more maintainable in the long run.
DE
Deandrea
1 year ago
Hmm, I'm a bit unsure about this one. The question mentions integrating with a third-party system, so I'm not sure if a view would be the best approach. Maybe option B with a SSIS package would be more robust and flexible?
SE
Selma
1 year ago
This looks like a straightforward data integration problem. I'd probably start by considering option C - creating a view between the two tables. That seems like the most efficient approach to get the data from both sources into a single record.
DE
Delpha
1 year ago
Option B with a SSIS package? Sounds like a good way to make your job security more... permanent.
JO
Jolanda
1 year ago
D) Create a stored procedure to query the data from both the [appian].[document] and [appian].[caseData] tables.
PI
Pilar
1 year ago
C) Create a view between both the [appian].[document] and [appian].[caseData] tables to feed the record.
AN
Anthony
1 year ago
A) Create a trigger on the [appian].[document] table to copy all the data across to the [appian].[caseData] table and point the record at [appian].[caseData].
MI
Mica
1 year ago
Option A with a trigger? That's like using a sledgehammer to crack a nut. Talk about going overboard!
AN
An
1 year ago
C) Create a view between both the [appian].[document] and [appian].[caseData] tables to feed the record.
TA
Tamera
1 year ago
B) Create a SSIS package to run at a regular interval.
EL
Elliot
1 year ago
A) Create a trigger on the [appian].[document] table to copy all the data across to the [appian].[caseData] table and point the record at [appian].[caseData].
KI
Kimberely
1 year ago
I'm torn between options C and D. A view or a stored procedure both sound reasonable, but I'd probably lean towards the stored procedure to keep the logic more encapsulated.
CE
Cecil
1 year ago
Creating a view might be simpler, but a stored procedure would offer more flexibility in the long run.
TY
Tyra
1 year ago
I agree, a stored procedure would help keep the logic centralized and make it easier to manage.
TH
Theola
1 year ago
Creating a view might work too, but a stored procedure seems like a more efficient choice.
JU
Juan
1 year ago
I agree, a stored procedure would help keep the logic centralized and easier to manage.
RE
Remona
1 year ago
I think a stored procedure would be the best option for this scenario.
FR
Franklyn
1 year ago
I think a stored procedure would be the best option for this scenario.
AN
Anglea
1 year ago
Option A with a trigger is a bit too much for this use case. It might work, but it feels like overkill and could lead to potential performance issues down the line.
LA
Lashawn
1 year ago
I agree, a view would simplify the process without the need for triggers or stored procedures.
JE
Jerry
1 year ago
I think creating a view between both tables would be the most efficient way.
MA
Malcolm
1 year ago
Using a SSIS package to run at regular intervals might be a bit more complex than necessary.
LI
Lizbeth
1 year ago
Creating a stored procedure to query data from both tables could also be a good option.
TI
Titus
1 year ago
Agreed, a view would simplify the process and avoid potential performance issues.
HU
Hui
1 year ago
I think creating a view between both tables would be the most efficient way.
TR
Tricia
1 year ago
Option B with a SSIS package running at regular intervals seems like a good approach. It allows for more flexibility and control over the data synchronization process.
AR
Arletta
1 year ago
But wouldn't creating a trigger to copy data across be the best option?
AL
Alesia
1 year ago
I disagree, I believe creating a stored procedure would be more efficient.
OD
Odette
2 years ago
I would go with option D. A stored procedure can encapsulate the logic and provide a clean interface to fetch the data, instead of relying on a view.
VE
Verdell
1 year ago
I would go with option C, creating a view between the tables.
TH
Thora
1 year ago
Creating a trigger on the document table seems like a good idea too.
RY
Ryan
1 year ago
I agree, a stored procedure would encapsulate the logic nicely.
PA
Pamella
1 year ago
I think option D is the best choice. It provides a clean interface to fetch the data.
CA
Casey
2 years ago
Option C seems the most efficient to me. A view will combine the data from both tables and provide a single source of truth for the record display.
AR
Arletta
2 years ago
I think the most efficient way is to create a view between both tables.