SF-Data-Arch Large Data Volume Considerations Practice Question
A data architect is planning to implement a Skinny Table for a custom object with 10 million records to improve query performance. Which two considerations are critical when designing the Skinny Table? (Choose two.)
⚠ Common exam trap
The trap here is assuming a Skinny Table must mirror all fields or can replace the main object entirely, when it is a targeted performance optimization.
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
✓
The Skinny Table requires a synchronization mechanism to keep data current with the main object.
A Skinny Table is a denormalized copy of a subset of fields from a large object, used to accelerate specific queries. The two critical considerations are selecting only the fields needed for common queries to minimize row size, and implementing a synchronization mechanism to keep the copy up to date. Without these, the Skinny Table would either be too large to be effective or become inconsistent with the source data.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The Skinny Table requires a synchronization mechanism to keep data current with the main object.
Why this is correct
Because a Skinny Table is a separate custom object, it does not automatically reflect changes to the main object. A synchronization process, such as a trigger or batch job, must be implemented to update the Skinny Table when the main object changes. Without synchronization, the Skinny Table would become stale and produce incorrect query results.
- ✗
The Skinny Table can be used as the primary data source for all reporting to replace the main object.
Why it's wrong here
A Skinny Table is intended for specific, performance-critical queries, not as a full replacement for the main object. It lacks the full set of fields and business logic, so using it for all reporting would lead to incomplete data and maintenance challenges. The main object should remain the system of record.
- ✗
The Skinny Table should be indexed on all fields to maximize query flexibility.
Why it's wrong here
Indexing all fields is not feasible or necessary. Salesforce limits the number of custom indexes per object, and indexing low-selectivity fields provides little benefit. Only fields used in selective filters should be indexed. Over-indexing can also degrade write performance.
- ✗
The Skinny Table must include all fields from the original object to maintain data integrity.
Why it's wrong here
Including all fields defeats the purpose of a Skinny Table, which is to reduce row size and improve performance. Data integrity is maintained by keeping the Skinny Table in sync with the main object through a synchronization process, not by duplicating all fields. Only a subset of fields is needed.
- ✓
The Skinny Table should include only the fields required for the most common queries.
Why this is correct
A Skinny Table is designed to contain a subset of fields from the main object to reduce the data volume per row, improving query performance. Including only frequently queried fields minimizes storage and speeds up reads. Fields not needed for common queries should remain on the main object to avoid unnecessary overhead.
About these practice questions
One of 222 original SF-Data-Arch practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.