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 ACD200 Exam - Topic 10 Question 49 Discussion

Actual exam question for Appian's ACD200 exam
Question #: 49
Topic #: 10
[All ACD200 Questions]

A lead designer receives this requirement:

Every time a record is modified, the data changed must be stored for audit.

Which design is the most efficient and has the least impact on the Appian application? (Choose the best answer.)

Show Suggested Answer Hide Answer
Suggested Answer: C, D

by Lizbeth at Feb 07, 2025, 09:12 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Ronald
5 months ago
Definitely leaning towards B, triggers are reliable for this kind of task.
upvoted 0 times
...
Vashti
5 months ago
Wait, can we really trust a web API for audit trails?
upvoted 0 times
...
Queen
6 months ago
A custom plugin? Sounds like a lot of extra work!
upvoted 0 times
...
Shaquana
6 months ago
I disagree, I think C would be more efficient for tracking changes.
upvoted 0 times
...
Salley
6 months ago
Option B seems like the most straightforward approach.
upvoted 0 times
...
Jennie
6 months ago
I recall a similar question where we debated between using APIs and database triggers. I think option D might complicate things too much.
upvoted 0 times
...
Valentin
7 months ago
I think option C could work well since it uses Appian's built-in processes, but I wonder if it would be as efficient as a database trigger.
upvoted 0 times
...
Major
7 months ago
I'm not entirely sure, but I feel like creating a custom plugin could add unnecessary complexity. Option A seems risky.
upvoted 0 times
...
Kallie
7 months ago
I remember we discussed the impact of triggers on performance in one of our practice sessions. I think option B might be the most efficient.
upvoted 0 times
...
Georgeanna
7 months ago
I'm a little confused by this question. All the options seem like they could work, but I'm not sure which one would be the most efficient. I might need to do some more research on the pros and cons of each approach before I can decide. Any tips on how to evaluate these options?
upvoted 0 times
...
Ernestine
7 months ago
Ah, this is a good one. I'd probably go with the Appian process option. That way, I can keep the audit trail management within the application itself, which could make it easier to maintain and integrate with other Appian features. Plus, it doesn't require any external systems or custom code.
upvoted 0 times
...
Brittani
7 months ago
Hmm, I'm not sure about this one. I'm trying to think through the pros and cons of each option. Creating a custom plugin might give me more control, but it could also be more complex to implement. And using a web API call seems like it might add unnecessary overhead. I'll have to weigh the tradeoffs carefully.
upvoted 0 times
...
Magda
7 months ago
This looks like a pretty straightforward question. I think the most efficient and least impactful solution would be to create a trigger on the database table to capture the audit trail. That way, the audit logging happens automatically without any additional code or processes in the Appian application.
upvoted 0 times
...
Merrilee
1 year ago
Option D? Really? Involving an external system just to store audit trails? That's like using a bazooka to kill a fly. B is the way to go, folks.
upvoted 0 times
...
Aretha
1 year ago
Option A sounds like a lot of work. Who wants to write a custom plugin when you can just let the database handle it? B is the winner, no doubt.
upvoted 0 times
Shasta
11 months ago
C: I think option C could also work well, creating an Appian process to capture the change history.
upvoted 0 times
...
Ira
12 months ago
B: Yeah, creating a trigger on the database table seems like the easiest solution.
upvoted 0 times
...
Josefa
12 months ago
A: I agree, option B is definitely the most efficient choice.
upvoted 0 times
...
...
Rusty
1 year ago
Option C seems like overkill. Why add an entire process just to capture audit trails? Option B is the clear winner here.
upvoted 0 times
Willodean
11 months ago
I think option B is more direct and less complex.
upvoted 0 times
...
Clement
12 months ago
But wouldn't creating a custom plugin be simpler?
upvoted 0 times
...
Tamar
1 year ago
I agree, option B is the most efficient choice.
upvoted 0 times
...
...
Nu
1 year ago
I agree, Option B is the best choice. It's a standard database-level solution that will have minimal impact on the Appian application.
upvoted 0 times
Emogene
11 months ago
Creating a custom plugin might be more complex than necessary. Option B seems like the best choice.
upvoted 0 times
...
Meghan
11 months ago
Agreed, using a database trigger is a common practice for capturing audit trails.
upvoted 0 times
...
Yvette
11 months ago
I think creating a trigger on the database table is the most straightforward approach.
upvoted 0 times
...
Marg
11 months ago
Option B is definitely the way to go. It's a simple and efficient solution.
upvoted 0 times
...
...
Magda
1 year ago
That's a good point, but I still think option B is better for minimizing impact on the Appian application.
upvoted 0 times
...
Katie
1 year ago
I disagree, I believe option C is more efficient as it uses an Appian process to capture the change history.
upvoted 0 times
...
Billy
1 year ago
Option B is the way to go. It's a simple and efficient solution that doesn't require additional code or system integrations.
upvoted 0 times
Ashley
1 year ago
I agree, using a trigger on the database table is the most efficient way to capture the audit trail.
upvoted 0 times
...
Melda
1 year ago
Option B is definitely the best choice. It keeps everything within the database and is easy to implement.
upvoted 0 times
...
...
Magda
1 year ago
I think option B is the best choice because it directly captures the audit trail in the database.
upvoted 0 times
...

Save Cancel