The AUDIT_ITM tables in Clarity hold the audit trail that Chronicles records when item auditing is enabled. Auditing is a deliberate configuration: it is activated for specific items that warrant a history of changes, so these tables can answer questions about who changed a value and when, but only for items on which auditing has been turned on. That is the sense of the second option. The first option overstates the coverage, since turning auditing on for every item would be impractical and is not the design, and items without auditing leave no trail to extract. The third option is incorrect: the point of the audit tables is that the change history is retained and extracted to Clarity, making it recoverable for analysis. The fourth option is correct because the underlying audit data resides in Chronicles, where the Record Viewer can be used to examine it for a record, allowing an analyst to corroborate what the Clarity table shows or to research a specific change. Together these characteristics make the tables a targeted forensic resource rather than a universal log, and an analyst should first confirm that auditing was active for the item in question.
[Reference: Cogito Fundamentals – Clarity Data Model: Audit Tables; Record Viewer, ===============, ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit