DEA-C02 Performance Optimization Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Query acceleration service

  Why it's wrong here

  Query acceleration service helps with queries that have large scans and selective filters by offloading portions of the scan to shared compute resources. However, it is not specifically designed for point lookups on high-cardinality columns. Search optimization service is the more targeted solution for this scenario.

• ✓

  Search optimization service

  Why this is correct

  Search optimization service is designed to accelerate selective point lookups and queries that filter on high-cardinality columns and return a small number of rows. It builds a search access path that allows the optimizer to quickly locate matching rows without scanning all micro-partitions. This directly addresses the slow dashboard query pattern.

• ✗

  Materialized view

  Why it's wrong here

  Materialized views are beneficial for pre-computing aggregations or joins, but they are not optimized for selective point lookups on high-cardinality columns. They require maintenance and may not improve performance for queries that return a small number of rows. The search optimization service is specifically designed for this use case.

• ✗

  Clustering key on the filtered column

  Why it's wrong here

  Clustering can improve pruning for range filters, but for high-cardinality columns with point lookups, the benefits are limited because the data is spread across many micro-partitions. Clustering may not provide the same performance boost as search optimization for selective queries. It is more suited for range or equality filters on lower cardinality columns.