How do you audit user activity in Foundry?

• A. Rely on user self-reports.
• B. Only monitor login failures.
• C. Use audit logs, track asset changes, access events, monitor suspicious actions, and export for compliance.
• D. Disable auditing for performance.

Answer: (C)

Auditing user activity in Foundry relies on capturing a comprehensive trail of actions across the platform. This means using audit logs to record who did what, when, and from where; tracking changes to assets so you can see who modified datasets, pipelines, permissions, and other objects; monitoring access events to know who accessed which data and when; watching for suspicious actions to detect anomalies; and exporting these records to support compliance and external audits. This combination provides a complete, verifiable history rather than relying on memory or scattered indicators. Relying on self-reports is unreliable and incomplete; monitoring only login failures misses most activity and data access; and disabling auditing removes traceability and regulatory control.