A retail company stores transactions, store locations, and customer tables on a four-node reserved ra3.4xlarge Amazon Redshift cluster. All tables currently use EVEN distribution. The store location table is updated very infrequently, but queries are slow because the table is being broadcast to all four compute nodes. To reduce broadcasting and speed up queries in the most cost-effective way, what should the data engineer do?

Changing the distribution style of the store location table to ALL distribution is the most cost-effective solution. ALL distribution replicates the entire table to every compute node, eliminating the need for broadcasting during queries. This significantly speeds up queries involving the store location table, especially since it's updated infrequently. KEY distribution would require careful selection of a distribution key and might not eliminate broadcasting for all queries. Adding a join column to the sort key only helps with sorting and filtering, not distribution. Upgrading instance size is a more expensive solution that might not address the root cause of broadcasting.