What is a key consideration when setting up search optimization service for a table?

Question

Options

• ASearch optimization service works best with a column that has a minimum of 100 K distinct values.
• BSearch optimization service can significantly improve query performance on partitioned external
• CSearch optimization service can help to optimize storage usage by compressing the data into a
• DThe table must be clustered with a key having multiple columns for effective search optimization.

• A
  93% (40)
• B
  5% (2)
• C
  2% (1)

Explanation

The Search Optimization Service (SOS) builds a persistent search access path (a dedicated data structure maintained by a background service) that accelerates equality and IN-list predicates on columns with high cardinality - meaning many distinct values. Option A correctly identifies that SOS is most effective when a column has a large number of distinct values (the 100K threshold is the recognized benchmark), because the access path can efficiently narrow down which micro-partitions contain a specific value without a full table scan. Option B is incorrect: SOS has limited or no benefit for external tables and does not significantly improve partitioned external table queries. Option C is incorrect: SOS actually increases storage consumption because it maintains a supplemental data structure alongside the table - it does not compress data. Option D is incorrect: SOS works independently of clustering keys; a table does not need to be clustered at all, let alone with multiple columns, to use SOS.

No community discussion yet for this question.