A data engineer manages a large Delta table that is frequently queried with filters on different columns depending on the reporting period — sometimes by region, other times by product_category, and increasingly by sales_rep_id. The team currently uses static partitioning on region, but query performance has degraded and many small files exist within some partitions. They want a layout strategy that adapts to changing query patterns without requiring them to rewrite the table's partitioning scheme each time filter columns change. Which approach best addresses this requirement?