An analyst occasionally runs ad hoc queries that each scan a very large table and spill heavily because a single warehouse cluster lacks the scan throughput, yet these queries are infrequent so the team does not want to pay for a permanently larger warehouse. They want these outlier scan-heavy queries to borrow additional compute only while they run. Which feature best addresses this scenario?
- AConvert the warehouse to a multi-cluster warehouse in auto-scale mode so additional clusters start and absorb each outlier scan-heavy query as it runs
- BAdd the search optimization service to the large table so the infrequent ad hoc scans prune to fewer micro-partitions and finish without spilling to remote storage
- CDefine a clustering key on the table so automatic clustering co-locates the data and each large ad hoc scan reads fewer micro-partitions and avoids spilling
- DEnable the query acceleration service on the warehouse so eligible scan-heavy queries offload portions of their work to serverless compute only while they run Correct
Why A is wrong: Multi-cluster warehouses add clusters to handle concurrent queries, but a single large scan still runs on one cluster, so extra clusters do not give that one query more scan throughput.
Why B is wrong: Search optimization accelerates selective lookups, not broad full-table scans, so it does not help ad hoc queries that legitimately read most of a very large table.
Why C is wrong: Clustering only helps when queries filter on the clustering key, so it does little for unpredictable ad hoc scans that read large fractions of the table regardless of order.
Why D is correct: Query acceleration lets eligible large-scan queries borrow serverless compute for parts of their work during execution, speeding outliers without paying for a permanently bigger warehouse.