Which field supports explaining changes in a Clarity data model audit?

Which field supports explaining changes in a Clarity data model audit?

• A. change_reason
• B. created_at
• C. updated_by
• D. valid_from

Answer: (A)

Capturing why a change was made is essential for an audit trail. The field that stores that rationale is change_reason. It provides a clear, human-readable explanation of the modification, which audit reviewers rely on to understand the intent behind the change. Other fields describe when the change happened or who made it—created_at marks creation time, updated_by shows who last edited, and valid_from indicates when the change becomes effective. These help track timing and responsibility, but they don’t convey the reason behind the change. For example, if a value was corrected due to a data-entry error, change_reason might be "corrected data-entry error in field X."

Capturing why a change was made is essential for an audit trail. The field that stores that rationale is change_reason. It provides a clear, human-readable explanation of the modification, which audit reviewers rely on to understand the intent behind the change. Other fields describe when the change happened or who made it—created_at marks creation time, updated_by shows who last edited, and valid_from indicates when the change becomes effective. These help track timing and responsibility, but they don’t convey the reason behind the change. For example, if a value was corrected due to a data-entry error, change_reason might be "corrected data-entry error in field X."