Which type of workload traditionally benefits from the use of the query acceleration service?

Question

Options

• AWorkloads with a predictable data volume for each query
• BWorkloads that include on-demand data analyses
• CQueries with small scans and non-selective filters
• DQueries that do not have filters or aggregation

• A
  4% (2)
• B
  90% (43)
• C
  4% (2)
• D
  2% (1)

Explanation

The Query Acceleration Service (QAS) is designed for ad-hoc or on-demand analytical queries whose data volumes are large and unpredictable. It offloads portions of query processing (particularly large scans and selective filter operations) to shared serverless compute, reducing reliance on the virtual warehouse. Predictable, steady workloads (A) gain little benefit because they can be right-sized with a fixed warehouse. Queries with small scans and non-selective filters (C) or no filters/aggregations (D) don't involve the large intermediate result sets that QAS is optimized to accelerate.

No community discussion yet for this question.