Audit logs play what role in address changes and events?

Audit logs play what role in address changes and events?

• A. Regular automated changes with no audit
• B. User feedback alone
• C. Periodic data cleansing without logs
• D. Audit logs that record address changes and events

Answer: (D)

Audit logs provide traceability and accountability for address changes and events. They capture who made a change, when it happened, and what specifically was changed, often including previous and new values. This visibility is essential for security, compliance, and data integrity, because it lets you investigate discrepancies, detect unauthorized updates, and understand the sequence of events that affected an address record. With a verifiable log, you can audit activities, support troubleshooting, and even revert changes if needed. The other options miss this critical history: automatic changes without an audit trail lack accountability; relying on user feedback alone doesn’t establish a formal, verifiable record; and periodic data cleansing without logs discards the necessary context to understand how and when data evolved.

Audit logs provide traceability and accountability for address changes and events. They capture who made a change, when it happened, and what specifically was changed, often including previous and new values. This visibility is essential for security, compliance, and data integrity, because it lets you investigate discrepancies, detect unauthorized updates, and understand the sequence of events that affected an address record. With a verifiable log, you can audit activities, support troubleshooting, and even revert changes if needed. The other options miss this critical history: automatic changes without an audit trail lack accountability; relying on user feedback alone doesn’t establish a formal, verifiable record; and periodic data cleansing without logs discards the necessary context to understand how and when data evolved.