DEA-C01 · Question #38
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 becau
The correct answer is C. Use the ALL distribution style for rarely updated small tables. Specify primary and foreign keys for. Use the ALL Distribution Style for Rarely Updated Small Tables. This approach optimizes the performance of joins involving these smaller tables and is a common best practice in Redshift data warehousing. For the larger tables, maintaining the EVEN distribution style or considerin
Question
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?
Options
- AKeep using the EVEN distribution style for all tables. Specify primary and foreign keys for all
- BUse the ALL distribution style for large tables. Specify primary and foreign keys for all tables.
- CUse the ALL distribution style for rarely updated small tables. Specify primary and foreign keys for
- DSpecify a combination of distribution, sort, and partition keys for all tables.
How the community answered
(34 responses)- A9% (3)
- B18% (6)
- C71% (24)
- D3% (1)
Explanation
Use the ALL Distribution Style for Rarely Updated Small Tables. This approach optimizes the performance of joins involving these smaller tables and is a common best practice in Redshift data warehousing. For the larger tables, maintaining the EVEN distribution style or considering a KEY-based distribution (if there are common join columns) could be more appropriate.
Topics
Community Discussion
No community discussion yet for this question.