How are data retention policies handled in Foundry?

• A. Delete data immediately after use.
• B. Configure retention periods, automatic archival, deletion rules, and compliance auditing.
• C. Ignore retention.
• D. Store everything indefinitely.

Answer: (B)

Data retention in Foundry is managed through policy-driven lifecycle management that governs how long data stays, how it’s archived, when it’s deleted, and how activity is recorded for compliance. You configure retention periods for assets so they remain usable for the required time. When data isn’t actively used but hasn’t reached its end of life, the system can automatically archive it to lower-cost storage while keeping it accessible if needed. When the retention window ends or certain conditions are met, deletion rules remove the data in a controlled way to satisfy governance and privacy requirements. Compliance auditing tracks who accessed, archived, or deleted data and when, providing an auditable trail for regulators and internal governance.

For example, a dataset may have a seven-year retention. If it becomes inactive, it can be archived automatically, and once seven years pass, a deletion rule removes it, with an audit log recording the actions taken.

Immediate deletion, ignoring retention, or storing everything indefinitely don’t align with governance, cost management, or regulatory needs.