Exam Certified Data Architect topic 1 question 53 discussion

Not A, because you can't create one skinny table for both account and contact. Remember the documentation says 'Skinny tables can not refer fields from another object.' Skinny table only avoids a join to fetch standard and custom fields for one object. so contact skinny table can include related account Id but not any other field as per my understanding

It must be C. A is not valid because you cannot condense data from two objects in a single skinny table. If the answer had been phrased as create a skinny table for each object, then this would be also a valid answer.

Cannot be A because Skinny tables do not support multiple objects. Adding indexes does improve search performance.

Skinny tables can be created on custom objects, and on Account, Contact, Opportunity, Lead, and Case objects. They can enhance performance for reports, list views, and SOQL.

Not A - The primary bottleneck seems to be search performance, which indexes directly address. C - Indexes speeds up data retrieval.

The most accurate answer is A. Create a skinny table to represent account and contact objects. Skinny tables can be used to improve the performance of read-only operations in Salesforce. They contain frequently used fields and are kept in sync with their source tables. By reducing the number of joins performed during a query, skinny tables can significantly improve the performance of reports and list views. Not C. Add custom indexes on frequently searched account and contact objects fields: While adding custom indexes can improve the performance of certain types of queries, it may not have a significant impact on the performance of reports and list views. Additionally, maintaining custom indexes can add complexity and overhead.