New Year Sale 2026! 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 ACD201 Exam - Topic 4 Question 6 Discussion

Actual exam question for Appian's ACD201 exam
Question #: 6
Topic #: 4
[All ACD201 Questions]

You need to implement a field-level audit functionality on the application data, and then display a log of the changes made over time to the users.

What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: C

Creating audit tables and using triggers on each transaction table ensures that all field-level changes are automatically recorded at the database level, providing a reliable and consistent audit log for display to users.


by Dorsey at Oct 15, 2025, 12:45 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Willard
5 days ago
Option A could work too, but it feels more complex.
upvoted 0 times
...
Vincent
10 days ago
I agree, C is efficient. No need for manual intervention.
upvoted 0 times
...
Whitley
15 days ago
I think option C is the best. Triggers automate the logging process.
upvoted 0 times
...
Nelida
21 days ago
Wait, can triggers really handle all that data without slowing things down?
upvoted 0 times
...
Lashandra
26 days ago
I totally agree with C, triggers are the way to go!
upvoted 0 times
...
Lino
1 month ago
I prefer A, stored procedures give more control over the process.
upvoted 0 times
...
Erick
1 month ago
Triggers? Really? That's so 2000s. I'd go with option B and use a utility process. More modern and flexible.
upvoted 0 times
...
Joye
1 month ago
Option C is the clear winner here. Triggers are the standard approach for implementing field-level auditing.
upvoted 0 times
...
Leontine
2 months ago
Haha, option B sounds like something a software engineer would come up with to overcomplicate a simple problem. Triggers all the way!
upvoted 0 times
...
Magda
2 months ago
I agree, triggers are the way to go. Stored procedures and utility processes sound like overkill for a simple audit requirement.
upvoted 0 times
...
Reita
2 months ago
Option C is the way to go. Triggers are the easiest and most efficient way to capture data changes.
upvoted 0 times
...
Giovanna
2 months ago
Option C seems the most efficient for real-time tracking.
upvoted 0 times
...
Carmela
2 months ago
I'm leaning towards option A. Creating audit tables and stored procedures gives you more fine-grained control over what gets logged and how. It might take a bit more work upfront, but it could pay off if you have complex auditing requirements.
upvoted 0 times
...
Ciara
3 months ago
B sounds interesting, but isn't it a bit redundant?
upvoted 0 times
...
Tula
3 months ago
I think option C is the way to go. It's a common pattern for implementing field-level auditing, and it's relatively straightforward to set up. The triggers will handle the logging automatically, which should make it easier to maintain over time.
upvoted 0 times
...
Kris
3 months ago
Option B sounds interesting, creating utility processes to insert new versions of the data. That could give you more control and flexibility over the audit logging. But it might also be more complex to implement. I'd have to weigh the pros and cons.
upvoted 0 times
...
Tiera
4 months ago
Hmm, I'm not sure which approach I'd take here. The question doesn't give a lot of details about the application or the data model. I'd want to understand that better before deciding on the best solution.
upvoted 0 times
...
Ashlyn
4 months ago
This seems like a pretty straightforward question. I'd probably go with option C - creating audit tables and triggers on the transaction tables. That way, the changes get logged automatically without having to write a lot of custom code.
upvoted 0 times
Penney
2 months ago
I agree, option C sounds efficient. Triggers will handle it seamlessly.
upvoted 0 times
...
Trina
3 months ago
But what about performance? Triggers can slow down transactions.
upvoted 0 times
...
...
Wynell
4 months ago
I feel like using utility processes to insert new versions could lead to data duplication issues, but I’m not completely confident about that.
upvoted 0 times
...
Kristel
4 months ago
I practiced a similar question where we had to decide between triggers and stored procedures, and I think triggers might automatically handle changes better.
upvoted 0 times
...
Ulysses
4 months ago
I think creating an Audit table and using stored procedures might be more manageable, but I can't recall the specific advantages over triggers.
upvoted 0 times
...
Raina
5 months ago
I remember we discussed using triggers for auditing in class, but I'm not entirely sure if they are the best option for performance.
upvoted 0 times
...

Save Cancel