SF-Data-Arch Data Modeling and Database Design Practice Question
An organization has 50 million records in a custom object. They need to report on historical snapshots weekly. What is the best strategy to manage storage while keeping data available?
⚠ Common exam trap
Test-takers frequently choose standard reporting snapshots or standard archival objects, ignoring the massive scale of 50 million records which will quickly breach standard data storage limits.
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 Big Objects
Big Objects are designed for massive scale, supporting billions of records with optimized storage costs. By moving historical snapshot data to Big Objects, the organization retains accessibility for reporting via asynchronous queries or external tools without consuming standard Salesforce storage limits. This strategy preserves database performance for the active operational records while ensuring compliance and historical availability for long-term analytical business requirements.
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 standard Salesforce objects
Why it's wrong here
Using standard objects for 50 million records will quickly exhaust data storage limits, incurring significant costs. Furthermore, large volumes in standard tables can degrade query performance and impact the efficiency of indexing, making this an unsuitable long-term strategy for high-volume historical snapshot data storage.
- ✓
Use Big Objects
Why this is correct
Big Objects allow for the storage and querying of massive datasets without impacting performance or standard data storage limits. They are specifically engineered to handle high volumes, making them the optimal choice for weekly snapshots that need to be queried but not frequently updated or edited.
- ✗
Move data to a sandbox
Why it's wrong here
Sandboxes are not designed for long-term production data storage or archival. Moving production data to a sandbox will not solve the storage limit issue in production, and it introduces security risks regarding production data persistence, version control, and potential synchronization issues with the live environment.
- ✗
Use Platform Events
Why it's wrong here
Platform Events are for real-time event-driven messaging, not for persisting historical records. They have a short retention period and are not intended to act as a database for reporting snapshots. Using them for this purpose would result in data loss as events expire after 24 to 72 hours.
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.