SF-Data-Arch Data Modeling and Database Design Practice Question
Which design approach is best for handling a 'Data Warehouse' requirement within Salesforce when dealing with millions of records?
⚠ Common exam trap
Candidates mistakenly suggest standard custom objects for long-term archiving of tens of millions of records, ignoring platform storage limits and data skew.
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
✓
Implement Big Objects for high-volume storage.
For high-volume data, architects should utilize Big Objects or External Objects to prevent hitting platform storage limits and performance degradation. Big Objects are specifically designed to store and query massive amounts of data efficiently. This strategy is vital for data management, as it keeps the core CRM performance high while still maintaining accessibility to historical archives needed for operational reporting or compliance purposes.
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 objects and archive periodically.
Why it's wrong here
Archiving standard objects frequently creates maintenance overhead and complicates data retrieval. It is not designed for analytical workloads or massive datasets. Relying on this approach often leads to data fragmentation and makes it difficult for users to maintain a holistic view of the customer across the entire lifecycle.
- ✓
Implement Big Objects for high-volume storage.
Why this is correct
Big Objects are purpose-built for massive scale, allowing storage and querying of billions of records. They do not count against the standard record count limits and offer optimized performance for analytical queries. This is the optimal architecture for data-intensive requirements, ensuring that the CRM platform remains fast and responsive.
- ✗
Store all data in a single custom object.
Why it's wrong here
Storing millions of records in a single custom object will cause significant performance issues, including slow queries, reporting timeouts, and potential governor limit violations. It ignores the platform's architectural limits and will lead to system degradation, making the environment unusable for standard business processes as data volume grows over time.
- ✗
Use a custom field to store external reference IDs.
Why it's wrong here
While external reference IDs are useful for integration, they are not a storage solution. Storing the primary data externally without a proper Salesforce-native strategy like Big Objects or External Objects makes the data inaccessible for native reporting and analytics, failing the core requirements of a data warehouse implementation within Salesforce.
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.