SF-Data-Arch Salesforce Data Management Practice Question
A Data Architect is designing a strategy to manage 'soft-deleted' data in a Salesforce instance. The requirement is to maintain data for seven years, but only show active records in standard views. What is the most recommended approach?
⚠ Common exam trap
Candidates often over-engineer by suggesting archiving to external databases or custom objects, ignoring that simple list view filtering on a boolean field is the most performant, native solution.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use an 'Active' checkbox and filtered list views to hide inactive records.
Using a combination of a status field and optimized list views/reports provides a flexible, low-impact solution. By setting an 'IsActive' flag, data remains available for historical reporting and audits without cluttering the UI for operational users. This pattern is easily scalable and avoids the complexities of moving data to external systems or utilizing custom objects, while adhering to organizational data retention policies without compromising standard Salesforce object relationships.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use the 'Archive' custom object to store all inactive records.
Why it's wrong here
Moving data to a custom object breaks reporting capabilities that span across both current and historical records. It forces developers to create complex joins or union-like reports, increasing maintenance overhead and complexity. Furthermore, it creates a fragmented data model that is difficult for end-users to navigate effectively.
- ✓
Use an 'Active' checkbox and filtered list views to hide inactive records.
Why this is correct
This approach is the standard Salesforce practice for managing record lifecycle without deleting data. By using a simple status flag, users see only what they need, while data remains in the main table for audit and reporting purposes. It maintains full relational integrity and keeps the data easily accessible for compliance.
- ✗
Create a daily batch job that deletes records older than one year.
Why it's wrong here
Deleting records violates the seven-year retention requirement. If the records must be kept for compliance, simply deleting them after one year is insufficient. While the data could be backed up, it would no longer be searchable within the Salesforce environment, which is a key requirement for the audit process.
- ✗
Change the sharing settings to 'Private' for all inactive records.
Why it's wrong here
Sharing settings are meant for security, not lifecycle management. While private settings could hide records from certain users, they would still appear in global searches and reports for those with higher access. It does not provide a clean separation for operational users and creates unnecessary complexity in the security model.
About these practice questions
This SF-Data-Arch question is part of Courseiva's 222-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-Data-Arch practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Data-Arch exam.