A company uses Amazon Redshift for its data warehouse. While designing a physical schema, a data engineer finds a denormalized table that keeps growing but has no good candidate for a distribution key. Which distribution style should the engineer choose to minimize ongoing maintenance?

AUTO distribution is the best choice because Amazon Redshift automatically determines the optimal distribution style for the table based on its size and how it's used. This minimizes ongoing maintenance as Redshift adapts to changes in data and query patterns without manual intervention. ALL distribution copies the entire table to every compute node, which is inefficient for large, growing tables as it consumes significant storage and slows down writes. EVEN distribution distributes rows round-robin across all nodes, which is a good default but might not be optimal for query performance if data needs to be co-located for joins. KEY distribution requires a specific column to be chosen as the distribution key, which the problem statement explicitly states is not available or suitable.