A Fabric data warehouse contains a large fact table, FactSales (1.2 billion rows), that is frequently joined to a large dimension table, DimCustomer (40 million rows), on CustomerKey. Analysts report that queries joining these two tables are slow, and when you inspect the query plan you see a large data movement (shuffle/redistribution) operation before the join. Both tables are currently loaded without any distribution strategy specified. What is the most effective way to reduce this data movement and improve join performance?