Answer-first summary for fast verification
Answer: Use the ALL distribution style for rarely updated small tables. Specify primary and foreign keys for all tables.
Using the ALL distribution style for small, rarely updated tables (such as dimension tables) optimizes performance by placing a full copy of the table on every compute node. This drastically reduces the need for data movement (broadcasting) across the cluster during JOIN operations. Large tables should not use the ALL distribution style because it heavily multiplies storage requirements and slows down loading and updating.
Author: Ritesh Yadav
Ultimate access to all questions.
Question 14
A company's data engineer needs to optimize the performance of table SQL queries. The company stores data in an Amazon Redshift cluster. The data engineer cannot increase the size of the cluster because of budget constraints. The company stores the data in multiple tables and loads the data by using the EVEN distribution style. Some tables are hundreds of gigabytes in size. Other tables are less than 10 MB in size. Which solution will meet these requirements?
A
Keep using the EVEN distribution style for all tables. Specify primary and foreign keys for all tables.
B
Use the ALL distribution style for large tables. Specify primary and foreign keys for all tables.
C
Use the ALL distribution style for rarely updated small tables. Specify primary and foreign keys for all tables.
D
Specify a combination of distribution, sort, and partition keys for all tables.
No comments yet.