What audit data should be captured for address changes?

What audit data should be captured for address changes?

• A. Who changed it, when, previous value, new value, reason/source (UI, API, import), and whether the change affected active status or history.
• B. Only timestamp.
• C. Only user ID.
• D. No audit data.

Answer: (A)

Tracking address changes requires capturing who made the change, when it happened, the values before and after, the reason or source of the change (UI, API, import), and whether the change affects the active address or the historical record. This combination gives a complete, verifiable trail: you know exactly which user or process performed the change and when, you can see precisely what changed, you can understand how the change came about (manual edit vs automated import), and you can assess its impact on the current record and on the history of changes. Relying on only a timestamp misses who or what changed and what the actual data change was; recording only a user ID lacks the details of what was altered, and no audit data provides no traceability at all.

Tracking address changes requires capturing who made the change, when it happened, the values before and after, the reason or source of the change (UI, API, import), and whether the change affects the active address or the historical record. This combination gives a complete, verifiable trail: you know exactly which user or process performed the change and when, you can see precisely what changed, you can understand how the change came about (manual edit vs automated import), and you can assess its impact on the current record and on the history of changes. Relying on only a timestamp misses who or what changed and what the actual data change was; recording only a user ID lacks the details of what was altered, and no audit data provides no traceability at all.