Which of the following describes the auditing capabilities Foundry provides?

• A. Auditing capabilities that log only login events.
• B. Auditing capabilities that maintain data integrity, transparency, and historical lineage.
• C. Auditing capabilities that track only data exports.
• D. Auditing capabilities that delete historical data after use.

Answer: (B)

Auditing in Foundry is about complete observability of data actions across the platform. It records what happened, who did it, and when, across the full spectrum of activities—reads, writes, transformations, exports, and permission changes—creating an end-to-end trail of data movement and usage. This ongoing record supports data integrity, transparency, and historical lineage, giving you a trustworthy history of how data has evolved and been accessed, which is essential for governance, compliance, and troubleshooting. The option that best describes this broad, preservation-focused capability is the one that emphasizes maintaining data integrity, transparency, and historical lineage. The other choices are narrower or contradict the purpose of auditing (such as logging only login events, tracking only exports, or deleting historical data after use).