SF-Data-Arch Data Modeling and Database Design Practice Question
An architect is modeling a 'Subscription' service where Customers have multiple active subscriptions. Which approach best handles the 'Current' vs 'Historical' subscription data for reporting?
⚠ Common exam trap
Candidates often try to create separate objects for historical and current records, leading to complex data synchronization challenges rather than utilizing simpler status-driven schemas.
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 a single object with 'Status' and 'Date' fields.
Using a combination of a status field and a date range is the standard way to model active versus historical subscriptions. By flagging records as 'Active' and using the 'End Date' field, the architect allows the system to easily filter for current records while maintaining a full history. This design supports both operational reporting and long-term analytical tracking, which is essential for subscription-based business models.
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 two separate objects for Current and Historical subscriptions.
Why it's wrong here
Maintaining two separate objects is a 'Split-brain' architecture that creates significant complexity. It requires double-entry or custom automation to move records between objects and makes reporting across both sets of data extremely difficult, as you would need to combine results from two distinct data sources.
- ✓
Use a single object with 'Status' and 'Date' fields.
Why this is correct
A single object with a status field and date range is the most efficient design. It allows for simple filtering (e.g., WHERE Status = 'Active') and makes historical reporting straightforward. This pattern is easy to maintain and scales well as the number of subscription records grows.
- ✗
Delete historical records to save storage space.
Why it's wrong here
Deleting historical data destroys the audit trail and prevents longitudinal analysis of customer behavior. Businesses need this data to calculate lifetime value, churn, and other critical metrics. Deletion should only occur as part of a formal data retention policy, not as a primary architectural choice.
- ✗
Use a multi-select picklist to track history.
Why it's wrong here
Multi-select picklists are not designed for tracking history or filtering by date ranges. They would quickly become cluttered and unmanageable, and it would be impossible to report on the state of a subscription at a specific point in time using this data structure.
About these practice questions
Courseiva writes every SF-Data-Arch question from scratch — 222 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.