Universal Containers (UC) is concerned that data is being corrupted daily either through negligence or maliciousness. They want to implement a backup…

When designing a field-level audit and recovery plan, the primary consideration is the significant increase in data volume. Solutions like Field Audit Trail or custom audit objects generate a large amount of historical data. Therefore, the architect must review and project the data storage needs to ensure the solution is sustainable, performant, and does not exceed Salesforce org limits. This analysis informs the choice of solution, data retention policies, and potential need for off-platform archiving of the audit data itself.

A. Reduce data storage by purging old data: Purging data is contrary to the goal of creating a robust audit and recovery plan which relies on retaining historical data.

B. Implement an AppExchange package: This is a potential solution, not a design consideration. The architect must first consider requirements like storage before selecting a tool.

D. Schedule a weekly export file: While a weekly export is part of a backup strategy, it is not a "field-level audit" and is a specific tactic, not a foundational design consideration like storage.

1. Salesforce Help, "Field Audit Trail". The documentation explicitly states, "Field Audit Trail lets you know the state and value of your data for any date, at any time. But it uses a lot of your data storage." (See "Considerations for Field Audit Trail").

2. Salesforce Architects, "Architect's Guide to Data Management". This guide emphasizes the importance of understanding data growth and storage implications when implementing data governance and retention policies. (See "Data Governance" section).

3. Salesforce Help, "Monitor Data and Storage Resources". Architects must be aware of how different features consume storage to plan effectively.