Discuss Appian ACD201 Exam Topic 4 Question 6

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?

ACreate Audit table(s) and create stored procedures on each transaction table to compare and save the modified data.

BCreate utility process model(s) to insert new version of the modified data for the same record into the transaction tables on modification.

CCreate Audit table(s) and create triggers on each transaction table to record modifications into the Audit table.

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.

Get Premium ACD201 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

29 comments · newest first

Vincent 7 months ago

Plus, it keeps the audit trail clean and consistent.

Whitley 7 months ago

True, C ensures all changes are captured.

Kanisha 7 months ago

B seems less reliable. What if the utility fails?

Willard 8 months ago

Option A could work too, but it feels more complex.

Vincent 8 months ago

I agree, C is efficient. No need for manual intervention.

Whitley 8 months ago

I think option C is the best. Triggers automate the logging process.

Nelida 8 months ago

Wait, can triggers really handle all that data without slowing things down?

Lashandra 8 months ago

I totally agree with C, triggers are the way to go!

Lino 9 months ago

I prefer A, stored procedures give more control over the process.

Erick 9 months ago

Triggers? Really? That's so 2000s. I'd go with option B and use a utility process. More modern and flexible.

Joye 9 months ago

Option C is the clear winner here. Triggers are the standard approach for implementing field-level auditing.

Leontine 9 months ago

Haha, option B sounds like something a software engineer would come up with to overcomplicate a simple problem. Triggers all the way!

Magda 9 months ago

I agree, triggers are the way to go. Stored procedures and utility processes sound like overkill for a simple audit requirement.

Reita 9 months ago

Option C is the way to go. Triggers are the easiest and most efficient way to capture data changes.

Giovanna 10 months ago

Option C seems the most efficient for real-time tracking.

Carmela 10 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.

Ciara 10 months ago

B sounds interesting, but isn't it a bit redundant?

Tula 11 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.

Kris 11 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.

Tiera 11 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.

Ashlyn 11 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.

Lelia 6 months ago

↳ replying to Ashlyn

Good point! Maybe we should consider the trade-offs before deciding.

Lavera 6 months ago

↳ replying to Ashlyn

True, less manual coding is always a plus!

Penney 10 months ago

↳ replying to Ashlyn

I agree, option C sounds efficient. Triggers will handle it seamlessly.

Trina 10 months ago

↳ replying to Ashlyn

But what about performance? Triggers can slow down transactions.

Wynell 12 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.

Kristel 12 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.

Ulysses 12 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.

Raina 1 year 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.

Appian ACD201 Exam - Topic 4 Question 6 Discussion