DATA-ARCHITECT practice question 1 of 35

Which three characteristics of a skinny table help improve report and query performance?

Full set: 257 questions
Answer options
A: Skinny tables can contain frequently used fields and thereby help avoid joins. Correct answer
B: Skinny tables can be used to create custom indexes on multi-select picklist fields.
C: Skinny tables provide a view across multiple objects for easy access to combined data.
D: Skinny tables are kept in sync with changes to data in the source tables. Correct answer
E: Skinny tables do not include records that are available in the recycle bin. Correct answer
Correct Answer:
A. Skinny tables can contain frequently used fields and thereby help avoid joins.; D. Skinny tables are kept in sync with changes to data in the source tables.; E. Skinny tables do not include records that are available in the recycle bin.
Explanation

Skinny tables are a performance-tuning feature created by Salesforce Support to optimize queries on objects with millions of records. They work by creating a separate, narrower database table that contains a subset of frequently used fields, including fields from a parent object to avoid costly joins (A). Salesforce automatically keeps this table synchronized with the source data (D). Crucially, skinny tables do not contain soft-deleted records (records in the Recycle Bin), which makes queries more efficient as they don't need to filter these records out (E).

Why Incorrect

B. Skinny tables are not a mechanism for creating indexes on multi-select picklist fields; custom indexes are a separate feature.
C. While a skinny table can provide a "view" across objects, option A is more precise by stating the mechanism: it helps avoid joins, which is the direct source of the performance gain.

References

1. Salesforce Developer Documentation, "Best Practices for Deployments with Large Data Volumes", Section: "Use Skinny Tables to Improve Performance". This document states, "Skinny tables can contain frequently used fields and avoid joins...", "Skinny tables are kept in sync with their source tables...", and "Skinny tables don’t include soft-deleted records...".

2. Salesforce Help, "Reduce Report Timeouts", Section: "Ask Salesforce to create a skinny table". This article confirms that skinny tables "combine frequently accessed fields into a single table to avoid joins" and are "kept in sync with the source table".

Scroll to Top