Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Appian Exam Appian Certified Senior Developer Topic 1 Question 51 Discussion

Actual exam question for Appian's Appian Certified Senior Developer exam
Question #: 51
Topic #: 1
[All Appian Certified Senior Developer Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: C, D

by Peter at Mar 20, 2025, 08:27 AM

Limited Time Offer

25%

Off

Get Premium Appian Certified Senior Developer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Delpha
2 months ago
Option B with a SSIS package? Sounds like a good way to make your job security more... permanent.
upvoted 0 times
Jolanda
21 days ago
D) Create a stored procedure to query the data from both the [appian].[document] and [appian].[caseData] tables.
upvoted 0 times
...
Pilar
1 months ago
C) Create a view between both the [appian].[document] and [appian].[caseData] tables to feed the record.
upvoted 0 times
...
Anthony
1 months 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].
upvoted 0 times
...
...
Mica
2 months ago
Option A with a trigger? That's like using a sledgehammer to crack a nut. Talk about going overboard!
upvoted 0 times
An
26 days ago
C) Create a view between both the [appian].[document] and [appian].[caseData] tables to feed the record.
upvoted 0 times
...
Tamera
29 days ago
B) Create a SSIS package to run at a regular interval.
upvoted 0 times
...
Elliot
2 months 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].
upvoted 0 times
...
...
Kimberely
3 months 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.
upvoted 0 times
Cecil
30 days ago
Creating a view might be simpler, but a stored procedure would offer more flexibility in the long run.
upvoted 0 times
...
Tyra
1 months ago
I agree, a stored procedure would help keep the logic centralized and make it easier to manage.
upvoted 0 times
...
Theola
2 months ago
Creating a view might work too, but a stored procedure seems like a more efficient choice.
upvoted 0 times
...
Juan
2 months ago
I agree, a stored procedure would help keep the logic centralized and easier to manage.
upvoted 0 times
...
Remona
2 months ago
I think a stored procedure would be the best option for this scenario.
upvoted 0 times
...
Franklyn
2 months ago
I think a stored procedure would be the best option for this scenario.
upvoted 0 times
...
...
Anglea
3 months 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.
upvoted 0 times
Lashawn
2 months ago
I agree, a view would simplify the process without the need for triggers or stored procedures.
upvoted 0 times
...
Jerry
2 months ago
I think creating a view between both tables would be the most efficient way.
upvoted 0 times
...
Malcolm
2 months ago
Using a SSIS package to run at regular intervals might be a bit more complex than necessary.
upvoted 0 times
...
Lizbeth
2 months ago
Creating a stored procedure to query data from both tables could also be a good option.
upvoted 0 times
...
Titus
2 months ago
Agreed, a view would simplify the process and avoid potential performance issues.
upvoted 0 times
...
Hui
3 months ago
I think creating a view between both tables would be the most efficient way.
upvoted 0 times
...
...
Tricia
3 months 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.
upvoted 0 times
...
Arletta
3 months ago
But wouldn't creating a trigger to copy data across be the best option?
upvoted 0 times
...
Alesia
3 months ago
I disagree, I believe creating a stored procedure would be more efficient.
upvoted 0 times
...
Odette
3 months 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.
upvoted 0 times
Verdell
2 months ago
I would go with option C, creating a view between the tables.
upvoted 0 times
...
Thora
2 months ago
Creating a trigger on the document table seems like a good idea too.
upvoted 0 times
...
Ryan
2 months ago
I agree, a stored procedure would encapsulate the logic nicely.
upvoted 0 times
...
Pamella
3 months ago
I think option D is the best choice. It provides a clean interface to fetch the data.
upvoted 0 times
...
...
Casey
3 months 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.
upvoted 0 times
...
Arletta
4 months ago
I think the most efficient way is to create a view between both tables.
upvoted 0 times
...

Save Cancel